An exception has occurred while accessing DCM repository. Please refer to the accompanying base exception for more details.
Resolution:
check the details of the base exception.
Base Exception:
The DCM farm or an instance in the farm could not be found. This generally happens when an Oracle Application Server instance has inadvertently been removed from the farm.
Resolution:
The repository may need to be restored from a backup. Please refer to DCM reference guide or call Oracle Support for more information.
FIX:
Metalink:DocID 753917.1[@more@]
All Dcmctl Commands Fail With ADMN-202001 "DCM farm or an instance in the farm could not be found" [ID 753917.1]
In this Document
Symptoms
Changes
Cause
Solution
Applies to:
Oracle Application Server 10g Enterprise Edition - Version: 10.1.2.0.2 to 10.1.2.3.0This problem can occur on any platform.
Checked for relevance on 20-May-2009
Symptoms
For an Oracle Application Server 10g middle-tier which is associated with an infrastructure instance, all dcmctl commands (ie. 'dcmctl getstate -v -d' or 'dcmctl updateconfig') fail with the following errors :-
ADMN-202001
An exception has occurred while accessing DCM repository. Please refer to the accompanying base exception for more details.
Resolution:
check the details of the base exception.
Base Exception:
The
DCM farm or an instance in the farm could not be found. This generally
happens when an Oracle Application Server instance has inadvertently
been removed from the farm.
Resolution:
The repository may need to
be restored from a backup. Please refer to DCM reference guide or call
Oracle Support for more information.
Changes
The $ORACLE_HOME/dcm/config/dcm.conf file looks like the following:
repository_type=db
instance_id=
cluster_id=
instance_name=
cluster_name=
cluster_name=standalone
cluster_id=1
instance_name=standalone
instance_id=1
The $ORACLE_HOME/dcm/config/dcm.conf.bak shows the following :-
repository_type=db
instance_id=
cluster_id=
instance_name=
cluster_name=
Cause
The following four extra lines in the $ORACLE_HOME/dcm/config/dcm.conf file are causing the dcmctl commands to fail:
cluster_name=standalone
cluster_id=1
instance_name=standalone
instance_id=1
It has not been determined why the dcm.conf file has changed from the original dcm.conf.bak file; this is unknown.
Solution
1. Rename the existing dcm.conf file:cd $ORACLE_HOME/dcm/config
mv dcm.conf dcm.conf.bad
2. Copy the dcm.conf.bak to dcm.conf
cd $ORACLE_HOME/dcm/config
cp dcm.conf.bak dcm.conf
3. Stop/Start the Oracle Application Server middle-tier instance :
cd $ORACLE_HOME/opmn/bin
opmnctl stopall
opmnctl startall
4. Run a dcmctl command to confirm it works now:
cd $ORACLE_HOME/dcm/bin
dcmctl getstate -v -d
5. Update the repository with latest configuration changes:
cd $ORACLE_HOME/dcm/bin
dcmctl updateconfig -force