No. 1000 ~ 1999

1001: Unable to create file %1$s.

• Cause: Cannot create the file.

• Action: Check the file path and permissions.

1002: Unable to lock file %1$s.

• Cause: Cannot lock the file.

• Action: Check the file path and permissions.

1003: Unable to open file %1$s.

• Cause: Cannot open the file.

• Action: Check the file path and permissions.

1004: Unable to read file %1$s.

• Cause: Cannot read the file.

• Action: Check the file path and permissions.

1005: Unable to write to file %1$s.

• Cause: Cannot write to the file.

• Action: Check the file path and permissions.

1006: Unable to open log file in group %1$d.

• Cause: Cannot open the log file.

• Action: Check the log file path and permissions.

1007: Unable to read log file in group %1$d, block %2$d.

• Cause: Cannot read the log file.

• Action: Check the log file path and permissions.

1008: Unable to write to log file in group %1$d, block %2$d.

• Cause: Cannot write to the log file.

• Action: Check the log file path and permissions.

1009: Unable to read corrupt block: file# %1$u, block# %2$u.

• Cause: Cannot read the corrupted data block.

• Action: Perform a media recovery and try again.

1010: Unable to read fractured block: file# %1$u, block# %2$u.

• Cause: Cannot read the data block due to inconsistency.

• Action: Perform a media recovery and try again.

1011: File is not %1$s file: %2$s.

• Cause: Invalid file type.

• Action: Check the data file type and try again.

1012: Log file group mismatch: GROUP %1$d <> %2$d (%3$s)

• Cause: The log file is not the one from the specified log group.

• Action: Check the log file and try again.

1013: Unable to create log file %1$s.

• Cause: Failed to create a log file.

• Action: Check the log file path and permissions.

1014: Unable to create datafile %1$s.

• Cause: Failed to create a data file.

• Action: Check the file path and permissions.

1015: Unable to pin more blocks.

• Cause: The size of buffer cache is insufficient.

• Action: Check the size of buffer cache and try again.

1016: Log group %1$d is corrupt.

• Cause: One of the log group members is corrupt.

• Action: Perform a recovery of the log file.

1017: Duplicate log file %1$d exists.

• Cause: Tried to create a log file with a duplicate log file number.

• Action: Check the log file.

1018: Bad log group %1$d (%2$s).

• Cause: One of the log group members is abnormal.

• Action: Perform a recovery of the log file.

1019: Bad log file %2$s (%1$s).

• Cause: Log file is abnormal.

• Action: Check the log file.

1020: Bad datafile %1$s.

• Cause: The data file is from another database.

• Action: Check the data file.

1021: Duplicate datafile %1$s exists.

• Cause: Tried to create a file with a duplicate data file number.

• Action: Check the data file.

1022: Resetlogs failed: %1$s (%2$s)

• Cause: Resetlogs failed.

• Action: Locate the cause of the failure and try again.

1023: Resetlogs is required.

• Cause: Reboot the system with resetlogs.

• Action: Perform any required recovery processes and try again.

1024: Database needs media recovery: %1$s(%2$s).

• Cause: Media Recovery is needed.

• Action: Perform media recovery.

1025: Media Recovery has already started.

• Cause: Media Recovery has already started.

• Action: Locate the cause of the failure and try again.

1026: Media Recovery has not started.

• Cause: Media Recovery has not started.

• Action: Locate the cause of the failure and try again.

1027: Unable to find archive log file for thread %1$d from change "UINT64_FMT(2$)".

• Cause: Cannot locate the log file needed for Media Recovery.

• Action: Check the log file and try again.

1028: Log file is invalid: %1$s (seq=%2$d), %3$s.

• Cause: The log file is invalid.

• Action: Choose a valid log file and try again.

1029: Log network write failed.

• Cause: Failed to transmit a redo log to standby DB.

• Action: Check the condition of standby DB and try again.

1030: Log network protocol failure (type=%1$d req_type=%2$d).

• 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.

1032: Invalid cache replication configuration (%1$s).

• Cause: The settings for the standby DB are invalid.

• Action: Modify the settings in primary DB and try again.

1033: Unable to open log file (%1$d).

• Cause: Cannot open the redo log file to be transmitted to standby DB.

• Action: Verify the log file exists and try again.

1034: Database requires recovery.

• Cause: Database requires recovery.

• Action: Check the cause of the failure and try again.

1035: Database is open in read-only mode.

• Cause: DB has been opened in read-only mode.

• Action: Reopen in another mode and try again.

1036: Standby consistency check failed.

• Cause: A consistency check for the standby DB failed.

• Action: Create a new standby DB.

1037: Log network read failed.

• Cause: No response has arrived from standby DB.

• Action: Verify the standby DB is running, and check the server version.

1038: Log network connect failed (%1$s).

• 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.

1039: LF#%1$d - %2$s.

• Cause: Error with online redo log file.

• Action: Check the online redo log file and restart the server.

1040: Not permitted while standby database is connected.

• Cause: The action is not permitted while the standby DB is connected.

• Action: Disconnect the standby DB and try again.

1041: Unable to start partial recovery - %1$s (%2$s).

• Cause: A partial recovery cannot be started because an invalid recovery finish time has been specified.

• Action: Contact the technical support team.

1042: Unable to read log member file in group %1$d, member %2$d (%3$s), block %4$d.

• Cause: Failed to read the log member file.

• Action: Perform a recovery of invalid log file members.

1043: Unable to finish media recovery - %1$s (%2$s).

• Cause: Cannot finish media recovery now.

• Action: Finish the media recovery after satisfying the conditions necessary for completion.

1044: Unable to read log file: file %1$s, blk %2$d.

• Cause: Failed to read the log file.

• Action: Verify the log file is error free and try again.

1045: Redo thread #%1$d is not enabled.

• Cause: Cannot use redo threads.

• Action: Enable redo threads and try again.

1046: Unable to add log file - %1$s (%2$s).

• Cause: Cannot add a log file.

• Action: Contact the technical support team.

1047: Datafile requires redo thread #%1$d to be enabled - %2$s.

• Cause: Cannot use redo threads.

• Action: Enable redo threads and try again.

1048: Light work rule violated.

• Cause: The light work rule was violated.

• Action: Internal flag. This error can be safely ignored.

1049: Datafile #%1$d needs Media Recovery.

• Cause: Media Recovery is required.

• Action: Perform media recovery.

1050: Datafile #%1$d needs Media Recovery.

• Cause: The checkpoints should be set first.

• Action: Set the checkpoints first and try again.

1051: Instance recovery cascaded.

• Cause: The instance recovery was canceled due to the activation of another instance recovery.

• Action: Internal flag. This error can be safely ignored.

1052: Log members in group %1$d, block %2$d are not identical.

• Cause: The members of the log group are not identical.

• Action: Ensure all log members identical.

1053: Unable to run database in single instance mode.

• Cause: Unable to start database in a single instance mode.

• Action: Use a clustered database.

1054: Redo thread %1$d already used.

• Cause: The redo thread is already in use.

• Action: Check the status of the redo threads and try again.

1055: Unable to automatically recover media from change "UINT64_FMT(1$)".

• Cause: Cannot perform automatic Media Recovery.

• Action: Continue Media Recovery through manual recovery.

1056: Unable to proceed while other instances are running.

• Cause: Some other instances are running.

• Action: End the active instances and try again.

1057: Unable to start a Media Recovery - %1$s.

• Cause: Unable to start the Media Recovery with the information given.

• Action: Specify another argument or a different Media Recovery.

1058: Unable to recover corrupt/corruptible media.

• Cause: Media Recovery stops due to an invalid redo log or a data block.

• Action: Check the redo log or the data block.

1059: Cannot access the file at instance %1$d - %2$s.

• Cause: Cannot access the file at instance.

• Action: Check the file path and try again.

1060: Unable to read afferent DBA block: file# %1$u, block# %2$u.

• Cause: Cannot read the data block due to unformatted or corrupted block.

• Action: Perform Media Recovery and try again.

1061: Instance recovery is ongoing.

• Cause: Cannot complete boot since instance recovery is ongoing.

• Action: Try to boot later.

1062: Cannot decrypt block.

• Cause: Cannot decrypt block.

• Action: Verify the wallet is valid or check if the block is corrupt.

1063: Log writer is waiting for all logfiles to be archived.

• Cause: Unable to proceed while all logfiles are being archived.

• Action: Check that the archive log destination device or directory is not full.

1064: Unable to recover specified block(s).

• Cause: The size of buffer cache is insufficient.

• Action: Check the size of buffer cache and try again.

1065: Unable to read spanned log: file %1$s, blk %2$d.

• Cause: Failed to read the log file.

• Action: Verify the log file is error free and try again.

1066: Block Change Tracker is not configured.

• Cause: Block Change Tracker is not configured.

• Action: Verify Block Change Tracker configuration.

1067: Block Change Tracker setting (%1$s) is should be %2$s across the cluster.

• Cause: Block Change Tracker is not configured correctly for TAC.

• Action: Verify Block Change Tracker configuration.

1068: The memory space in the system is insufficient.

• Cause: ERROR : malloc failed due to a lack of memory space in the system.

• Action: Increase the memory space in the system.

1069: Media recovery has stopped due to cluster reconfiguration.

• Cause: Media recovery has stopped.

• Action: Try again.

1070: Incomplete media recovery is finished, but resetlogs is required.

• Cause: Incomplete media recovery is finished.

• Action: Resetlogs is required.

1071: Media recovery is not needed, but resetlogs is required.

• Cause: Media recovery is not needed.

• Action: Resetlogs is required.

1072: Current online log file (thread %1$d seq %2$d) is outdated.\nNeed a log with seq %3$d to recover from TSN%4$s\nRecovery is incomplete and resetlogs is required.

• Cause: Current online log file is outdated. Recovery is incomplete.

• Action: Resetlogs is required.

1073: Unable to read flushed redo blocks. logfile #%1$d, blk %2$d, remain %3$d

• Cause: Read flushed redo blocks partially. Redo buffer wasn't completely flushed.

• Action: Verify the log file is error free and try again.

1074: Incomplete media recovery is finished, but resetlogs is required.\n%1$s

• Cause: Incomplete media recovery is finished.

• Action: Resetlogs is required.

1075: Redo thread #%1$d is has missing logfiles.

• Cause: Cannot use this redo thread.

• Action: Resetlogs is required to use this redo thread.

1076: Unable to create online datafile in current boot mode.

• Cause: In the current boot mode, this DDL cannot be executed.

• Action: Change the boot mode and run the DDL statement again.

1077: Bitmap already set on block #%1$d

• Cause: Bitmap already set on block #%1$d

• Action: Check backup data file.

1078: Bitmap overflow. Bitmap size was %1$d

• Cause: Bitmap overflow. Bitmap size was %1$d

• Action: Check backup data file.

1079: Datafile's DB names differ. ('%1$s' != '%2$s')

• Cause: Datafile's DB names differ. ('%1$s' != '%2$s')

• Action: Check data files.

1080: Datafile's DB ids differ. (%1$d != %2$d)

• Cause: Datafile's DB ids differ. (%1$d != %2$d)

• Action: Check data files.

1081: Datafile's DB versions differ. (%1$d != %2$d)

• Cause: Datafile's DB versions differ. (%1$d != %2$d)

• Action: Check data files.

1082: Datafile file number mismatch. (%1$d != %2$d)

• Cause: Datafile file number mismatch. (%1$d != %2$d)

• Action: Check data files.

1083: Datafile file block size mismatch. (%1$d != %2$d)

• Cause: Datafile file block size mismatch. (%1$d != %2$d)

• Action: Check data files.

1084: Can't setup new uid to data file.

• Cause: Can't setup new uid to data file.

• Action: Check data file.

1085: Backup must have %1$d blocks, but %1$d blocks copied.

• Cause: Backup must have %1$d blocks, but %1$d blocks copied.

• Action: Check backup data file.

1086: Decompress error while restore.

• Cause: Decompress error while restore.

• Action: Check backup data file.

1087: Compress error while backup.

• Cause: Compress error while backup.

• Action: Check data file.

1088: Block is not bitmap header.

• Cause: Block is not bitmap header.

• Action: Check backup data file.

1089: Invalid backup file %1$s.

• Cause: Invalid backup file %1$s.

• Action: Check backup data file.

1090: Invalid backup block #%1$d in %2$s.

• Cause: Invalid backup block #%1$d in %2$s.

• Action: Check backup data file.

1091: Unable to recover corrupted media.

• Cause: Unable to perform a Crash Recovery due to invalid log or data block.

• Action: Restore the datafile and try again.

1092: Unable to find backup path for backup archiving.

• Cause: Unable to find backup path for backup archiving.

• Action: Please specify path of archive of backup files.

1093: Buffer size(%1$d) is not multiple of compress unit(%2$d).

• Cause: Buffer size(%1$d) is not multiple of compress unit(%2$d).

• Action: Please make buffer size to be multiple of compress unit.

1094: Tablespace #%1$d isn't included in backupset id #%2$d.

• Cause: Tablespace #%1$d isn't included in backupset id #%2$d.

• Action: Please make sure this backup set contains tablespace #%1$d.

1095: Can't find proper backup set to restore

• Cause: Can't find proper backup set to restore

• Action: Check there is a backup set containing all required tablespaces.

1096: Can't perform standby side controlfile operation: %1$s

• Cause: Can't perform standby side controlfile operation: %1$s

• Action: Recreate the standby database.

1097: Flashback thread #%1$d is not enabled.

• Cause: Cannot use flashback threads.

• Action: Enable flashback threads and try again.

1098: Database in standby mode. Failover is required to boot as primary.

• Cause: Reboot the system with failover.

• Action: Perform any required recovery processes and try again.

1099: Cannot find marker before change "UINT64_FMT(1$)" for thread %2$d. (Deprecated)

• Cause: Cannot perform flashback database operation. (Deprecated)

• Action: Check flashback marker status and try again. (Deprecated)

1100: Unable to access tape device

• Cause: Cannot perform tape backup.

• Action: Check path of tape device.

1101: No more free space available in tape device

• Cause: Cannot perform tape backup.

• Action: Change tape to new one.

1102: Log network connection disconnected.

• Cause: Log network connection disconnected.

• Action: Examine network connection between the primary and standby DBs and try again.

1107: Set the parameter USE_STANDBY_REDO_LOG to Y.

• Cause: Set the parameter USE_STANDBY_REDO_LOG to Y.

• Action: Set the parameter USE_STANDBY_REDO_LOG to Y.

1108: A bitmap header block is unformatted while accessing the datafile header view.

• Cause: Creating a datafile may cause this error.

• Action: Query the datafile header view again.

1109: Set the parameter ENCRYPT_GLOBAL_KEY_FILE to recover encrypted tablespace.

• Cause: Set the parameter ENCRYPT_GLOBAL_KEY_FILE to recover encrypted tablespace.

• Action: Set the parameter ENCRYPT_GLOBAL_KEY_FILE to recover encrypted tablespace.

1110: Failed to read ENCRYPT_GLOBAL_KEY_FILE: %1$s

• Cause: Failed to read ENCRYPT_GLOBAL_KEY_FILE: %1$s

• Action: Set the correct path for the parameter ENCRYPT_GLOBAL_KEY_FILE

1111: Cannot read log blocks of invalid range for logfile %1$d.

• Cause: Cannot read log blocks of invalid range for logfile %1$d.

• Action: Logfile %1$d might have been cleared.

1112: Invalid log file found: %1$s, seq#%2$d (expected: seq#%3$d)

• Cause: Invalid log file found: %1$s, seq#%2$d (expected: seq#%3$d)

• Action: Invalid log file found: %1$s, seq#%2$d (expected: seq#%3$d)

1113: Unable to recover corrupt/corruptible media.

• Cause: Crash/Instance Recovery stops due to an invalid redo log or a data block.

• Action: Check the redo log or the data block.

1114: Not permitted while some standby databases are disconnected.

• Cause: The action is not permitted while some standby DBs are disconnected.

• Action: Examine network connection between the primary and standby DBs and try again.

1115: Failed to set the status of flashback %1$s %2$s.

• Cause: Flashback %1$s is already %2$s.

• Action: Check flashback %1$s is already %2$s.

1116: FLASHBACK_LOG_BUFFER parameter must be set as non-zero when flashback logging is activated, and vice versa.

• Cause: FLASHBACK_LOG_BUFFER parameter must be set as non-zero when flashback logging is activated, and vice versa.

• Action: Check the value of FLASHBACK_LOG_BUFFER.

1117: Unable to open flashback log file in group %1$d.

• Cause: Cannot open the flashback log file.

• Action: Check the flashback log file path and permissions.

1118: Unable to read flashback log file in group %1$d, block %2$d.

• Cause: Cannot read the flashback log file.

• Action: Check the flashback log file path and permissions.

1119: Unable to write to flashback log file in group %1$d, block%2$d.

• Cause: Cannot write to the flashback log file.

• Action: Check the flashback log file path and permissions.

1120: LF#%1$d - %2$s.

• Cause: Error with online flashback log file.

• Action: Check the online flashback log file and restart the server.

1121: Unable to find flashback archive log file for thread %1$d from change "UINT64_FMT(2$)".

• Cause: Cannot locate the flashback log file needed for Flashback.

• Action: Check the flashback log file and try again.

1122: File fstat failed: %1$s

• Cause: File fstat failed: %1$s

• Action: File fstat failed: %1$s

1123: Standby reverse sync is not possible.

• Cause: Standby reverse sync is not possible.

• Action: Need to reconstruct standby.

1124: Reconfiguration occurred duirng the gca lock opeartion.

• Cause: Reconfiguration occurred duirng the gca lock opeartion.

• Action: Internal flag. This error can be safely ignored.

1125: Insufficient buffer size(%1$d) to serve the requested read operation. (Requested block count %2$d)

• Cause: Insufficient buffer size(%1$d) to serve the requested read operation. (Requested block count %2$d)

• Action: Contact the technical support team.

1126: Standby redo log is necessary for snapshot standby.

• Cause: Standby redo log is necessary for snapshot standby.

• Action: Configure standby redo log first.

1127: Database not in standby mode.

• Cause: Database not in standby mode.

• Action: Database not in standby mode.

1128: Database not in snapshot standby mode.

• Cause: Database not in snapshot standby mode.

• Action: Database not in snapshot standby mode.

1129: Database in snapshot standby mode. Convert to standby first to boot as standby.

• Cause: Convert to standby first and reboot as standby.

• Action: Perform any required recovery processes and try again.

1130: Block Change Tracking is not supported yet when LGWR_USE_AIO is set Y.

• Cause: Block Change Tracking is not supported yet when LGWR_USE_AIO is set Y.

• Action: Block Change Tracking is not supported yet when LGWR_USE_AIO is set Y.

1131: Standby redo thread #%1$d is not enabled.

• Cause: Cannot use standby redo threads.

• Action: Enable standby redo threads and try again.

1132: The size of standby logfile is too small.

• Cause: The size of standby logfile must be larger than or equal to the size of redo log file.

• Action: Increase the size of standby logfile and try again.

1133: Global log flush failed.

• Cause: Failed to execute the query due to global log flush failure.

• Action: Re-execute the query.

1134: Unable to recover corrupt/corruptible media.

• Cause: SMR stops due to an invalid redo log or a data block.

• Action: Check the redo log or the data block.

1135: An invalid bucket has been found.

• Cause: Unable to proceed because the bucket is invalid.

• Action: Check the dump file.

1136: Cannot raise to read only server mode until standby managed recovery recovers until TSN %1$u.

• Cause: Standby managed recovery need to recover until TSN %1$u to raise to read only server

  mode.

• Action: Wait for the standby managed recovery recovers until TSN %1$u and try again.

1137: Failover is not allowed. Database is not in standby mode.

• Cause: Reboot the system with another bootmode.

• Action: Perform any required recovery processes and try again.

1138: Unable to unlink file %1$s.

• Cause: Cannot delete the file.

• Action: Check the file path and permissions.

1139: Standby reverse sync is not possible: %1$s.

• Cause: Standby reverse sync is not possible: %1$s

• Action: Need to reconstruct standby.

1140: Too many LNWs. (%1$d, max: %2$d)

• Cause: Number of LNWs is limited to %2$d.

• Action: Modify the tip file and try again.

1141: Request to Block Change Tracker failed.

• Cause: Block Change Tracker failed the action requested.

• Action: Investigate the sys.log about BCT(Block Change Tracking).

1142: Standby redo log feature is not activated.

• Cause: Standby redo log feature is not activated.

• Action: Activate standby redo log feature and try again.

1143: Standby redo log feature is already activated.

• Cause: Standby redo log feature is already activated.

• Action: Standby redo log feature is already activated.

1144: Standby redo log feature is already deactivated.

• Cause: Standby redo log feature is already deactivated.

• Action: Standby redo log feature is already deactivated.

1145: Deactivating standby redo log feature is not allowed for snapshot standby.

• Cause: Deactivating standby redo log feature is not allowed for snapshot standby.

• Action: Deactivating standby redo log feature is not allowed for snapshot standby.

1146: SMR read archive log.

• Cause: SMR stopped because it had been reading archive log.

• Action: Contact the technical support team.

1147: Need log file (thread %1$d seq %2$d) to recover from TSN %3$s\nRecovery is incomplete and resetlogs is required.

• Cause: Current online log file is outdated. Recovery is incomplete.

• Action: Resetlogs is required.

1148: Unable to boot standby instance while other instances are running.

• Cause: Some other standby instances are running.

• Action: End the active standby instances and try again.

1149: Failed to initlalize log network reader: %1$s

• Cause: Error occured while initializing log network reader.

• Action: Contact the technical support team.

1150: Standby redo log feature in TAC environment is not support ed in this version.

• Cause: Standby redo log feature in TAC envirnoment is not supported in this version.

• Action: Upgrade Tibero version to use this feature.

1151: Offline datafile #%1$d requires media recovery. When reset log, the file may be lost.

• Cause: Offline datafile #%1$d requires media recovery. When resetlog, the file may be lost.

• Action: Take a backup file and recover it or take it offline using the IMMEDIATE option.

1152: Unable to read dp corrupt block: file# %1$u, block# %2$u.

• Cause: Cannot read the dp corrupted data block.

• Action: Perform a media recovery and try again.

1153: Flashback logging is activated in standby database.

• Cause: Flashback logging is not allowed in standby database.

• Action: Deactivate flashback logging and try again.

1154: Flashback logging is disabled in snapshot standby database.

• Cause: Flashback logging must be enabled in snapshot standby database.

• Action: Activate flashback logging and try again.

1155: Block media recovery target block is out of range: block#%1$u.

• Cause: Target block number must be within valid range.

• Action: Try block range within (1 ~ %2$u).

1156: Cannot read bitmap header block while performing block media recovery: %1$s

• Cause: Need to read bitmap header block to perform block media recovery.

• Action: Recover bitmap header block first and try again.

1157: Incomplete recovery has progressed up to TSN %1$d, but it needs to reach at least TSN %2$d.

• Cause: The process must continue up to the maximum checkpoint value in all datafiles.

• Action: Check the log file and retry.

1158: Database trying to recover is not a snapshot database.

• Cause: Snapshot database recovery should only be performed on snapshot database.

• Action: Try other recovery options.

1159: Unable to read archive log file: file %1$s, block %2$d.

• Cause: Cannot read the archive log file.

• Action: Check the archive log file path and permissions.

1160: A pin self-deadlock has occurred.

• Cause: An attempt was made to pin a block that is already pinned.

• Action: Retry the canceled query. If the issue persists, contact Tibero Technical Support or Tibero

  R&D.