ADMN-705021Just run %ORACLE_HOME%\dcm\bin\dcmctl shutdown and retry the patch.
The configuration files for this Oracle Application Server instance are inconsistent with the
configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem with the configuration on the filesystem is resolved. This condition arises when a prior operation was unsuccessful. The exception associated with this failed operation is:
{0}
. Please also check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk. Some possible causes are:
* permissions on files
* file contention issues on Windows NT
* internal Oracle error
After resolving the problem that prevented DCM from updating the configuration
files, you may use the dcmctl resyncInstance command to resolve the problem.
Alternatively, you can stop and then restart the active dcmctl or EMD
process and resyncInstance will automatically be performed.
Resolution:
Base Exception:
Transaction failed in Plugin cannot rename old configuration file:e:\OMS\oms10g\diagnostics\config\logloader.xml.
Resolution:
Transaction failed in Plugin.
Tuesday, January 26, 2010
Patching OMS to 10.2.0.5 problem
When patching to OMS 10.2.0.5 on Windows, this error encountered:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment