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

3PAR1080: ERROR: Failed to retrieve the retention/expiration time for Virtual Copy <name>.
REASON
Failed to retrieve the retention and/or expiration time from the HP 3PAR storage system for the
specified virtual copy.
SOLUTION
Make sure all parameters in the configuration file are up to date. Make sure the HP 3PAR storage
system is functioning properly. Contact customer support for further investigation.
MESSAGE ID
1087
SYMBOLIC NAME
RMO_ERROR_WRONG_VC_CLONE
MESSAGE
3PAR1087: ERROR: Database '%s' was not started using the virtual copy <name>.
REASON
Executing rmora_removedb failed as the file indicating the virtual copy is being used for cloning
the database does not exist.
SOLUTION
Make sure the specified virtual copy is currently cloned, or make sure the specified virtual copy is
the one that needs to be used to remove the cloned database.
MESSAGE ID
1090
SYMBOLIC NAME
RMO_ERROR_RESET_OCFS2_DEV
MESSAGE
3PAR1090: ERROR: Could not reset uuid for OCFS2 device <device>.
REASON
Failed to reset the UUID for an OCFS device on the backup server during an rmora_mount
operation.
SOLUTION
Contact customer support for further investigation.
MESSAGE ID
1096
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_REDOLOG
MESSAGE
3PAR1096: ERROR: Could not retrieve location of the redo logs from <file name>.
REASON
Trying to clone a database failed because the redo log information cannot be found in the ascii
control file.
SOLUTION
Check the original database and manually create an ascii control file to make sure it contains
correct redo log information. The virtual copy, which will be used for clone, may be corrupted, or
there could be some strange characters which prevent the parser from parsing the ascii control file
correctly. Try using a different virtual copy, or modify the ascii control file in the repository to
include the redo log information. Contact customer service for further investigation.
146 Troubleshooting