Hello,
If you are receiving above error when accessing the DBConsole it is possible that there is some problem with EM repository.
It is always better to drop the em repository and deconfig all your database running in cluster or non-cluster mode.
Below are the steps that you can use.
If you are receiving above error when accessing the DBConsole it is possible that there is some problem with EM repository.
It is always better to drop the em repository and deconfig all your database running in cluster or non-cluster mode.
Below are the steps that you can use.
- emca -deconfig all db
Note: Above command will be used for all the ORACLE_SID running on the node and use below command for the last one.
- emca -deconfig all db -repos drop
- ORACLE_SID
- ORACLE_UNQNAME
- ORACLE_HOSTNAME
- ORACLE_HOME
- GRID_HOME
- emca -config dbcontrol db -repos create -cluster -EM_NODE_LIST dbnode1,dbnode2
- emca -config dbcontrol db -cluster -EM_NODE_LIST dbnode1,dbnode2
D:\app\n\product\11.2.0\dbhome_1\BIN>emca -deconfig all db
ReplyDeleteSTARTED EMCA at Jan 18, 2013 12:52:24 AM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: orcl
Do you wish to continue? [yes(Y)/no(N)]: y
Jan 18, 2013 12:52:30 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at D:\app\n\cfgtoollogs\emca\emca_2013_01_18_00_52_24.log.
Jan 18, 2013 12:52:30 AM oracle.sysman.emcp.EMConfig perform
SEVERE: Database instance unavailable.
Refer to the log file at D:\app\n\cfgtoollogs\emca\emca_2013_01_18_00_52_24.log for more details.
Could not complete the configuration. Refer to the log file at D:\app\n\cfgtoollogs\emca\emca_2013_01_18_00_52_24.log for more details.