| ETERNUS SF Recovery Manager for Oracle EE 13.0.1 User's Guide - Solaris(TM) Operating System - |
|
Contents
|
This chapter explains the message which Recovery Manager for Oracle outputs. And the solution of a trouble generated in Recovery Manager for Oracle is explained.
Message
Data required in order to solve a trouble
A solution when a trouble occurs
(The message text is described.)
(The semantics of a message is described.)
(The semantics of a parameter is described when a parameter is displayed.)
(Dispensation of a system is described when a message is outputted.)
(When a message is outputted, the disposition which the system administrator's performs is described.)
An input parameter contains an error.[PARAMETER]
The input parameter is incorrect.
PARAMETER: Parameter character string
Exits the application
Specify the input parameter correctly.
The configuration file could not be obtained. [FILENAME]
Either the configuration file is not located or parameters assigned to the configuration file contain an error.
FILENAME: Configuration setup file name
Exits the application
Amend the output configuration file correctly.
An error is contained in the "rmfo_system.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_syspw.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_node.ini" setting [PARAMETER]
Parameters assigned to "rmfo_node.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_bkcom.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_bkcom.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_bkdbf.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_bkdbf.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_bkctl.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_bkctl.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_arch.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_arch.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_bkarch.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_bkarch.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_catalog.ini" setting. [PARAMETER]
Parameters assigned to "rmfo_catalog.ini" contain an error.
PARAMETER: Incorrect parameter
Exits the application
Amend the output parameter correctly.
An error is contained in the "rmfo_syspw.ini" setting.
A password assigned to "rmfo_syspw.ini" contains an error.
Nothing
Exits the application
Set the password before it is encrypted.
The password could not be encrypted.
A password assigned to "rmfo_syspw.ini" contains an error.
Nothing
Exits the application
Set the password before it is encrypted.
The password could not be decrypted.
The password assigned to "rmfo_syspw.ini" could not be decrypted.
Nothing
Exits the application
Confirm that "rmfo_syspw.ini" has been located. Alternatively, confirm that the password has been correctly encrypted.
This product is not installed on the remote host. [HOSTNAME]
The directory of this product cannot be found on the remote host.
HOSTNAME: Host name
Exits the application
Confirm that this product has been installed on the remote host. Confirm also that the cluster software is operating correctly.
The directory could not be created on the remote host. [HOSTNAME]
An error was generated while creating the working directory for the remote host.
HOSTNAME: Host name
Exits the application
Confirm that the disk where the product directory is located on the remote host has free space. Confirm also that the cluster software is operating correctly.
The file could not be sent to the remote host. [HOSTNAME:FILENAME]
An error was generated while sending the configuration file to the remote host.
HOSTNAME: Host name
FILENAME: Configuration setup file name
Exits the application
Confirm that the disk where the product directory is located on the remote host has free space. Confirm also that the cluster software is operating correctly.
The host name could not be obtained.
The host name could not be obtained.
Nothing
Exits the application
Check the environment.
The recovery catalog database could not be created.
An error was generated while creating the RMAN recovery catalog database.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The recovery catalog database could not be deleted.
An error was generated while deleting the RMAN recovery catalog database.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The recovery catalog database of the same name has been located.
When the RMAN recovery catalog database has already been located, an attempt was made to create the same database again.
Nothing
Exits the application
Delete the RMAN recovery catalog database, and re-execute.
After deleting the recovery catalog database, the backup history file could not be deleted. [DIR_NAME]
The backup history file could not be deleted.
DIR_NAME: Backup history directory name
Exits the application
Delete the displayed directory manually.
After deleting the recovery catalog database, the backup history file of the other node could not be deleted. [HOSTNAME:DIR_NAME]
The backup history file of other nodes (host) could not be deleted.
HOSTNAME: Host name
DIR_NAME: Backup history directory name
Exits the application
Manually delete the directories of displayed and other nodes.
An unexpected error was generated while executing the program.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
The backup volume could not be unmounted.
The backup volume could not be unmounted.
Nothing
Exits the application
Check the execution log file, and manually unmount the volume that could not be unmounted.
The external command could not be executed.
External commands including the ACM command and Oracle operation command could not be executed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The file could not be read.
Files including temporary files could not be manipulated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The file could not be written to.
Files including temporary files could not be manipulated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The command execution file could not be created. (ROOT)
The command execution file could not be manipulated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The command execution file could not be created. (ROOTSH)
The command execution file could not be manipulated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The command execution file could not be created. (RMANS)
The command execution file could not be manipulated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The command execution file could not be created. (ENV)
The command execution file could not be manipulated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The recovery catalog database could not be activated.
The RMAN recovery catalog database could not be activated.
Nothing
Exits the application
Check the alert log of the RMAN recovery catalog database. Remove the cause of the error, and confirm that the system can be activated normally.
The recovery catalog database could not be terminated.
The RMAN recovery catalog database could not be terminated.
Nothing
Exits the application
Check the alert log of the RMAN recovery catalog database. Remove the cause of the error, and terminate the database.
The listener for recovery catalog database could not be activated.
The RMAN recovery catalog database listener could not be activated.
Nothing
Exits the application
Check the listener log ($ORACLE_HOME/network/log), remove the cause of the error, and confirm that the system can be activated normally.
The listener for recovery catalog database could not be terminated.
The RMAN recovery catalog database listener could not be terminated.
Nothing
Exits the application
Check the listener log ($ORACLE_HOME/network/log) confirm that the system can be terminated normally.
The environment information could not be read. (Basic Information)
The configuration file could not be read (rmfo_system.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Password)
The configuration file could not be read (rmfo_syspw.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Common Backup Information)
The configuration file could not be read (rmfo_bkcom.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Data File Information)
The configuration file could not be read (rmfo_bkdbf.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Control File Information)
The configuration file could not be read (rmfo_bkctl.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Archived Redo Log Information)
The configuration file could not be read (rmfo_bkarch.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Recovery Catalog Database Information)
The configuration file could not be read (rmfo_catalog.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (Node List)
The configuration file could not be read (rmfo_node.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The environment information could not be read. (RAC Archived Redo Log Information)
The configuration file could not be read (rmfo_arch.ini).
Nothing
Exits the application
Confirm that the configuration file has been located and that the configuration has been set up correctly.
The database status is abnormal. (Instance)
A normal instance is not located.
Nothing
Exits the application
Activate the instance of the target database.
Alternatively, confirm that the target database is normal.
If not normal, recover normal status.
The database status is abnormal. (ARCHIVELOG mode)
Operation is not in the ARCHIVELOG mode.
Nothing
Exits the application
Change so that the target database is in the ARCHIVELOG mode.
Alternatively, confirm that the target database is normal.
If not normal, recover normal status.
The database status is abnormal. (Database)
The status of the target database is abnormal.
Nothing
Exits the application
Confirm that the target database is normal.
If not normal, recover normal status.
An invalid backup mode has been selected.
A function specified in the configuration as invalid in the backup mode, was executed.
Nothing
Exits the application
A function not valid in backup mode that is specified in the configuration was executed. Alternatively, the configuration contains an error.
Confirm that the execution details are correct or that the configuration contains no errors.
The execution permission could not be granted.
The permission for either the temporary file or the directory could not be granted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The tape backup shell script could not be executed.
An error was generated while executing the tape backup shell script specified by the administrator.
Nothing
Exits the application
Confirm that the tape backup shell script is correct.
Expired archived redo log files could not be deleted.
The archived redo log has exceeded its storage period and could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup database could not be initialized.
The backup set could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The data file could not be backed up.
The data file could not be backed up by RMAN.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The control file could not be backed up.
The control file could not be backed up by RMAN.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The archived redo log could not be backed up.
The archived redo log could not be backed up by RMAN.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup set for the data file could not be deleted.
The backup set has exceeded its storage period and could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup set of the control file could not be deleted.
The backup set has exceeded its storage period and could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup set of archived redo log could not be deleted.
The backup set has exceeded its storage period and could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup execution log could not be deleted.
The backup execution log has exceeded its storage period and could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The recovery execution log could not be deleted.
The recovery execution log has exceeded its storage period and could not be deleted.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup history file could not be created.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup history file could not be initialized.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup history file could not be updated.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup history file could not be updated.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup working file could not be read.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup working file could not be written to.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup working file could not be read.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup working file could not be written to.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
An error was generated while executing JDBC.
The start/end Oracle access processing has failed.
Nothing
Exits the application
Confirm that the Oracle configuration has been set up correctly.
The redo log sequence number could not be obtained.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Backup start time for the archived redo log could not be obtained.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The recovery catalog database could not be backed up.
The RMAN recovery catalog database could not be backed up.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Execution of the backup command ended abnormally.
The RMAN recovery catalog database could not be backed up.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The data file list could not be read.
A failure has occurred in the get database configuration information processing.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Database SID cannot be obtained.
"ORACLE_SID" could not be obtained by the node during the backup operation in the cluster operation.
Nothing
Exits the application
Confirm that the cluster node configuration file is normal.
Check the execution log. Remove the cause of the error, and re-execute.
The backup history file could not be read.
The backup history management processing failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The tablespace information could not be obtained.
A failure has occurred in the get database configuration information processing.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Temporary tablespace information could not be obtained.
A failure has occurred in the get database configuration information processing.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Temporary tablespace information is not located.
No temporary tablespace (TEMPFILE) is located in the database where the backup operation was attempted.
Nothing
Exits the application
Only the database with a minimum of one temporary tablespace volume (TEMPFILE) can be backed up.
Create a temporary tablespace.
The backup pre-process script could not be created.
A failure has occurred in the database backup operation.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup post-process script cannot be created.
A failure has occurred in the database backup operation.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup pre-process script is not located.
A failure has occurred in the database backup operation.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup post-process script cannot be located.
A failure has occurred in the database backup operation.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup pre-process script could not be executed.
A failure has occurred in the database backup operation.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup post-process script could not be executed.
A failure has occurred in the database backup operation.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Backup device information could not be generated.
The environment information setup has failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
Device data for the recovery catalog database could not be generated.
The environment information setup has failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The backup device information could not be located.
The environment information setup has failed.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The specified device cannot be found.
The device (volume) specified in the data file backup information cannot be found.
Nothing
Exits the application
Confirm that the device has been set correctly in the data file backup information.
A data file not backed up exists on the database.
A data file not defined for backup in the data file back up information, is located in the target database.
Nothing
Exits the application
Confirm that the data file is set correctly in the the data file backup information to avoid any backup omission.
The advanced copy function ended abnormally. (HistDel)
History could not be deleted during the OPC or EC backup processing.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
Alternatively, confirm that the ACM configuration has been set up correctly.
The advanced copy function ended abnormally. (Backup)
The backup operation could not be started during the OPC or EC backup processing.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
Alternatively, confirm that the ACM configuration has been set up correctly.
The advanced copy function ended abnormally. (BackStat)
The backup execution information could not be obtained by the OPC backup processing.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
Alternatively, confirm that the ACM configuration has been set up correctly.
The advanced copy function is being executed.
The OPC or EC backup processing was executed while restoring OPC, but processing failed.
Nothing
Exits the application
Wait for the OPC restore operation to end, and re-execute.
The OPC physical copy end could not be completed.
The OPC backup status could not be obtained while waiting for OPC physical copy to end.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The advanced copy function ended abnormally. (SyncStat)
Backup execution information could not be obtained during the EC backup processing.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
Alternatively, confirm that the ACM configuration has been set up correctly.
The status of the advanced copy function is abnormal.
A contradiction was generated in the EC backup processing sequence.
Nothing
Exits the application
Confirm the status from the ACM backup management screen.
Remove the cause of the error, recover normal status, and re-execute.
Alternatively, confirm that the ACM configuration has been set up correctly.
The status of the advanced copy function is abnormal.
The processing failed because the ACM status could not be confirmed.
Nothing
Exits the application
Confirm the status from the ACM backup management screen.
Remove the cause of the error, recover normal status, and re-execute.
Alternatively, confirm that the ACM configuration has been set up correctly.
The advanced copy function ended abnormally. (Backup Suspend)
The backup volume could not be suspended during the EC backup processing.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
Alternatively, confirm that the ACM configuration has been set up correctly.
The advanced copy function ended abnormally. (StartSync)
Synchronous starting of the backup volume during the EC backup processing failed.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
Alternatively, confirm that the ACM configuration has been set up correctly.
The backup device could not be synchronized.
Failed to execute EC synchronous processing.
Nothing
Exits the application
Confirm the status from the ACM backup management screen.
Remove the cause of the error, recover normal status, and re-execute.
Alternatively, confirm that the ACM configuration has been set up correctly.
The RMAN recovery catalog database volume could not be mounted.
The RMAN recovery catalog database volume could not be mounted.
Nothing
Exits the application
Confirm that the RMAN recovery catalog database information has been set correctly.
The RMAN recovery catalog database volume could not be unmounted.
The RMAN recovery catalog database volume could not be unmounted.
Nothing
Exits the application
Confirm the status from the ACM backup management screen.
Remove the cause of the error, recover normal status, and re-execute.
Alternatively, confirm that the ACM configuration has been set up correctly.
The backup volume for the control files and archived redo log, could not be mounted.
The backup volume for the control files and archived redo log, could not be mounted.
Nothing
Exits the application
Confirm that the backup volume information for the control files and the archived redo log have been set correctly.
The backup volume for the control files and archived redo log, could not be unmounted.
The backup volume for the control files and archived redo log, could not be unmounted.
Nothing
Exits the application
The backup volume information for the control files and archived redo log may not be set correctly. Check the status of the volume.
The archive output volume of the cluster node could not be mounted.
The archive output volume of the cluster node could not be mounted.
Nothing
Exits the application
Confirm that the cluster node information and RAC archive output volume information are set correctly.
Alternatively, confirm that the cluster configuration or the network setup have been made correctly..
The archive output volume of the cluster node could not be unmounted.
The archive output volume of the cluster node could not be unmounted.
Nothing
Exits the application
Confirm that the cluster node information and RAC archive output volume information are set correctly.
Alternatively, confirm that the cluster configuration or the network setup have been made correctly..
The ACM volume could not be mounted.
The ACM volume could not be mounted.
Nothing
Exits the application
Confirm that the data file backup information has been set correctly.
The ACM volume could not be unmounted.
The ACM volume could not be unmounted.
Nothing
Exits the application
The backup volume of the data file may have been accessed.
Alternatively, the data file backup information may not have been set correctly.
Check the status of the setup information and the device (volume).
An internal error has been generated.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unknown database has been specified.
The environment information for the specified database has not been located.
Nothing
Exits the application
Check the name of the database that is to be backed up to see if the configuration has been set up.
The recovery operation ended normally.
The database has been recovered normally.
Nothing
Nothing
Nothing
The recovery operation ended normally.
The archived redo log is no longer valid. Back up immediately.
The database has been recovered normally but all the backup database is invalidated as the log has been reset (resetlogs).
Nothing
Nothing
Obtain the backup database immediately.
The recovery operation was executed but abnormal resources have been found.
The recovery operation for the database was executed but resources in abnormal status exist.
Nothing
Nothing
Execute the recovery operation again.
The backup database corresponding to the specified generation cannot be found.
Rider : GEN_NO
The backup database specified in the generation specification at the restore point cannot be found.
GEN_NO : Generation
Exits the application
Specify the correct generation.
Specified time is incorrect.
Rider : TIME
The value specified in the time specification at the restore point contains an error.
TIME : Specified time
Exits the application
Specify the correct time.
The backup database corresponding to the specified time cannot be found.
Rider : TIME
The backup database specified in the time specification at the restore point cannot be found.
TIME: Time
Exits the application
Specify the correct time.
The specified thread number is incorrect.
Rider:THREAD
The thread specified in the thread number specification at the restore point cannot be found.
THREAD: Thread number
Exits the application
Specify the correct thread number.
The backup database corresponding to the specified log sequence number cannot be found.
Rider:LOG_NO
The backup database specified in the log sequence number specification at the restore point cannot be found.
LOG_NO: Log sequence number
Exits the application
Specify the correct log sequence number.
The backup database could not be restored.
The restore operation was attempted retrospectively, but failed completely.
Nothing
Exits the application
Confirm that the backup database has been obtained normally.
On-line recovery cannot be executed.
Rider: TABLESPACE
The specification method contains an error.
TABLESPACE: Tablespace
Exits the application
Specify offline recovery.
The instance could not be activated.
Rider:HOST/SID
The instance could not be activated in the auto recovery operation.
HOST: Host name
SID: ORACLE_SID name
Exits the application
confirm that "init<ORACLE_SID>.ora" or "spfile<ORACLE_SID>.ora" has been set up correctly.
An error was generated while checking the database status.
Rider:ORA_ERR
An unexpected error was generated while checking the database status.
ORA_ERR: ORACLE error number
Exits the application
Confirm the ORACLE error number and remove the cause of the error.
The working directory could not be created.
Rider:DIR_NAME
An error was generated while creating the working directory for this product.
DIR_NAME: Working directory name
Exits the application
Check the free disk status and the execution permission.
The instance could not be activated.
Rider:HOST/SID
An error was generated while activating the instance.
HOST: Host name
SID: ORACLE_SID name
Exits the application
Check the log so that no other errors have been generated.
The instance could not be terminated.
Rider:HOST/SID
An error was generated while terminating the instance.
HOST: Host name
SID: ORACLE_SID name
Exits the application
Check the log so that no other errors have been generated.
An error was generated during the RMAN restore processing.
Rider:DB_FILE
An error was generated while the Oracle Recovery Manager (RMAN) was executing the restore command.
DB_FILE: Type of restored resource
Exits the application
Check the log so that no other errors have been generated.
The redo log could not be restored.
Rider:COMMAND
An error was generated while transferring a normal redo log to a damaged redo log.
COMMAND: Restore command name
Exits the application
Check the log so that no other errors have been generated.
An error was generated during the RMAN recovery processing.
An error was generated while the Oracle Recovery Manager (RMAN) was executing the recovery command.
Nothing
Exits the application
Check the log so that no other errors have been generated.
A temporary file could not be recreated.
An expected error was generated while recreating the temporary file (TEMPFILE).
Nothing
Exits the application
Check the log so that no other errors have been generated.
The tablespace could not be online.
An error was generated while the tablespace is online.
Nothing
Exits the application
Check the log so that no other errors have been generated.
The tablespace could not be offline.
An error was generated while the tablespace is offline.
Nothing
Exits the application
Check the log so that no other errors have been generated.
The listener for recovery catalog database could not be activated.
An error was generated while activating the listener for the RMAN recovery catalog database.
Nothing
Exits the application
Check the log so that no other errors have been generated.
The listener for recovery catalog database could not be terminated.
An error was generated while the listener for the RMAN recovery catalog database was inactive.
Nothing
Exits the application
Check the log so that no other errors have been generated.
This product may not be installed correctly on the remote host.
Rider:HOST
The directory of this product cannot be found on the remote host.
HOST: Host name
Exits the application
Confirm that this product has been installed on the remote host.
Confirm also that the cluster software is operating correctly.
The remote host could not be operated.
Rider:HOST
An error was generated while creating the working directory for the remote host.
HOST: Host name
Exits the application
Confirm that the disk where the product directory is located on the remote host has free space. Confirm also that the cluster software is operating correctly.
An error was generated upon cancellation of the EC synchronous processing.
Rider:DEVICE
An unexpected error was generated while executing the ACM synchronous cancel command.
DEVICE: Device (volume) name where an error was generated.
Exits the application
Check the log so that no other errors have been generated.
An error was generated upon cancellation of the OPC restore processing.
Rider:DEVICE
An unexpected error was generated while executing the ACM restore cancel command.
DEVICE: Device (volume) name where an error was generated.
Exits the application
Check the log so that no other errors have been generated.
An error was generated during the OPC restore processing.
Rider:Parameter1
An error was generated while executing the ACM restore command.
Parameter1: Name of the device where an error was generated
Exits the application
Check the log so that no other errors have been generated.
Information on the cluster operation could not be obtained.
Rider: HOST/SID
An error was generated while executing the get data command in the cluster operation.
HOST: Host name
SID: ORACLE_SID name
Exits the application
Confirm that the cluster software is operating correctly.
The cluster operation (resource name) could not be obtained.
Rider: HOST/SID
An error was generated while executing the get data command in the cluster operation.
HOST: Host name
SID: ORACLE_SID name
Exits the application
Confirm that the resources are registered correctly with the cluster software.
Cluster software monitor could not be activated.
Rider:HOST/SID
An error was generated while executing the monitor activation command of the cluster software.
HOST: Host name
SID: ORACLE_SID name
Exits the application
Confirm that the cluster software is operating correctly.
Cluster software monitor could not be terminated.
Rider:HOST/SID
An error was generated while executing the monitor termination command of the cluster software.
HOST: Host name
SID: ORACLE_SID name
Exits the application
Confirm that the cluster software is operating correctly.
An error was generated while mounting the disk.
Rider:BACKUP_DISK
An error was generated while mounting the backup disk used in the recovery operation.
BACKUP_DISK:Backup disk type
Exits the application
Check the log so that no other errors have been generated.
An error was generated while unmounting the disk.
Rider:BACKUP_DISK
An error was generated while unmounting the backup disk used in the recovery operation.
BACKUP_DISK:Backup disk type
Exits the application
Check the log so that no other errors have been generated.
The backup operation may not have been executed properly.
Rider:BACKUP_INFO
The recovery operation was executed where the backup operation had never been implemented.
BACKUP_INFO: Backup history file name
Exits the application
Back up when the database is in normal status.
Name of the connecting host cannot be recognized.
The host name of the machine connected for the recovery operation could not be obtained.
Nothing
Exits the application
Confirm again that the host name can be obtained in the environment.
The connecting host is not registered in the configuration file.
Rider: HOST
The host name of the machine connected for the recovery operation is not registered in the configuration file (rmfo_node.ini).
HOST: Host name
Exits the application
Confirm that the host name in the configuration file (rmfo_node.ini) is set correctly.
The recovery method cannot be determined.
Rider:NO
A recovery method not supported has been specified.
NO: Recovery method (number)
Exits the application
Contact a Fujitsu engineer.
The recovery point cannot be determined.
Rider:NO
A recovery point not supported has been specified.
NO: Recovery method (number)
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated during the recovery operation.
Rider:ERR_INFO
An unpredicted error may have been generated during the recovery operation.
ERR_INFO: Error generation information
Exits the application
Contact a Fujitsu engineer.
The configuration file and backed up database cannot be located.
Either the directory for locating the configuration file or necessary configuration files are not found.
Nothing
Exits the application
Confirm that the configuration has been set up correctly for the database that is to be recovered and re-execute the application.
The database could not be checked.
A process execution error was detected while checking the database.
Nothing
Exits the application
Check the database status, and re-execute.
The configuration file could not be read.
Either the directory for locating the configuration file or necessary configuration files are not found.
Nothing
Exits the application
Confirm that the configuration has been set up correctly for the database that is to be recovered and re-execute the application.
An unexpected error was generated while displaying the recovery operation selection screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery operation selection screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery operation selection screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the DB check result display screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery operation screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery operation screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery operation screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
The alert log file could not be read.
The alert log file could not be found.
Nothing
Continues processing
Confirm whether:
a. The database instance has been activated
b. The alert log file has been set up correctly
c. The alert log file has been located
The alert log file could not be read.
The alert log file could not be found.
Nothing
Continues processing
Confirm that the alert log file has been set up correctly. Alternatively, confirm that the alert log file has been located.
An unexpected error was generated while displaying the recovery point specification dialog.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery point specification dialog.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery point specification dialog.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery point specification dialog.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery point specification dialog.
An unexpected internal error was generated.
Nothing
Continues processing
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery point specification dialog.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery method selection screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery method selection screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery operation confirmation screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the recovery method selection screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the execution log display screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the execution log display screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated, while displaying the DB check result display screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated, while displaying the DB check result display screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
An unexpected error was generated, while the DB check result display screen.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
The processing ended normally.
Either the create or delete RMAN recovery catalog database processing ended normally.
Nothing
Nothing
Nothing
Initialization has failed.
An unexpected internal error was generated.
Nothing
Exits the application
Contact a Fujitsu engineer.
The configuration file (Basic Information) could not be read.
The configuration file (basic information) could not be read.
Nothing
Exits the application
Confirm that the configuration file (basic information) has been located and that the configuration has been set up correctly.
The configuration file (Password) could not be read.
The configuration file (password) could not be read.
Nothing
Exits the application
Confirm that the configuration file (password) has been located and that the configuration has been set up correctly.
The configuration file (Node List) could not be read.
The configuration file (node list) could not be read.
Nothing
Exits the application
Confirm that the configuration file (node list) has been located and that the configuration has been set up correctly.
The mount processing has failed.
The RMAN recovery catalog database volume could not be mounted.
Nothing
Exits the application
Confirm that the mount point specified in the configuration file (RMAN recovery catalog database information) is enabled.
Unmount processing failed.
The RMAN recovery catalog database volume could not be unmounted.
Nothing
Continues processing
Confirm that the create or delete RMAN recovery catalog database processing has ended normally. If ended normally, unmount the volume manually. If ended abnormally, check the execution log, remove the cause of the error, and re-execute.
The database could not be activated.
The database could not be activated.
The RMAN recovery catalog database could not be activated.
Nothing
Exits the application
Check the execution log to ensure the database can be activated normally.
The database could not be terminated.
The RMAN recovery catalog database could not be terminated.
Nothing
Exits the application
Check the execution log to ensure the database can be activated normally.
The listener could not be activated.
The RMAN recovery catalog database listener could not be activated.
Nothing
Exits the application
Check the listener log ($ORACLE_HOME/network/log) and confirm that the system can be activated normally.
The listener could not be terminated.
The RMAN recovery catalog database listener could not be terminated.
Nothing
Continues processing
Check the listener log ($ORACLE_HOME/network/log) and confirm that the system can be activated normally.
The RMAN create recovery catalog shell script could not be generated.
An unexpected internal error was generated.
Nothing
Exits the application after the error recovery processing
Check the execution log. Remove the cause of the error, and re-execute.
The RMAN create recovery catalog shell script could not be executed.
The execution shell script of the create RMAN recovery catalog database script could not be executed.
Nothing
Exits the application after the error recovery processing
Check the execution log. Remove the cause of the error, and re-execute.
The "init.ora" file could not be copied to other nodes.
"inito.ora" of the RMAN recovery catalog database could not be distributed to other nodes.
Nothing
Exits the application after the error recovery processing
Check the contents of the configuration file (node list) and that each node can be connected to.
"listener.ora" and "tnsnames.ora" could not be generated.
Either the create/update processing of "listener.ora" and "tnsnames.ora" for the RMAN recovery catalog database or its distribution to other nodes failed.
Nothing
Exits the application after the error recovery processing
Confirm that "listener.ora" and "tnsnames.ora" of the primary node have been updated correctly. If the primary node has been updated correctly, check the contents of the configuration file (node list) and that each node can be connected to.
The catalog tablespace command could not be executed.
The recovery catalog could not be created (create catalog).
Nothing
Exits the application after the error recovery processing
Check the execution log. Remove the cause of the error, and re-execute.
The register database command could not be executed.
The database could not be registered with the recovery catalog (register database).
Nothing
Exits the application after the error recovery processing
Confirm that the target database has been activated normally. If it has, remove the cause of the error, and re-execute.
The RMAN recovery catalog database could not be created.
An error was generated while creating the RMAN recovery catalog database.
Nothing
Interrupts processing and executes recovery processing, depending on the error location.
Check the execution log. Remove the cause of the error, and re-execute.
The command to change the Oracle owner could not be executed.
The owner of the file or the directory could not be changed to the Oracle Owner.
Nothing
Exits the application after the error recovery processing
Check the execution log. Remove the cause of the error, and re-execute.
The configuration file (Recovery Catalog Database Information) could not be read.
The configuration file (RMAN recovery log database information) could not be read.
Nothing
Exits the application after the error recovery processing
Confirm that the configuration file (RMAN recovery log database information ) is located or the configuration has been set up correctly.
The "init.ora" file could not be deleted.
An error was generated while deleting the initial parameter file (init<DB_NAME>.ora) in the RMAN recovery catalog database.
Nothing
Exits the application after the error recovery processing
Confirm that "init<DB_NAME>.ora" of the primary node has been deleted. When the primary node has been deleted, check the contents of the configuration file (node list) and that each node can be connected to.
The RMAN recovery catalog database could not be deleted.
An error was generated while creating the RMAN recovery catalog database.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The host name could not be obtained.
An unexpected internal error was generated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
SID could not be obtained.
An unexpected internal error was generated.
Nothing
Exits the application
Check the execution log. Remove the cause of the error, and re-execute.
The directory could not be created (RMAN recovery catalog database).
The directory could not be created at the mount point of the RMAN recovery catalog database.
Nothing
Exits the application
Confirm that the mount point of the RMAN recovery catalog database is enabled.
The directory could not be deleted.
An unexpected internal error was generated.
Nothing
Exits the RMAN recovery catalog database application
Check the execution log. Remove the cause of the error, and re-execute.
An unexpected error was generated while displaying the help screen.
An unexpected internal error was generated.
Nothing
Ignores
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the help screen.
An unexpected internal error was generated.
Nothing
Exits the help screen display processing
Contact a Fujitsu engineer.
An unexpected error was generated while displaying the version information screen.
An unexpected internal error was generated.
Nothing
Exits the version information display processing
Contact a Fujitsu engineer.
|
Contents
|