Splunk AppDynamics

Failed to resolve DB topological structure. java.sql.SQLException: ORA-01005: null password given; logon denied

ranaveer_mariya
New Member

Upgraded the Machine Agent from 22 to v24.8.0.4467, after the changes, seeing below errors,

[DBAgent-7] 06 Nov 2024 17:24:28,994 ERROR ADBMonitorConfigResolver - [XXXXXXXXXXXX] Failed to resolve DB topological structure.
java.sql.SQLException: ORA-01005: null password given; logon denied

I have provided the userid and password in the configuration -> controller setting,

Any one faced this kind of issue ?

Labels (1)
0 Karma

iamryan
Community Manager
Community Manager
0 Karma

Michael_Horstm1
Explorer

IDK if this will help you, but speaking as someone monitoring 468 Oracle RAC clusters, if it were me I'd try the following 3 steps, possibly putting the pw-validation above others if I was to alter anything as I wrote it below.

1) Disable the collector for a few minutes + re-enable the db collector - This is my goto solution for messages like this.
2) Validate the DBMonitor agent that's the middle man in all this is updated and compatible with your updated controller.
3) While you're there, attempt to validate you can establish a basic JDBC connection to the DB from the instance the DBMon collector is running on, and that you can do basic topology queries with the AppD DB user the collector is using.

I'm just speaking to you as another user who's been through similar issues, so hopefully it helps! 🙂

Get Updates on the Splunk Community!

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL  The Splunk AI Assistant for SPL ...

Buttercup Games: Further Dashboarding Techniques (Part 5)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Customers Increasingly Choose Splunk for Observability

For the second year in a row, Splunk was recognized as a Leader in the 2024 Gartner® Magic Quadrant™ for ...