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

When running rmora_createdb to clone the database on the backup server using the binary
control file, and if the original datafiles/archive log destinations are symbolic links,
rmora_createdb
will try to create the links to point to the virtual copy, and the operation failed.
SOLUTION
Make sure the user running rmora_createdb has the correct permission to create the symbolic
links. Check the log file for more details.
REASON
Trying to clone a database using the specified virtual copy failed in the following cases:
•
Cloning using a binary control file, and
•
The original databases and/or archive log destinations are symbolic links.
•
Trying to create the symbolic link on the backup server failed.
SOLUTION
Check the log file for more details. Manually create the symbolic links to see if it works or not. If
not, check the OS for further solutions.
MESSAGE ID
1143
SYMBOLIC NAME
RMO_ERROR_RCVV_NOTFOUND
MESSAGE
3PAR1143: ERROR: Virtual volume <name> is not in any Remote Copy group.
REASON
The volume used by the Oracle database, which belongs to either datafiles or archive log
destinations, could not be found in any Remote Copy groups.
SOLUTION
Add the volume to the appropriate Remote Copy group.
MESSAGE ID
1144
SYMBOLIC NAME
RMO_ERROR_2ORMORE_DATA_RCGROUPS
MESSAGE
3PAR1144: ERROR: Datafile volumes belong to more than one Remote Copy groups.
REASON
To support remote copy, Recovery Manager for Oracle requires the following:
•
All datafiles are in one Remote Copy group and all archive log destinations are in a second
remote copy group. This is a recommended group setup; or
•
All datafiles and archive log destinations belong to one Remote Copy copy.
•
If synchronous long distance Remote Copy is configured, all redo logfiles and control files
should be in separate Remote Copy groups from the datafiles and archive log destinations.
SOLUTION
Rearrange the Remote Copy groups used by the database accordingly.
MESSAGE ID
1145
SYMBOLIC NAME
157