Cause | Cannot create the file. |
Action | Check the file path and permissions. |
Cause | Cannot lock the file. |
Action | Check the file path and permissions. |
Cause | Cannot open the file. |
Action | Check the file path and permissions. |
Cause | Cannot read the file. |
Action | Check the file path and permissions. |
Cause | Cannot write to the file. |
Action | Check the file path and permissions. |
Cause | Cannot open the log file. |
Action | Check the log file path and permissions. |
Cause | Cannot read the log file. |
Action | Check the log file path and permissions. |
Cause | Cannot write to the log file. |
Action | Check the log file path and permissions. |
Cause | Cannot read the corrupted data block. |
Action | Perform a media recovery and try again. |
Cause | Cannot read the data block due to inconsistency. |
Action | Perform a media recovery and try again. |
Cause | Invalid file type. |
Action | Check the data file type and try again. |
Cause | The log file is not the one from the specified log group. |
Action | Check the log file and try again. |
Cause | Failed to create a log file. |
Action | Check the log file path and permissions. |
Cause | Failed to create a data file. |
Action | Check the file path and permissions. |
Cause | The size of buffer cache is insufficient. |
Action | Check the size of buffer cache and try again. |
Cause | One of the log group members is corrupt. |
Action | Perform a recovery of the log file. |
Cause | Tried to create a log file with a duplicate log file number. |
Action | Check the log file. |
Cause | One of the log group members is abnormal. |
Action | Perform a recovery of the log file. |
Cause | Log file is abnormal. |
Action | Check the log file. |
Cause | The data file is from another database. |
Action | Check the data file. |
Cause | Tried to create a file with a duplicate data file number. |
Action | Check the data file. |
Cause | Resetlogs failed. |
Action | Locate the cause of the failure and try again. |
Cause | Reboot the system with resetlogs. |
Action | Perform any required recovery processes and try again. |
Cause | Media Recovery is needed. |
Action | Perform media recovery. |
Cause | Media Recovery has already started. |
Action | Locate the cause of the failure and try again. |
Cause | Media Recovery has not started. |
Action | Locate the cause of the failure and try again. |
Cause | Cannot locate the log file needed for Media Recovery. |
Action | Check the log file and try again. |
Cause | The log file is invalid. |
Action | Choose a valid log file and try again. |
Cause | Failed to transmit a redo log to standby DB. |
Action | Check the condition of standby DB and try again. |
Cause | The communications protocol does not match that of standby DB. |
Action | Verify the server versions of the primary DB and standby DB match and then try again. |
Cause | The settings for the standby DB are invalid. |
Action | Modify the settings in primary DB and try again. |
Cause | Cannot open the redo log file to be transmitted to standby DB. |
Action | Verify the log file exists and try again. |
Cause | Database requires recovery. |
Action | Check the cause of the failure and try again. |
Cause | DB has been opened in read-only mode. |
Action | Reopen in another mode and try again. |
Cause | A consistency check for the standby DB failed. |
Action | Create a new standby DB. |
Cause | No response has arrived from standby DB. |
Action | Verify the standby DB is running, and check the server version. |
Cause | The primary DB failed to connect with the standby DB. |
Action | Examine the configuration files of the primary and standby DBs and try again. |
Cause | Error with online redo log file. |
Action | Check the online redo log file and restart the server. |
Cause | The action is not permitted while the standby DB is connected. |
Action | Disconnect the standby DB and try again. |
Cause | A partial recovery cannot be started because an invalid recovery finish time has been specified. |
Action | Contact the technical support team. |
Cause | Failed to read the log member file. |
Action | Perform a recovery of invalid log file members. |
Cause | Cannot finish media recovery now. |
Action | Finish the media recovery after satisfying the conditions necessary for completion. |
Cause | Failed to read the log file. |
Action | Verify the log file is error free and try again. |
Cause | Cannot use redo threads. |
Action | Enable redo threads and try again. |
Cause | Cannot add a log file. |
Action | Contact the technical support team. |
Cause | Cannot use redo threads. |
Action | Enable redo threads and try again. |
Cause | The light work rule was violated. |
Action | Internal flag. This error can be safely ignored. |
Cause | Media Recovery is required. |
Action | Perform media recovery. |
Cause | The checkpoints should be set first. |
Action | Set the checkpoints first and try again. |
Cause | The instance recovery was canceled due to the activation of another instance recovery. |
Action | Internal flag. This error can be safely ignored. |
Cause | The members of the log group are not identical. |
Action | Ensure all log members identical. |
Cause | Unable to start database in a single instance mode. |
Action | Use a clustered database. |
Cause | The redo thread is already in use. |
Action | Check the status of the redo threads and try again. |
Cause | Cannot perform automatic Media Recovery. |
Action | Continue Media Recovery through manual recovery. |
Cause | Some other instances are running. |
Action | End the active instances and try again. |
Cause | Unable to start the Media Recovery with the information given. |
Action | Specify another argument or a different Media Recovery. |
Cause | Unable to perform a Media Recovery due to invalid log or data block. |
Action | Check the log file and try again. |
Cause | Cannot access the file at instance. |
Action | Check the file path and try again. |
Cause | Cannot read the data block due to unformatted or corrupted block. |
Action | Perform Media Recovery and try again. |
Cause | Cannot complete boot since instance recovery is ongoing. |
Action | Try to boot later. |
Cause | Cannot decrypt block. |
Action | Verify the wallet is valid or check if the block is corrupt. |
Cause | Unable to proceed while all logfiles are being archived. |
Action | Check that the archive log destination device or directory is not full. |
Cause | The size of buffer cache is insufficient. |
Action | Check the size of buffer cache and try again. |
Cause | Failed to read the log file. |
Action | Verify the log file is error free and try again. |
Cause | Block Change Tracker is not configured. |
Action | Verify Block Change Tracker configuration. |
Cause | Block Change Tracker is not configured correctly for TAC. |
Action | Verify Block Change Tracker configuration. |
Cause | ERROR : malloc failed due to a lack of memory space in the system. |
Action | Increase the memory space in the system. |
Cause | Media recovery has stopped. |
Action | Try again. |
Cause | Incomplete media recovery is finished. |
Action | Resetlogs is required. |
Cause | Media recovery is not needed. |
Action | Resetlogs is required. |
Cause | Current online log file is outdated. Recovery is incomplete. |
Action | Resetlogs is required. |
Cause | Read flushed redo blocks partially. Redo buffer wasn't completely flushed. |
Action | Verify the log file is error free and try again. |
Cause | Incomplete media recovery is finished. |
Action | Resetlogs is required. |
Cause | Cannot use this redo thread. |
Action | Resetlogs is required to use this redo thread. |
Cause | In the current boot mode, this DDL cannot be executed. |
Action | Change the boot mode and run the DDL statement again. |
Cause | Bitmap already set on block #%1$d |
Action | Check backup data file. |
Cause | Bitmap overflow. Bitmap size was %1$d |
Action | Check backup data file. |
Cause | Datafile's DB names differ. ('%1$s' != '%2$s') |
Action | Check data files. |
Cause | Datafile's DB ids differ. (%1$d != %2$d) |
Action | Check data files. |
Cause | Datafile's DB versions differ. (%1$d != %2$d) |
Action | Check data files. |
Cause | Datafile file number mismatch. (%1$d != %2$d) |
Action | Check data files. |
Cause | Datafile file block size mismatch. (%1$d != %2$d) |
Action | Check data files. |
Cause | Can't setup new uid to data file. |
Action | Check data file. |
Cause | Backup must have %1$d blocks, but %1$d blocks copied. |
Action | Check backup data file. |
Cause | Decompress error while restore. |
Action | Check backup data file. |
Cause | Compress error while backup. |
Action | Check data file. |
Cause | Block is not bitmap header. |
Action | Check backup data file. |
Cause | Invalid backup file %1$s. |
Action | Check backup data file. |
Cause | Invalid backup block #%1$d in %2$s. |
Action | Check backup data file. |
Cause | Unable to perform a Crash Recovery due to invalid log or data block. |
Action | Restore the datafile and try again. |
Cause | Unable to find backup path for backup archiving. |
Action | Please specify path of archive of backup files. |
Cause | Buffer size(%1$d) is not multiple of compress unit(%2$d). |
Action | Please make buffer size to be multiple of compress unit. |
Cause | Tablespace #%1$d isn't included in backupset id #%2$d. |
Action | Please make sure this backup set contains tablespace #%1$d. |
Cause | Can't find proper backup set to restore |
Action | Check there is a backup set containing all required tablespaces. |
Cause | Can't perform standby side controlfile operation: %1$s |
Action | Recreate the standby database. |
Cause | Cannot use flashback threads. |
Action | Enable flashback threads and try again. |
Cause | Reboot the system with failover. |
Action | Perform any required recovery processes and try again. |
Cause | Cannot perform flashback database operation. |
Action | Check flashback marker status and try again. |