cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

DB monitor doesnt work

ibabinec
Newcomer
 
5 REPLIES 5

shane_korbel
Dynatrace Pro
Dynatrace Pro

Hi Ivo! Could you please provide some more details and some screenshots of the issue you are having?

ibabinec
Newcomer

Hello,

We've got couple of db monitors which works without any problems.

We've creted new one, but we're not able to connect to db...

Type : Oracle

DB : CPSP

Port : 1521
Connection string (url]) : jdbc:oracle:thin:@odbrca1-scan.cc.csin.cz:1521/CPSP

query : SELECT count(*) FROM cpscsys.t1560case_search_data;

T

We're sure about SQL name and password. (tested)

Log shows us following error when monitor executed :

2017-02-02 21:00:14 INFO [QMonitor@CPSP _0] Connecting to Oracle database: jdbc:oracle:thin:@odbrca1-scan.cc.csin.cz:1521/CPSP
2017-02-02 21:00:14 SEVERE [QMonitor@CPSP _0] java.sql.SQLException: IO Error: The Network Adapter could not establish the connection
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:458)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:236)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at com.db.monitor.QueryMonitor.execute(QueryMonitor.java:139)
at com.db.monitor.QMonitor.execute(QMonitor.java:30)
at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:720)
at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:478)
at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:278)
at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)
at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)
at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)
at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)
at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)
at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)
at com.dynatrace.diagnostics.schedule.SchedulerJob.work(SourceFile:92)
at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)
at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at com.dynatrace.diagnostics.schedule.QuartzThreadPool$WorkerThread.run(SourceFile:788)
Caused by: oracle.net.ns.NetException: The Network Adapter could not establish the connection
at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:392)
at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:434)
at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:687)
at oracle.net.ns.NSProtocol.connect(NSProtocol.java:343)
at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1102)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:320)
... 22 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:150)
at oracle.net.nt.ConnOption.connect(ConnOption.java:133)
at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:370)
... 27 more

We are able to telnet from dt collector to db server...
Connection is established.

Other db monitors works well (diffrent db server).
Any idea where could be a problem ?

Babar_Qayyum
Leader

Hello Ivo,

I guess the necessary permissions for DB monitoring granted to the user that is used to connect to the DB instance.

https://community.dynatrace.com/community/display/...

In case if you have Oracle RAC 12c leaf nodes
  • With Oracle Database with Real Application Clusters (RAC) 12c, new type of base platform was introduced: Oracle Flex Clusters. It contains two types of nodes: Hub Nodes and Leaf Nodes. AppMon is able to monitor only nodes, where actual database instance is running - and it can run only on Hub nodes. Because of that, monitoring Leaf nodes with Database Agent is not possible. However, Host Agent can be installed on machine, in order to collect data like memory & CPU usage and more.

The following page describes various techniques for troubleshooting.

https://community.dynatrace.com/community/display/...

Regards,

Babar

datla
Newcomer

@Ivo B.I am having the same issue. Were you able to resolve it ?

ibabinec
Newcomer

@Phani D.

Finally yes. But I forgot to mention, that my issue was regarding DB Monitor Plugin....
One problem was the semilocon sign in the query ";" which was interpreted incorrectly by jdbc.

And the other was with connectivity to db server - even if the connection was not established, the monitor say connection ok in the result, which was misleading...