After upgrading the Oracle database to 10.2.0.4 from 10.2.0.1, the EM console was not working and it throws errors when tried to start in command line. This error is generic to all platforms but we faced issues in Windows 2003 SP2 server after upgrading the Oracle database to 10.2.0.4.
Os Version – Windows 2008 SP2, Oracle 10g 10.2.0.4
We tried to recreate the EM console with emca utility but it eventually failed with the below errors,
2011-07-01 17:21:44 Thread-6752 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://PGDB.sstc.local:1158/em/upload/: retStatus=-12011-07-01 17:21:45 Thread-8296 ERROR ssl: Open wallet failed, ret = 28750,2011-07-01 17:21:45 Thread-8296 ERROR http: 1568: Error initializing SSL connection for incoming request, aborting request. Ret=-1
These errors will be created under the ORACLE_HOME/sysman/logs
"2011-07-01 17:21:44 Thread-6752 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://PGDB.sstc.local:1158/em/upload/: retStatus=-12011-07-01 17:21:45 Thread-8296 ERROR ssl: Open wallet failed, ret = 28750,2011-07-01 17:21:45 Thread-8296 ERROR http: 1568: Error initializing SSL connection for incoming request, aborting request. Ret=-12011-07-01 17:21:45 Thread-1820 ERROR ssl: Open wallet failed, ret = 28750
2011-07-01 17:21:45 Thread-1820 ERROR ssl: nmehlenv_openWallet failed
Followed the Oracle support note ( 1222603.1) to overcome the issue Enterprise Manager Database Control Configuration - Recovering From Errors Due to CA Expiry on Oracle Database 10[1][1].2.0.4 or 10.2.0.5 [1222603.1]
Go-through the given metalink note and apply the patch 8350262 to resolve the issue. Enterprise Manager Database Control Configuration - Recovering From Errors Due to CA Expiry on Oracle Database 10[1][1].2.0.4 or 10.2.0.5 Video.
No comments:
Post a Comment