WebLogic JDBC GridLink Data Source Host Status Is Not Showing Accurate Value
(Doc ID 2410419.1)
Last updated on FEBRUARY 10, 2025
Applies to:
Oracle WebLogic Server - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]Information in this document applies to any platform.
Symptoms
On WLS 12.2.1.3.0 version, JDBC Data Source ONS status is showing heartbeat instead of Running. If the DB host is not available, then it is not showing the right statistics. Instead it is showing as "sdevoxxxxx Tue Mar 20 15:19:32 MDT 2018". This can be summarized below:
ACTUAL BEHAVIOR
Host Sorted Ascending Port Status
sdevxxxdb12 6200 sdevxxxdb12 - Tue Mar 20 15:19:32 MDT 2018
sdevxxxdb14 6200 sdevxxxdb14 - Tue Mar 20 15:19:32 MDT 2018
EXPECTED BEHAVIOR
Host Sorted Ascending Port Status
devorxxxx 6200 Running
devorxxxxx 6200 Running
Host Sorted Ascending Port Status
sdevxxxdb12 6200 sdevxxxdb12 - Tue Mar 20 15:19:32 MDT 2018
sdevxxxdb14 6200 sdevxxxdb14 - Tue Mar 20 15:19:32 MDT 2018
EXPECTED BEHAVIOR
Host Sorted Ascending Port Status
devorxxxx 6200 Running
devorxxxxx 6200 Running
The ONS status can be verified in the WLS Admin Console: JDBC Data Sources > Drill down on a gridlink data source -> Monitoring -> Drill down on a server -> ONS.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |