HP 3PAR Application Software Suite for Oracle - Manual (Page 184)

RMO_ERROR_SET_PROTECTION_MODE
MESSAGE
3PAR1173: ERROR: Could not set the database protection mode to maximum performance.
REASON
After using the binary control file to clone a database, trying to set the protection mode to the
default maximum performance failed.
SOLUTION
Check the alert.log for detailed information.
MESSAGE ID
1174
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_EQUIVALENT_FPATH
MESSAGE
3PAR1174: ERROR: Could not retrieve the equivalent file path for <name> on the backup server.
REASON
During the process of rmora_createdb, if the ascii control file is chosen to clone the database,
Recovery Manager for Oracle needs to modify the ascii control file saved in the repository and
then replace the datafiles with the correct physical locations on the backup server, if the files are
on file systems. If Recovery Manager for Oracle failed to retrieve the corresponding datafiles on
the backup server, the error occurs.
SOLUTION
Check the mapping file in the repository to see if it contains the specified datafile, and check if
the file system for this datafile is mounted.
MESSAGE ID
1176
SYMBOLIC NAME
RMO_ERROR_RESTORE_CLONE_CFILE
MESSAGE
3PAR1176: ERROR: Could not restore control files for the clone database.
REASON
During the process of rmora_createdb, RMAN failed to restore the control file to the correct
location.
SOLUTION
Check the log file for more details.
MESSAGE ID
1177
SYMBOLIC NAME
RMO_ERROR_QUERY_CFILE
MESSAGE
3PAR1177: ERROR: Could not query the clone database for the control file's location.
REASON
During the process of rmora_createdb, the Oracle database is found to use OMF format. After
the database is mounted (using binary control file to clone) or created (using ascii control file to
clone), Recovery Manager for Oracle needs to retrieve the current control file location and put
them into the init.ora file. During this process, the SQL command failed.
184 Troubleshooting