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

3PAR1007: ERROR: Cannot determine archive log mode for database .
REASON
Failed to retrieve the archive log mode for the specified database.
SOLUTION
Manually log onto the database and check if the database is running normally. Most likely, either
the database is not open or the archive log destination is full, which could cause the database to
hang.
MESSAGE ID
1008
SYMBOLIC NAME
SymbolicName = RMO_ERROR_ORAHOME_BACKUP
MESSAGE
3PAR1008: ERROR: Oracle binary location on the backup server is required. Use configure utility
to generate a new configuration file.
REASON
When running the command rmora_createdb, the Oracle binary is required for database clone
or database backup via Oracle RMAN.
SOLUTION
Install the same version of the Oracle software on the backup server and run rmora_config to
specify the Oracle home on the backup server. An updated configuration file will be generated.
Rerun rmora_createdb after the change.
MESSAGE ID
1009
SYMBOLIC NAME
SymbolicName = RMO_ERROR_FSTAT
MESSAGE
3PAR1009: ERROR: Could not stat file/directory .
REASON
Failed to get the file or directory status.
SOLUTION
Check if the specified file or directory exists. Check the context for more information.
MESSAGE ID
1011
SYMBOLIC NAME
RMO_ERROR_ORAASM_DISK_NOTSUPPORT
MESSAGE
3PAR1011: ERROR: Oracle asmlib is not supported in this OS release.
REASON
In Red Hat 6.x release, devices using Oracle asmlib is not supported.
SOLUTION
Change to use Recovery Manager supported devices.
MESSAGE ID
1012
161