DB Wait Link Not Working in JVM Diagnostics
Last updated on NOVEMBER 05, 2016
Applies to:Enterprise Manager Base Platform - Version: 18.104.22.168 to 22.214.171.124 - Release: 11.1 to 11.1
Information in this document applies to any platform.
JVM Diagnostics setup and running in EM Grid Control. The dbagent is deployed to an Oracle database running on host machine with virtual IP address.
In JVM Diagnostics Manager, the Real Time Analysis page shows DB Waits for threads that are waiting on a locked table in the database. Clicking on DB Wait hyperlink drills down to database level showing the session holding the lock. However, the DB Wait link does not work, there is no hyperlink.
The dbagent output on database host shows following:
Error reading IP Config Structures: Invalid argument
JAM Agent: Received 354 bytes 4|NoProcessing|activethreads|global|currcall|weblogic.socket.DevPollPosixSocketMuxer->processSockets
global|currcall|weblogic.socket.DevPollSocketMuxer->processSockets| | || from console
Jam Agent: Keep alive time out occured, connecting to console.
The server output on EMAD4JMANAGER managed server shows following:
JAM No database matching [x.x.x.x], service [xxx.xxx.xxx.xxx)or sid , port  found in registered DBs
JAM ERROR:PoolMonitor pollJVMs(): could not get dbname from dburl [jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.xxx)(PORT=1570)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=xxx.xxx.xxx.xxx))] no matching database found
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms