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

MESSAGE ID
1101
SYMBOLIC NAME
RMO_ERROR_REMOVE_ORAASMDISK
MESSAGE
3PAR1101: ERROR: Could not delete oracleasm disk <disk ID>.
REASON
Failed to use the command oracleasmdeletedisk to delete the specified Oracle asmlib disk.
SOLUTION
Most likely the disk is still busy. Check the /var/log/oracleasm logfile for more information.
Make sure there are no other processes accessing this disk. Normally the +ASM instance could
still hold the resource. Shutting down/starting up the +ASM instance could resolve the issue. If
none of the above is successful, rebooting the backup server and running rmora_umount with
the -f option will resolve the problem.
MESSAGE ID
1102
SYMBOLIC NAME
RMO_ERROR_REDODG_NOTFOUND
MESSAGE
3PAR1102: ERROR: Redo log ASM disk group <name> not found.
REASON
When rmora_createdb tries to clone the database on the backup server, the following two cases
requires redo diskgroup precreated:
•
Using binary control files to recover the database, or
•
Specify the recovery location from the command line with one or more ASM disk groups,
however one or more diskgroups cannot exist or must not be mounted.
SOLUTION
Create and mount the ASM disk group for redo logfiles on the backup server.
MESSAGE ID
1103
SYMBOLIC NAME
RMO_ERROR_CREATE_VC_NOTALLOWED
MESSAGE
3PAR1103: ERROR: virtual copy creation is not allowed for database <name>.
REASON
The VCDBA_MAXVC is set to a negative number.
SOLUTION
Run rmora_config or the GUI application to modify the configuration file to set VCDBA_MAXVC
to a positive number, which cannot exceed 500. Also make sure the VCEXPIRATION parameter
is not enabled (it should be set to 0d or 0h), otherwise the time-based policy will be in effect.
MESSAGE ID
1104
Symbolic Name
RMO_ERROR_MAXVC_ALLOWED
148 Troubleshooting