In this Document
Symptoms |
Cause |
Solution |
References |
APPLIES TO:
Enterprise Manager for Oracle Database - Version 13.2.0.0.0 and laterInformation in this document applies to any platform.
SYMPTOMS
Getting the below error message on 12.2 target Database Home Page/ target cluster database home page in OEM Console:
Failed to connect to the target database. Regions that pull real-time data from the database will not be displayed.
Failed to connect to the target database. Regions that pull real-time data from the database will not be displayed.
emoms.trc
2018-11-09 08:37:00,738 [MetricCollector:SITEMAP_THREAD1513:15] ERROR rt.DbMetricCollectorTarget logp.251 - Exception in getConnection()<Database_name>:oracle_databasejava.sql.SQLException: Connection Cache with this Cache Name does not exist
2018-11-09 08:37:00,738 [MetricCollector:SITEMAP_THREAD1513:15] ERROR perf.sitemap logp.251 - java.sql.SQLException: Connection Cache with this Cache Name does not exist
java.sql.SQLException: Connection Cache with this Cache Name does not exist
at oracle.jdbc.pool.OracleConnectionCacheManager.purgeCache(OracleConnectionCacheManager.java:947)
at oracle.sysman.emSDK.core.util.jdbc.ConnectionCache.close(ConnectionCache.java:345)
2018-11-09 08:37:00,738 [MetricCollector:SITEMAP_THREAD1513:15] ERROR perf.sitemap logp.251 - java.sql.SQLException: Connection Cache with this Cache Name does not exist
java.sql.SQLException: Connection Cache with this Cache Name does not exist
at oracle.jdbc.pool.OracleConnectionCacheManager.purgeCache(OracleConnectionCacheManager.java:947)
at oracle.sysman.emSDK.core.util.jdbc.ConnectionCache.close(ConnectionCache.java:345)
CAUSE
Issue is due to the following bug:
Bug 28513706 - 13c2EM: DB home page shows Connection Cache with this Cache Name does not exist
SOLUTION
Perform the following steps on the OMS server as a work around until the Bug 28513706 has been fixed
1. <OMS_HOME>/bin/emctl set property -name use_pooled_target_connections -value false
1. <OMS_HOME>/bin/emctl set property -name use_pooled_target_connections -value false
2. Restart oms
<OMS_HOME>/bin/emctl stop oms -all
<OMS_HOME>/bin/emctl start oms
Note: We are facing the issue while using connection pooling. Disabling the parameter use_pooled_target_connections will just use traditional way to connect db. Connection pooling is an jdbc feature where connection are created as a pool and will be used.
REFERENCES
BUG:28513706 - 13C2EM: DB HOME PAGE SHOWS CONNECTION CACHE WITH THIS CACHE NAME DOES NOT EXISTNOTE:2308038.1 - 13c EM: Target db home page shows Failed to connect to the target database, Regions that pull real-time data from the database will not be displayed
NOTE:2338876.1 - EM13c : Exception while loading RAC Database Home Page. Connection Cache with this Cache Name does not exist
No comments:
Post a Comment