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

SYMBOLIC NAME
RMO_ERROR_PHYSDEV_NOTFOUND
MESSAGE
3PAR1182: ERROR: Could not find device '%s'.
REASON
Failed to retrieve the OS device used by the database while executing rmora_create or
rmora_rsync
.
SOLUTION
Check the log file from both the database server and the backup system to find out more information.
Contact customer support for further investigation.
MESSAGE ID
1183
SYMBOLIC NAME
RMO_ERROR_CONNECT_TO_HOST
MESSAGE
3PAR1183: ERROR: Could not connect (ssh) to host .
REASON
Recovery Manager for Oracle requires SSH configuration from the database server, backup system,
alternative backup system (if applicable), NetBackup server (if applicable), and HP 3PAR StoreServ
Storage system.
SOLUTION
Follow the instructions in the HP 3PAR Recovery Manager for Oracle User Guide to configure the
SSH connection.
MESSAGE ID
1186
SYMBOLIC NAME
RMO_ERROR_CONNECT_TO_RMANCAT
MESSAGE
3PAR1186: ERROR: Could not verify RMAN Catalog configuration from host .
REASON
rmora_checkconfig failed to use the credentials provided during configuration to connect to
the ORACLE RMAN catalog from the database server or the backup system.
SOLUTION
Verify if the credential provided during configuration is valid. Make sure the catalog database is
up and running and the listener is up and running. Manually test the connectivity if possible.
MESSAGE ID
1191
SYMBOLIC NAME
RMO_ERROR_CREATE_CLONE_PFILE
MESSAGE
3PAR1191: ERROR: Could not create Oracle parameter file for the clone database.
REASON
During the process of rmora_createdb, Recovery Manager for Oracle failed to generate
init.ora
to clone the database.
171