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

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.
SOLUTION
Check the alert log and Recovery Manager for Oracle log file for more details. Manually query
the cloned the database to see if there are any problems.
MESSAGE ID
1178
SYMBOLIC NAME
RMO_ERROR_GPFS_BKUPCONF
MESSAGE
33PAR1178: ERROR: Could not backup the configuration for GPFS file system '%s'.
REASON
During Oracle device discovery, the command mmbackupconfig failed to backup the specified
GPFS file system.
SOLUTION
Check if the file sysmte is valid or not, run with OS command directly and fix the reason caused
failure.
MESSAGE ID
1179
SYMBOLIC NAME
RMO_ERROR_ORAOWNER_NOTFOUND
190 Troubleshooting