21 Troubleshooting the Backup and Recovery Tool

This chapter describes common problems that you might encounter when using the Backup and Recovery Tool and explains how to solve them. It contains the following topic:

Problems and Solutions

21.1 Problems and Solutions

This section describes common problems and solutions. It contains the following topics:

Receiving restore_config Operations Fails Error
File-based Repository Restoration Fails
Cannot Run a Cold Backup on Identity Manager or J2EE Instance

21.1.1 Receiving restore_config Operations Fails Error

A restore_config operation fails.

Problem

A restore_config operation fails with the following error:

C:\OracleAS\IM_1128/dcm/bin/dcmctl.bat applyarchiveto -archive 
2004-11-29_11-23-18 -script 

ADMN-906025 
Base Exception:
The exception, 100999, occurred at Oracle Application Server instance 
"im_1128.stajx14.us.oracle.com"
"See base exception for details.See base exception for details."
Resolution:
Resolve the indicated problem at the Oracle Application Server instance where
it occurred then resync the instance
java.lang.Exception: Could not delete file
C:\OracleAS\IM_1128\j2ee\OC4J_SECURITY\application-
deployments\wirelesssso\jazn-data.xml. Please check file permissions.
at oracle.security.jazn.smi.JAZNPlugin.commit(Unknown Source)
at oracle.ias.sysmgmt.repository.DcmPlugin.commit(Unknown Source)

Solution

If you see error similar to "Could not delete file jazn-data.xml", execute the following steps:

Stop all the OC4J processes using the following command:

ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J

Rerun the restore_config operation.

21.1.2 File-based Repository Restoration Fails

A file-based repository restoration fials.

Problem

File based repository restoration fails with the error indicating that the dcm daemons across the farm could not be restarted.

C:\fbfhost\backup_restore>bkp_restore.bat -m restore_repos -t 
2004-12-07_13-49-13 
 
C:\fbfhost\backup_restore>echo off 
Stopping dcm-daemon across the farm ... 
Importing file based repository ... 
Restarting dcm-daemon across the farm ... 
  Problem running command (Returned 150) 
  c:\fbfhost/opmn/bin/opmnctl @farm restartproc ias-component=dcm-daemon 
The file based repository has been restored. 
But, dcm daemons across farm could not be restarted. 
Please take the appropriate action. 
See c:\logs/2004-12-07_13-50-18_restore_repos.log for more info

Solution

At this point, the file based repository has been restored successfully. Now, perform the following steps on the repository host:

Stop the dcm-daemon process on the file based repository host:

ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=dcm-daemon

Start the dcm-daemon processes across farm:

ORACLE_HOME/opmn/bin/opmnctl @farm startproc ias-component=dcm-daemon

21.1.3 Cannot Run a Cold Backup on Identity Manager or J2EE Instance

You cannot run a cold backup on Identity Manager or J2EE instance.

Problem

When backup_cold is attempted on IM or J2EE instance, the following error message is displayed:

C:\Product\OracleAS\SSO_1203\backup_restore>bkp_restore.bat -v -m backup_cold 
 
 C:\Product\OracleAS\SSO_1203\backup_restore>echo off 
   ======================================== 
 Running command: 
 C:\Product\OracleAS\SSO_1203/dcm/bin/dcmctl.bat whichfarm -v -script >> 
 C:\Product\OracleAS\SSO_1203\backups\log_path/2004-12-09_03-56-55_whichfarm.log 
 C:/Product/OracleAS/SSO_1203/backup_restore/config/config.inp: Invalid 
 'database backup_path' specified 
 VALUE_NOT_SET - No such file or directory 
 Consider using '-f' to force creation of this path 
 Failure: backup_cold failed

Solution

The backup_cold operation should only be used on the repository hosts - Metadata Repository instance and/or any instance hosting a file-based repository.

21.1.4 Failure Due to Loss or Corruption of OPMN.XML File

The loss or corruption of the opmn.xml file is causing a failure.

Problem

The loss or corruption of the opmn.xml file caused the following error:

ADMN-906025 
Base Exception:
The exception, 100999, occurred at Oracle Application Server instance
"J2EE_1123.stada07.us.oracle.com"

Resolution

Perform the following steps to restore the opmn.xml file:

Run

bkp_restore.bat -m restore_config -t <timestamp>

If that command fails, stop the OC4J processes.

Rerun

bkp_restore.bat -m restore_config -t <timestamp>

21.1.5 A restore_config Operation Fails

A restore_config operation fails or the ORACLE_HOME/j2ee/OC4J_SECURITY directory is deleted.

Problem:

The ORACLE_HOME/j2ee/OC4J_SECURITY directory is accidently deleted or a restore_config operation fails with the following error:

ADMN-906025 
Base Exception:
The exception, 806212, occurred at Oracle Application Server instance
"OID.stada07.us.oracle.com"
"OPMN Request: /start?mode=sync&process-type=OC4J_SECURITY

OPMN Response: HTTP/1.1 204 No Content
Content-Length: 724 
Content-Type: text/html
Response: 0 of 1 processes started.
.
<?xml version='1.0' encoding='US-ASCII'?> 
<response>
<opmn id="stada07:6200" http-status="204" http-response="0 of 1 processes started.">
  <ias-instance id="OID.stada07.us.oracle.com">
    <ias-component id="OC4J"> 
      <process-type id="OC4J_SECURITY">
        <process-set id="default_island"> 
          <process id="511967353" pid="956" status="Init" index="1"
log="C:\Product\OracleAS\OID\opmn\logs\OC4J~OC4J_SECURITY~default_island~1"
.
operation="request" result="failure"> 
        <msg code="-21" text="failed to start a managed process after the maximum retry limit">

Solution:

To resolve this problem, run the following command:

On UNIX systems:

bkp_restore.sh -m restore_config -F DCM-resyncforce

On Windows systems:

bkp_restore.bat -m restore_config -F DCM-resyncforce