HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

MESSAGE
3PAR1162: ERROR: ASM rebalancing operation is in progress.
REASON
Before Recovery Manager for Oracle creates a Virtual Copy for the datafile volumes and/or
archivelog destination volumes that reside on ASM disk groups, Recovery Manager for Oracle
discovers an ASM rebalance operation is in progress.
SOLUTION
Wait until the rebalance operation finishes, or stop the rebalance temporarily.
MESSAGE ID
1163
SYMBOLIC NAME
RMO_ERROR_VC_BACKUP_EXIST
MESSAGE
3PAR1163: ERROR: The Virtual Copy <Virtual Copy name> has been backed up.
Use the -f option to force the removal of the Virtual Copy's repository.
REASON
If a Virtual Copy is backed up to media using either NetBackup or RMAN, the Virtual Copy is
marked. The repository can only be removed with the -f option. This is to avoid removing the
repository accidently. The Virtual Copy can be used by rmora_restore to restore the database.
If the repository is removed, it is not possible to perform rmora_restore.
SOLUTION
Make sure you really do not need the backup image and then use the -f option to remove the
repository.
MESSAGE ID
1164
SYMBOLIC NAME
RMO_ERROR_SET_RETENTEXP
MESSAGE
3PAR1164: ERROR: Could not set retention/expiration for Virtual Copy <Virtual Copy name>.
REASON
Using rmora_set to set the retention time and/or expiration time for the specified Virtual Copy
failed.
SOLUTION
Check the screen output and log files for more information. Check the system by issuing showsys
-param and the maximum domain limit by issuing showdomain -d for the maximum allowed
retention time. Retention times and expiration times are available from HP 3PAR OS version 2.3.1
or later. Expiration time should be larger than retention time.
MESSAGE ID
1166
SYMBOLIC NAME
RMO_ERROR_REMOVE_DB_REPT
MESSAGE
3PAR1166: ERROR: Could not remove the repository for database <database name>.
REASON
187