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

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
MESSAGE
3PAR1104: ERROR: The number of Virtual Copies has exceeded the maximum of <value>.
REASON
The maximum number of Virtual Copies specified in configuration file is reached.
SOLUTION
Either remove one or more Virtual Copies, or increase the number in the configuration file by
running rmora_config or the GUI to modify the configuration. If you choose the option to remove
the oldest Virtual Copy when maximum number is reached during configuration, Recovery Manager
for Oracle will automatically remove the oldest Virtual Copy.
MESSAGE ID
1105
SYMBOLIC NAME
RMO_ERROR_DISCOVER_DEV
MESSAGE
3PAR1105: ERROR: Could not discover devices used by database <name>.
REASON
Recovery Manager for Oracle failed to retrieve the devices used by datafiles and/or archive log
destinations.
SOLUTION
Make sure datafiles and archive log destinations are on separate HP 3PAR volumes and make
sure the file system type is supported by Recovery Manager for Oracle (refer to the HP 3PAR
configuration matrix). Check log files from both the database server and the backup system. The
immediate preceding error message may indicate the reason for the failure. If none of the reveals
the failure reason, contact customer support for further investigation.
MESSAGE ID
1106
SYMBOLIC NAME
RMO_ERROR_OPEN_DEVICE
MESSAGE
3PAR1106: ERROR: Could not open device <device ID>.
REASON
System call open() failed for the specified device.
SOLUTION
Check if the device exists and has correct permissions. Contact customer support for further
investigation.
MESSAGE ID
1107
169