Hi I have installed the Oracle Monitor Plugin, at a customer place in production but I am not able to connect to get any data.
I had tested the same in the UAT environment and it worked fine , however now when I am trying in the production setup I am unable to connect.
I get the following errors.
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
192.168.25.89:1521/bvsbipr
I am able to manually connect to the database using the same user id and Password. But when I try through the plugin I am unable to do so.
The collector used is running on the dynaTrace Warehous server, which has an Oracle Database already installed , do I still need to install a client?
Also as far as I understand , we use jdbc connection even for the plugin to get information and not an Oracle client , so do we still need a client for getting connection.
Attaching herewith are the screen shots of the error.
Request help.
Thanks and Regards,
Ritesh.
Answer by Ritesh S. · Jul 12, 2012 at 01:52 PM
Please find the screen shots of the configuration and error.
The error message you get points at the database not being known by the listener, you are not even at the point where user/password would be checked.
I would take a look at the source of the Oracle plugin to see how it assembles the JDBC connection string. Once you have the string you can try if your DB tool can connect using this, if not adjust the plugin accordingly.
Best, Roman
Answer by Mohammed I. · Jul 12, 2012 at 06:55 PM
I have un jared the oracle plugin jar file and found the below code is commented
private String getConnectionUrl() { if (url.equals("jdbc:oracle:thin")) {
/*jdbc:oracle:thin:/@localhost:1521:diagrepo20
url=jdbc:oracle:thin
serverName=localhost
portNumber=1521
databaseName=diagrepo20
userName=cmillerjava
password=
*/
//Oracle thin driver new syntax - http://www.orafaq.com/wiki/JDBC
return url + ":" + "//@" + host + ":" + port + "/" + dbService;
}
else if (url.equals("jdbc:jtds:sqlserver")) {
/*
jdbc:jtds:sqlserver://localhost:41884/diagrepo20;
url=jdbc:jtds:sqlserver
serverName=localhost
portNumber=41884cd ..
*
databaseName=diagrepo20
userName=cmillerjava
password=
*/
return url + ":" + "//@" + host + ":" + port + ":" + dbService;
}
return new String("");
}
If I have understood your above comment correctly, this code has to be uncommented and edited with the ip address of the installed Oracle host machine instead of the localhost
Please find the Jar fill attached
Regards Ibrahim ]]>
Hi Ibrahim,
I have not written this plugin but looking at the source code it is now generating the URL by using the parameters you pass into the plugin:
return url + ":" + "//@" + host + ":" + port + "/" + dbService;
The question really is - how does the JDBC URL need to look like in order to work. Once you have figured that out you can adjust the plugin to generate the right format. In order to test the JDBC URLs you could use a tool like SQuirreL - http://squirrel-sql.sourceforge.net.
Best, Roman
Answer by Rob V. · Jul 12, 2012 at 08:06 PM
Ibrahim,
Look into your TNSNAMES.ORA file and find the service name for the TNS name that you are trying to use. Put that in as the DBNAME in the Oracle plugin. For example, on my system this works fine going from a Windows-based collector to a Linux oracle server:
Does this work for you?
Rob
Answer by Ritesh S. · Jul 13, 2012 at 02:20 PM
Hi Rob,
Actually this was one of the first things that I had checked with the local DB Administrator.
However , we have now managed to get the correct Service_Name, out of the 3 that are in place so we are able to get the data .
Thanks and lot for your inputs.
Regards,
Ritesh
Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!
Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!
Would you like to have an early taste of what we have cooked up for 2019? We would love to hear your feedback and improve some of the new features. Check NAM 2019 Beta release notes.
Sign up today!