19 Troubleshooting OracleAS Recovery Manager

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

• Problems and Solutions

19.1 Problems and Solutions

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

• Receiving Missing Files Messages During restore_config Operation

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

• Timeout Occurs While Trying to Stop Processes Using the "opmnctl stopall" Command

19.1.1 Receiving Missing Files Messages During restore_config Operation

A restore_config operation generates missing file messages.

Problem

During a restore_config operation, you receive messages indicating that files are missing, for example:

Could not copy file C:\Product\OracleAS\Devkit_1129/testdir/ to 
C:\Product\OracleAS\Devkit_1129\backup_restore\cfg_bkp/2006-12-01_03-26-22.

Solution

During a restore_config operation, a temporary configuration backup is taken so that, if the restore fails, the temporary backup can be restored, returning the instance to the same state as before the restore.

If some files are deleted (including file or directories specified in config_misc_files.inp) before a restore operation, then, during the temporary backup, messages are displayed indicating that certain files are missing. These error or warning messages should be ignored since the missing files are restored as part of the restore_config operation.

19.1.2 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.stad.oracle.com"

Resolution

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

1. Run the following command:

   bkp_restore.bat -m restore_config -t timestamp
   
   

2. If that command fails, stop the OC4J processes.

3. Rerun the following command:

   bkp_restore.bat -m restore_config -t timestamp
   

19.1.3 Timeout Occurs While Trying to Stop Processes Using the "opmnctl stopall" Command

During backup_instance_cold, backup_instance_cold_incr, and restore_instance operations, a timeout may occur while trying to stop processes using the opmnctl stopall command.

Problem:

During some operations involving the backup or restore of a server instance, a timeout may occur while trying to stop processes using the opmnctl stopall command. This can occur because of heavy machine load or a process taking a long time to shut down. Under these conditions, you may receive an error message similar to the following:

Oracle Application Server instance backup failed.
Stopping all opmn managed processes ... 

Failure : backup_instance_cold_incr failed 

Unable to stop opmn managed processes !!! 

Solution:

Running opmnctl stopall a second time should resolve this problem.