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

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
1188
SYMBOLIC NAME
RMO_ERROR_NBUSCHEDS_NOTFOUND
MESSAGE
3PAR1188: ERROR: Could not retrieve the NBU schedule for policy '%s'.
REASON
During configuration, Recovery Manager for Oracle failed to retrieve the schedule name for the
specified policy name.
SOLUTION
Make sure the necessary schedule is created for the specified policy name.
MESSAGE ID
1189
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_ORAOWNER
MESSAGE
3PAR1189: ERROR: Failed to retrieve Oracle (or ASM) binary owner from host .
REASON
On the specified host, for the given Oracle home parameter value from the configuration file, the
operation failed to retrieve the ownership of the file $ORACLE_HOME/bin/oracle.
SOLUTION
Check if the $ORACLE_HOMEvalue in configuration file is correct. Make sure the $ORACLE_HOMEis
accessible.
MESSAGE ID
1191
SYMBOLIC NAME
RMO_ERROR_CREATE_CLONE_PFILE
MESSAGE
3PAR1191: ERROR: Could not create Oracle parameter file for the clone database.
192 Troubleshooting