‘Ctrl+F’로 에러 메시지 번호를 검색하시면 문제 발생 원인과 해결 방법을 빠르게 확인하실 수 있습니다.
Tibero Error Message 24000~24999
24001: Unable to open control file.
Cause: Failed to open the control file.
Action: Check the file path and permissions and try again.
24002: Too many %1$s.
Cause: The number of DB files exceeds the specified number.
Action: Contact the technical support team.
24003: Unable to read control file.
Cause: Cannot read the control file.
Action: Check the file path and permissions and try again.
24004: Unable to write to control file.
Cause: Cannot write to the control file.
Action: Check the file path and permissions and try again.
24005: Unable to create controlfile.
Cause: Failed to create a control file.
Action: Check the file path and permissions and try again.
24006: Unable to load controlfile %1$s.
Cause: Cannot load the control file.
Action: Check the file path and permissions and try again.
24007: Invalid control file record %1$d.%2$d.
Cause: The record was not found in the control file.
Action: Verify that the correct control file is specified and try again.
24008: Unable to add tablespace name %1$s.
Cause: Failed to add a tablespace.
Action: Verify the tablespace name is not a duplicate.
24009: Tablespace %1$s is not empty.
Cause: The tablespace is not empty.
Action: Check data files in the tablespace and try again.
24010: Tablespace %1$s is in online backup mode.
Cause: The tablespace is involved in an online backup.
Action: Try again after the online backup is complete.
24011: Tablespace %1$s is not in online backup mode.
Cause: The tablespace is not involved in an online backup.
Action: Try again after an online backup has started.
24012: No such tablespace %1$d.
Cause: Failed to add the tablespace.
Action: Verify a tablespace exists and try again.
24013: No space left in tablespace %1$d.
Cause: No space is left in the control file.
Action: Check the control file and try again.
24014: Datafile %1$d is not online.
Cause: Cannot use the datafile.
Action: Contact the technical support team.
24015: Datafile %1$d was not found.
Cause: Cannot find the datafile.
Action: Contact the technical support team.
24016: Datafile %1$d in tablespace %2$d was not found.
Cause: Cannot find the datafile.
Action: Contact the technical support team.
24017: No datafile left.
Cause: No datafile left.
Action: Check the control file and try again.
24018: CF-DD correction is required due to wrong CF/DD info or added/dropped datafiles while recovery process.
Cause: CF-DD correction is required due to wrong CF/DD info or added/dropped datafiles while recovery process.
Action: Contact the technical support team for the guide.
24019: Critical error occurred.
Cause: A critical error occurred in the control file.
Action: Contact the technical support team.
24020: No such logfile ID %1$d.
Cause: Cannot find the ID of the log file.
Action: Check the log file and try again.
24021: Unable to add additional log files.
Cause: Cannot add log files.
Action: Check the values of MAXLOGGROUPS and MAXLOGMEMBERS.
24022: Duplicate log file ID %1$d exists.
Cause: The log file ID is already in use.
Action: Choose a new logfile ID and try again.
24023: Unable to drop log file %1$s.
Cause: Failed to delete the log file.
Action: Locate the cause of the failure and try again.
24024: Unable to drop log member %1$s.
Cause: Failed to delete the log member.
Action: Check the number of log files and see if they are archived.
24025: Unable to drop system tablespace datafile %1$d.
Cause: Cannot drop the datafile of the system tablespace.
Action: Check the datafile to be deleted.
24026: Blocksize (%1$d) does not match DB_BLOCK_SIZE (%2$d).
Cause: DB_BLOCK_SIZE is invalid.
Action: Modify DB_BLOCK_SIZE and try again.
24027: Invalid DB_NAME value in .tip file: ‘%1$s’ should be ‘%2$s’.
Cause: The DB name does not match with the control file.
Action: Check the [database sid].tip file and the control file.
24028: Unable to begin online backup ‘%1$s’ – %2$s.
Cause: Online backup is available only in archive log mode.
Action: Change the DB setting to archive log mode.
24029: Unable to shut down: file %1$d (‘%2$s’) has online backup set.
Cause: Online backup is being processed.
Action: End the online backup and close DB.
24030: Unable to create more tablespace.
Cause: Cannot create more tablespace.
Action: Check the value of MAXDATAFILES and modify it if necessary.
24031: Unable to create more data files.
Cause: Cannot create more data files.
Action: Check the value of MAXDATAFILES and modify it if necessary.
24032: Archive filename is too long: must be less than %1$d.
Cause: The absolute path of the archive is too long.
Action: Specify a shorter name or absolute path.
24033: Unable to add log member %1$s.
Cause: Cannot add a log member.
Action: Check the value of MAXLOGMEMBERS and modify it if necessary.
24034: Unable to change datafile #%1$d status: %2$s.
Cause: Cannot change the condition of the data file.
Action: Contact the technical support team.
24035: Unable to read file %1$d at this time.
Cause: The datafile is offline.
Action: Set the file to online and try again.
24036: Unable to modify file %1$d.
Cause: The datafile is read-only.
Action: Change the read/write settings of the file and try again.
24037: Incompatible control file version.
Cause: The control file is not compatible.
Action: Check the version information of the control file and the server.
24038: Tablespace ‘%1$s’ is offline.
Cause: The tablespace must be online.
Action: Set the tablespace to online and try again.
24039: Unable to modify tablespace ‘%1$s’.
Cause: The tablespace is read-only.
Action: Change the tablespace settings and try again.
24040: Unable to set tablespace ‘%1$s’ as read-only: %2$s.
Cause: Cannot set the tablespace as read-only.
Action: Check the tablespace type and try again.
24041: Unable to set datafile #’%1$d’ as read-only: %2$s.
Cause: Cannot set the datafile as read-only.
Action: Check the data file type and try again.
24042: Tablespace ‘%1$s’ is not read only: %2$s.
Cause: Cannot make the tablespace read-only.
Action: Check the tablespace settings and try again.
24043: Unable to clear logfile: %1$s.
Cause: Cannot clear the logfile.
Action: Contact the technical support team.
24044: Redo thread #%1$d is too big (max %2$d).
Cause: No space available for redo threads.
Action: Contact the technical support team.
24045: Unable to change thread #%1$d status: %2$s.
Cause: Cannot modify the properties of the redo/flashback thread.
Action: Check the condition of the redo/flashback thread and try again.
24046: Tablespace ‘%1$s’ is a temporary tablespace.
Cause: Temporary tablespace.
Action: Contact the technical support team.
24047: Tablespace ‘%1$s’ is in the middle of backup.
Cause: The tablespace is involved in an online backup.
Action: Try again after the online backup is complete.
24048: File %1$d is in the middle of backup.
Cause: The datafile is involved in an online backup.
Action: Try again after the online backup is complete.
24049: Unable to open datafile #%1$d: %2$s.
Cause: Cannot open the datafile because datafile information does not match the control file.
Action: Check the condition of the control file and the datafile and try again.
24050: Database cannot be run in single instance mode.
Cause: Cannot run the database in single instance mode.
Action: Use cluster database.
24051: Cannot take tablespace ‘%1$s’ offline.
Cause: Cannot take the tablespace offline.
Action: Check the condition of the tablespace and try again.
24052: Only allowed if media recover is enabled.
Cause: Media recover is not enabled.
Action: Check the log mode of the database and try again.
24053: Cannot recover the redo thread #%1$d because it is closed.
Cause: Cannot recover the redo thread.
Action: Check the log files that belong to the redo thread.
24054: The comp version of the control file does not match.
Cause: The comp version of the control file does not match that of a server.
Action: Check the comp versions of the control file and the server, and recreate a control file if necessary.
24055: None of the tablespaces are in the online backup mode.
Cause: Cannot perform end backup.
Action: Try again after an online backup is started.
24056: Flashback thread #%1$d is too big (max %2$d).
Cause: No space available for flashback threads.
Action: Contact the technical support team.
24057: No such redo thread %1$d.
Cause: Cannot find the redo thread.
Action: Check the configuration and try again.
24058: No such backup set %1$d.
Cause: Cannot find the backup set.
Action: Verify that the backup set exists and try again.
24059: Tablespace %1$s not in backup set %2$d.
Cause: Cannot find the tablespace in the given backup set.
Action: Check the backup set.
24060: No such controlfile section %1$s.
Cause: Cannot find the given section.
Action: Verify that the given section exists and try again.
24061: Controlfile section %1$s has more entries than %2$d.
Cause: Cannot resize the given section.
Action: Try again with a larger size.
24062: Invalid tsid bitmap.
Cause: Invalid tsid bitmap.
Action: Verify that tsid bitmap is in correct format.
24063: Backup set %1$u already exists.
Cause: Cannot add backup set.
Action: Retry after deleting backupset.
24064: The backup archive log file %1$s is not valid.
Cause: The backup archive log file %1$s is not valid.
Action: Retry the operation with a valid backup archive log file.
24065: Failed to open backup directory %1$s.
Cause: Failed to open backup directory %1$s.
Action: Retry the operation with a valid backup directory.
24066: Failed to get free backup set record number in the control file.
Cause: Failed to get free backup set record number in the control file.
Action: Retry the backup operation after deleting old backup sets.
24067: The base backup set #%1$d for the backup set #%2$d does not exist.
Cause: The base backup set #%1$d for the backup set #%2$d does not exist.
Action: Retry the operation after performing a full backup.
24068: The latest backup set #%1$d is backed up without archivelogs.
Cause: The latest backup set #%1$d is backed up without archivelogs.
Action: Retry without using –with-archivelog option.
24069: Can’t find the target archive log in CF.
Cause: Can’t find the target archive log in CF.
Action: Check whether the target archive log exists in CF.
24070: Failed to get free backup archivelog record number in the control file.
Cause: Failed to get free backup archivelog record number in the control file.
Action: Retry the backup operation after deleting old backup archivelog.
24071: Datafile backup is successful, but cannot backup archivelogs.
Cause: Datafile backup is successful, but cannot backup archivelogs.
Action: Database must be single or share same LOG_ARCHIVE_DEST on Active Storage.
24072: A cleanup is being performed for the previous RMGR operation.
Cause: A cleanup is being perfromed for the previous RMGR operation.
Action: Retry the operation after a while.
24073: The thread count specified for parallel operation exceeds the thread count limit (thread count limit = %1$d).
Cause: The thread count specified for parallel operation exceeds the thread count limit (thread count limit = %1$d).
Action: Retry the operation with a valid thread count.
24074: Thread allocation failed because the thread count specified for parallel operation exceeds the idle thread count (idle thread count = %1$d).
Cause: Thread allocation failed bacause the thread count specified for parallelopeartion exceeds the idle thread count (idle thread count = %1$d).
Action: Retry the operation with a valid thread count.
24075: Failed to perform end backup operation (tsid = %1$d).
Cause: Failed to perform end backup operation (tsid = %1$d).
Action: Retry the operation after performing end backup.
24076: Invalid dfid (dfid = %1$d).
Cause: Invalid dfid (dfid = %1$d).
Action: Retry the operation with a valid dfid.
24077: The validation target datafile does not exist (dfid = %1$d).
Cause: The validation target dataifle does not exist (dfid = %1$d).
Action: Retry the operation with a valid dfid.
24078: The validation target datafile is inaccessible (dfid = %1$d).
Cause: The validation target datafile is inaccessible (dfid = %1$d).
Action: Retry the operation with a valid dfid.
24079: The validation is canceled and cleanup is ongoing.
Cause: The validation is canceled and cleanup is ongoing.
Action: Retry the operation.
24080: The previous RMGR validation is ongoing.
Cause: The previous RMGR validation is ongoing.
Action: Retry the operation after a while.
24081: Thread allocation failed because the thread count specified for paralleloperation exceeds the netbackup limit (netbackup lmit count = %1$d).
Cause: Thread allocation failed bacause the thread count specified for parallelopeartion exceeds the netbackup limit (netbackup limit count = %1$d).
Action: Retry the operation with a valid thread count.
24082: Netbackup parameters are not properly specified in tip file (%1$s).
Cause: Netbackup parameters are not properly specified in tip file (%1$s).
Action: Retry the operation after specifying netbackup parameters properly in tip file.
24083: Failed to get DOP of netbackup.
Cause: Failed to get DOP of netbackup.
Action: Retry the operation after checking the connection with the netbackup master.server.
24084: Failed to open a netbackup session.
Cause: Failed to open a netbackup session.
Action: Retry the operation after checking the connection with the netbackup master.server.
24085: Failed to commit the netbackup TX. The current backup operation is canceled.
Cause: Failed to commit the netbackup TX. The current backup operation is canceled.
Action: Retry the operation after checking the connection with the netbackup master.server.
24086: Failed to delete the backupset, or could not find it in NetBackup storage.
Cause: Failed to delete the backupset, or could not find it in NetBackup storage.
Action: Check the connection and files at NetBackup storage, or delete the backupset with ‘–cf-only’ option.
24087: Cannot access netbackup storages. USE_NBU_FOR_BACKUPSET or NBU_ARCHIVELOG_SEARCH is not specified in tip file.
Cause: Cannot access netbackup storages. USE_NBU_FOR_BACKUPSET or NBU_ARCHIVELOG_SEARCH is not specified in tip file.
Action: Retry the operation after specifying USE_NBU_FOR_BACKUPSET and NBU_ARCHIVELOG_SEARCH in tip file.
24088: NBU_CLIENT_COUNT must be in the range of 1-10 (current value: %1$d).
Cause: NBU_CLIENT_COUNT must be in the ragne of 1-10 (current value: %1$d).
Action: Retry the operation after checking NBU_CLIENT_COUNT.
24089: NBU_BACKUP_INST_SID must be set to the instance ID of NBU_CLIENT_HOSTNAME_0 in tip file (current settings: NBU_BACKUP_INST_SID=%1$s, NBU_CLIENT_HOSTNAME_0=%1$s).
Cause: NBU_BACKUP_INST_SID must be set to the instance ID of NBU_CLIENT_HOSTNAME_0 in tip file (current settings: NBU_BACKUP_INST_SID=%1$s, NBU_CLIENT_HOSTNAME_0=%1$s).
Action: Retry the operation after checking NBU_BACKUP_INST_SID and NBU_CLIENT_HOSTNAME_0 in tip file.
24090: Failed to get the hostname of system.
Cause: Failed to get the hostname of system.
Action: Retry the operation after checking the hostname of system.
24091: Netbackup parameter is inconsistent (%1$s).
Cause: Netbackup parameter is inconsistent (%1$s).
Action: Retry the operation after checking the netbackup parameter in tip file.
24092: Netbackup processes are still performing the previous operation (ongoing process count = %1$d).
Cause: Netbackup processes are still performing the previous operation (ongoing process count = %1$d).
Action: Retry the operation after a while.
24093: NetBackup operation is canceled/stopped. NetBackup slaves aborts.
Cause: NetBackup operation is canceled/stopped. NetBackup slaves aborts.
Action: NetBackup operation is canceled/stopped. NetBackup slaves aborts.
24095: Data file is more recent than control file. Get current control file, or recreate control file and try again.
Cause: CF SEQ in DF header is larger than CF SEQ in CF header.
Action: Check whether given control file is backup file, or recreate the control file.
24096: Failed to assign datafile (dfid = %1$u)
Cause: Failed to assgin datafile (dfid = %1$u)
Action: Check if the given datafile exists in the backup set
24097: Failed to find the archive logs after the last archive log backup.
Cause: Failed to find the archive logs after the last archive log backup.
Action: Check if the target archive logs are in the backup_dest directory.
24098: Failed to find a tablespace to backup/restore.
Cause: Failed to find a tablespace to backup/restore.
Action: Check if the rmgr options are too much for the tablespaces available.
24099: Memory tablespace aalready exists.
Cause: Memory tablespace aalready exists.
Action: Drop the existing memory tablespace first.
24100: Memory tablespace cannot have datafiles more than ‘%1$d’.
Cause: Memory tablespace has too many datafiles.
Action: Check the number of datafiles.
24101: No free space for memory tablespace.
Cause: The size of memory tablespace exceeds the maximum size allowed.
Action: Check the size of memory tablespace.
24102: Current log file %1$d is still open.
Cause: Cannot disable the corresponding redo thread.
Action: Check the configuration or, tbdown normally and try it on MOUNT mode.
24103: Failed to find a readonly or an offline tablespace with the given option.
Cause: Failed to find a readonly or an offline tablespace with the given option.
Action: Check the status of the tablespaces and –skip-readonly / –skip-offline options.
24104: If datafiles are the backups, please restore the backup controlfile together or re-create a new controlfile.
Cause: The controlfile ckpt_tsn(%1$s) and the datafiles’ ckpt_tsn(%2$s) do not match.
Action: Please check the backup controlfile or the online redo logs after the backup.
24105: The option ‘–for-standby’ needs the latest backup set to be FOR_STANDBY.
Cause: The option ‘–for-standby’ needs the latest backup set to be FOR_STANDBY.
Action: The option ‘–for-standby’ needs the latest backup set to be FOR_STANDBY.
24106: Using netbackup dummy library. Do not use netbackup with dummy library.
Cause: Using netbackup dummy library. Do not use netbackup with dummy library.
Action: Using netbackup dummy library. Do not use netbackup with dummy library.
24107: Failed to add tablespace: could not aquire tablespace section record.
Cause: Cannot aquire tablespace section record in controlfile.
Action: Try again after previous addition of tablespace is resolved.
24108: RMGR VALIDATION FAILED
Cause: RMGR VALIDATION FAILED
Action: Retry the operation after a while.
24109: Backup set(%1$d) not found. Specify the path actually located.
Cause: Backup set(%1$d) not found. Specify the path actually located.
Action: Backup set(%1$d) not found. Specify the path actually located.
24110: NBU_CLIENT_HOSTNAME_0 must start with the hostname first with case sensitive. (current settings: NBU_CLIENT_HOSTNAME_0=%1$s, hostname=%2$s).
Cause: NBU_CLIENT_HOSTNAME_0 must start with the hostname first with case sensitive. (current settings: NBU_CLIENT_HOSTNAME_0=%1$s, hostname=%2$s).
Action: Retry the operation after checking NBU_CLIENT_HOSTNAME_0 and hostname in tip file.
24111: Backup datafiles need more redo logs at least until END_BACKUP to recover.
Cause: Backup datafiles need more redo logs at least until END_BACKUP to recover.
Action: Please restore more archive/online redo logs for appropriate recovery.
24112: Redo logfile generation time between the nodes is abnormal. Please check the system time.
Cause: Highly possibly, the system time between the nodes may vary.
Action: For now, please recover the DB with TSN based recovery (until change).
24113: All log files of this thread are never used at least once. (thread id=%1$d).
Cause: All log files of this thread are never used at least once. (thread id=%1$d).
Action: Please, check all the log files’ seqno and try again.
24114: Backing up archive log files from NetBackup(%1$s) to NetBackup is forbidden.
Cause: Backing up archive log files from NetBackup(%1$s) to NetBackup is forbidden.
Action: Change the NBU parameters or execute ‘–with-archivelog’
24115: Backing up archive log files with ‘–delete-original’ needs all standby nodes connected.
Cause: Backing up archive log files with ‘–delete-original’ needs all standby nodes connected.
Action: Please check all standby nodes are connected to all DB instances.
24116: Can’t find any backup archive logfile between %1$u and %2$u in CF (thread: %3$u, resetlogs: %4$d).
Cause: Can’t find any backup archive logfile between %1$u and %2$u in CF (thread: %3$u, resetlogs: %4$d).
Action: Please check thread id, resetlogs, v$backup_archived_log, and actual backup path whether any exists.
24117: Tablespace ‘%1$s’ must be offline for Online Media Recovery.
Cause: Tablespace ‘%1$s’ must be offline for Online Media Recovery.
Action: Set the tablespace ‘%1$s’ to offline and try recovery again.
24118: All the specified tablespaces must be offline.
Cause: All the specified tablespaces must be offline.
Action: All the specified tablespaces must be offline.
24119: NetBackup operation is canceled/stopped. NetBackup slaves abort.
Cause: NetBackup operation is canceled/stopped. NetBackup slaves abort.
Action: NetBackup operation is canceled/stopped. NetBackup slaves abort.
24120: Unexpected block number(%1$u) of the block is read. (expected:%2$u )
Cause: Unexpected block number(%1$u) of the block is read. (expected:%2$u )
Action: Confirm the actual block is not corrupted on the disk.
24121: Failed to find backup file %1$s among backup paths %2$s.
Cause: Failed to find backup file %1$s among backup paths %2$s.
Action: Retry the operation with a valid backup directory and file.
24122: No such backup archivelog set %1$d.
Cause: Cannot find the backup archivelog set.
Action: Verify that the backup archivelog set exists and try again.
24123: Failed to find marker before change “UINT64_FMT(1$)” for thread %2$d.
Cause: Failed to perform flashback database operation.
Action: Check flashback marker status and list.
24124: Flashback logging is not on.
Cause: Flashback logging is not on.
Action: Activate flashback logging and retry.
24125: No such flashback thread %1$d.
Cause: Cannot find the flashback thread.
Action: Check the configuration and try again.
24126: Could only flashed back to the marker tsn %1$u, because CF-DD correction is required due to dropped datafiles. %2$s
Cause: Could only flashed back to the marker tsn %1$u, because CF-DD correction is required due to dropped datafiles.
Action: %2$s
24127: Database flashed back to TSN %1$u, but CF-DD correction is required because the datafiles that were dropped later exist now. %2$s
Cause: Database flashed back to TSN %1$u, but CF-DD correction is required because the datafiles that were dropped later exist now. %2$s
Action: %2$s
24128: Flashback database must be done beforehand.
Cause: Flashback database must be done beforehand.
Action: Please check if the database has been flashed back in advance.
24129: Shrunken datafile(TS #%1$u, DF #%2$u) cannot be flashed back and should be taken offline.
Cause: Shrunken datafile(TS #%1$u, DF #%2$u) cannot be flashed back and should be taken offline.
Action: Take shrunken datafiles offline and try again.
24130: Due to CF-DD correction, some TS/DF which turned into read-write or online need recovery. Please request %1$s.
Cause: Due to CF-DD correction, some TS/DF which turned into read-write or online need recovery. Please request %1$s.
Action: Please request %1$s.
24131: Can’t find the target archive log in CF to %1$s (%2$s: %3$d).
Cause: Can’t find the target archive log in CF to %1$s (%2$s: %3$d).
Action: Check whether the target archive log exists in CF or use ‘–arc-dest-force’ option.
24132: Can’t add a flashback marker due to some instance down.
Cause: All nodes must be open to add a flashback marker.
Action: Check all nodes are open and try again.
24133: Can’t find the online flashback logfile in group #%1$u to be recovered by media recovery.
Cause: All the online flashback logfiles must exist or the flashback logging must be off.
Action: Restore the online flashback logfiles or turn off the flashback logging.
24134: Standby Redo thread #%1$d is too big (max %2$d).
Cause: No space available for standby redo threads.
Action: Contact the technical support team.
24135: If the database flashed back at least once, reboot is required after Media Recovery.
Cause: If the database flashed back at least once, reboot is required after Media Recovery.
Action: Reboot the database.
24136: Archived log thread %1$u, sequence %2$u already exists.
Cause: Cannot add archived log into the Control File.
Action: Contact R&D or re-generate the control file.
24137: Log history thread %1$u, sequence %2$u already exists.
Cause: Cannot add log history into the Control File.
Action: Contact R&D or re-generate the control file.
24138: Failed to execute the rmgr client command.
Cause: Failed to execute the rmgr client command.
Action: Check the client trace log.
24139: Unexpected block(%1$u) is read. (expected:%2$u, tsid: %3$u, dfid: %4$u)
Cause: Unexpected block(%1$u) is read. (expected:%2$u, tsid: %3$u, dfid: %4$u)
Action: Confirm the actual block is not corrupted on the disk.
24140: Cannot raise to read only server mode because temporary tablespace not exists.
Cause: Does not exist temporary tablespace information in controlfile.
Action: Check the control file for temporary tablespace.
24141: Cannot create the standby replication because the backup set is invalid.
Cause: Cannot find all end backup cvs until the recovery stop point.
Action: Check the backup procedures and retry backup correctly.
24142: Standby needs media recovery.
Cause: Standby terminated abnormally.
Action: Perform media recovery.
24143: The maximum number of instances of controlfile and IPARAM(MAX_INSTANCE_COUNT) does not match.
Cause: The maximum number of instances of controlfile and IPARAM(MAX_INSTANCE_COUNT) does not match.
Action: Modify the value of IPARAM(MAX_INSTANCE_COUNT) or recreate the controlfile.
24144: NetBackup backup/restore timed out.
Cause: NetBackup backup/restore timed out.
Action: Check the NetBackup status.
24145: Cannot recover because begin/end backup is in progress.
Cause: Cannot recover because begin/end backup is in progress.
Action: Try again after the online backup is complete.
24146: Tablespace ‘%1$s’ is online.
Cause: The tablespace must be offline.
Action: Set the tablespace to offline and try again.
24147: Metadata of log files in CF cache is duplicated or corrupt.
Cause: Some metadata of log files is duplicated or corrupt.
Action: Please contact the support team.
24148: Unable to modify file %1$d.
Cause: The datafile is being created (in creation).
Action: Try again after the datafile %1$d is successfully created.
24149: New blocks found in logfile in group #%1$d after %2$u by THREAD #%3$d.
Cause: New blocks found in logfile in group #%1$d after %2$u by THREAD #%3$d.
Action: Investigate if THREAD #%3$d is still in use.
24150: Cannot take datafile #%1$d offline.
Cause: Cannot take the datafile offline.
Action: Check the condition of the datafile and try again.
24151: Checkpoint progress cannot be cleared.
Cause: Checkpoint progress cannot be cleared.
Action: Please contact the support team.
24152: File DB_NAME(‘%1$s’) does not match control file DB_NAME(‘%2$s’).
Cause: The DB_NAME(‘%1$s’) of the file does not match the DB_NAME(‘%2$s’) in the control file.
Action: Verify and ensure that the DB_NAME for both the file and the control file are correct.
24153: File DB_ID(%1$d) does not match control file DB_ID(%2$d).
Cause: The DB_ID(%1$d) of the file does not match DB_ID(%2$d) in the control file.
Action: Verify and ensure that the DB_ID for both the file and the control file are correct.
Tibero Error Message 25000~25999
25001: XA protocol error.
Cause: Invalid XA protocol.
Action: Verify the protocol is valid.
25002: XA transaction branch was not found.
Cause: The XA branch does not exist.
Action: Verify the XID is correct.
25003: Unable to associate the XA transaction branch: local transaction is ongoing.
Cause: Failed to perform the XA command because an ongoing local transaction exists.
Action: Commit or roll back the local transaction first, and then perform the XA command.
25004: XA asynchronous feature is not supported by server.
Cause: An attempt was made to use an XA asynchronous command.
Action: XA asynchronous commands are not supported.
25005: Invalid arguments were specified.
Cause: An invalid flag was included in the XA command.
Action: Check the flag again.
25006: XA transaction branch is in rollback-only status for an unspecified reason.
Cause: The XA branch is in rollback-only status.
Action: Try xa_rollback.
25007: XA transaction branch is read-only.
Cause: The XA branch is in read-only status because no active transaction exists.
Action: Automatically terminate the branch.
25008: Duplicate XID exists.
Cause: There is another XA branch with the same XID.
Action: Check the XID or try again with another XID.
25009: Resource manager has indicated a problem with an XA branch.
Cause: Cannot perform the task because the global TX and XA branch loose_coupling properties mismatch.
Action: Verify that the XA command is correct or roll back the branch and try again.
25010: Transaction branch has been heuristically committed.
Cause: The XA branch has already been committed.
Action: Verify that the XA command is valid, or remove the terminated XA branch with xa_forget.
25011: Transaction branch has been heuristically rolled back.
Cause: The XA branch has already been heuristically rolled back.
Action: Verify that the XA command is valid, or remove the terminated XA branch with xa_forget.
25012: Transaction branch has been heuristically committed or rolled back.
Cause: The XA branch was already committed or rolled back.
Action: Verify that the XA command is valid, or remove the terminated XA branch with xa_forget.
25013: XA branch has timed out (sesswt).
Cause: The transaction was rolled back because the requested command could not be completed before session waiting time expired.
Action: Try again.
25014: No prepared XA transaction found with transaction ID %1$s.
Cause: Cannot find a prepared XA transaction with the requested transaction ID.
Action: Verify the transaction ID is valid.
25015: Unable to create more XA branches: maximum number of branches reached.
Cause: Cannot create any more XA branches – limit set in XA_MAX_BRANCH_CNT has been reached.
Action: Try later.
Tibero Error Message 26000~26999
26003: LOB object is too large.
Cause: The LOB type data is too large.
Action: Check if the size of the LOB type object is larger than the maximum limit (4GB * DB block size).
26004: Offset is out of range.
Cause: The LOB offset is greater than the length of the LOB.
Action: Specify a valid offset.
26005: Trim length is out of range.
Cause: The trim length is greater than the length of the LOB.
Action: Specify a valid length.
26006: LOB is read-only.
Cause: An attempt was made to write to a LOB opened in read-only mode.
Action: Open the LOB in read/write mode.
26007: Row containing LOB column is not locked.
Cause: The row that contains a LOB column to be used in a read/write mode is not locked.
Action: Lock the row and reopen it.
26008: LOB was not found.
Cause: The specified LOB data does not exist.
Action: The row may have been deleted. Verify that the LOB data exists and try again.
26009: Invalid LOB locator specified.
Cause: The DBA or ROWNO of the specified LOB locator is invalid.
Action: Try again with a valid LOB locator.
26010: Unable to write with a terminated transaction.
Cause: Cannot write to a LOB using a terminated transaction.
Action: Open the LOB data after restarting the transaction.
26012: Invalid LOB locator length.
Cause: The length of the specified LOB locator is invalid.
Action: Try again with a valid LOB locator.
26013: Invalid LOB locator segment ID.
Cause: The segment ID of the specified LOB locator is invalid.
Action: Try again with a valid LOB locator.
26014: Invalid LOB ID of LOB locator.
Cause: The LOB ID of the specified LOB locator is invalid.
Action: Try again with a valid LOB locator.
26019: Uninitialized LOB locator was specified.
Cause: The LOB locator has not been initialized.
Action: Initialize then search for the LOB.
26020: Cannot read a LOB object in a remote server.
Cause: Cannot read a LOB object in a remote server.
Action: Change the query.
26021: No data in the LOB index.
Cause: DML failed because there is no data in the LOB index.
Action: Recover the LOB index data.
Tibero Error Message 27000~27999
27001: Invalid table information specified.
Cause: Invalid table information is returned when the transaction is in prepared state.
Action: Enter correct table information.
27002: Given data does not complete a row.
Cause: The last row of the given data stream is not complete.
Action: Send the remaining data.
27003: Data stream is invalid.
Cause: The data stream is invalid.
Action: Send the correct data.
27004: Invalid LONG column position.
Cause: The position of the LONG column is invalid.
Action: Place the LONG column in the last part of the table.
27005: Direct path buffer is empty.
Cause: The DPL buffer is empty.
Action: The data has not yet been loaded. Load the data and then flush it.
27006: A transaction already exists.
Cause: A transaction already exists before the direct path has started.
Action: Commit or roll back the existing transaction.
27007: Partitioned tables are not supported.
Cause: Direct path loading is not supported for partitioned tables.
Action: REMOVED.
27008: Unsupported table schema.
Cause: Direct path loading is not supported for the schema.
Action: Use conventional loading method instead.
27009: DPL is not yet prepared.
Cause: DPL has not been started.
Action: Start a prepare protocol first.
27010: Cannot perform DPL for temporary table.
Cause: Cannot perform DPL for temporary table.
Action: Only CPL is supported for temporary table.
27011: The table has too many columns.
Cause: The table has too many columns.
Action: Use the conventional loading method.
27012: DPL failed due to lack of resources.
Cause: DPL failed due to lack of resources.
Action: Free sufficient resources and continue.
27013: Unsupported table schema.
Cause: Parallel DPL is not supported for the schema.
Action: DPL is not supported for an indexed table.
27014: DPL failed due to message uncompression error.
Cause: DPL failed due to message uncompression error.
Action: Check if client library settings are correct.
27015: DPL failed while rebuilding index on dp finish phase.
Cause: DPL failed while rebuilding index on dp finish phase.
Action: Check sys.log to determine the cause of the problem.
27016: The expression information is not valid.
Cause: DPL failed because the expression information was set incorrectly.
Action: Correct the expression information.
Tibero Error Message 28000~28999
28009: Unable to access LONG or LOB columns through RemoteDB.
Cause: An attempt was made use RemoteDB to refer to an object with LONG or LOB columns.
Action: Modify the query.
28010: Maximum number of group_ids (255) has been reached.
Cause: No more than 255 group_ids are allowed at a time.
Action: Modify the query.
28011: Pivot type expression %1$s cannot be used here.
Cause: The pivot type expression was used in an invalid location.
Action: Modify the query.
28012: Index ‘%1$s.%2$s’ is in an unusable state.
Cause: DML statements cannot be executed on an unusable index.
Action: Change the condition of the index.
28013: Index ‘%1$s.%2$s’ is in an unusable state.
Cause: Index hints cannot be specified on an unusable index.
Action: Change the condition of the index.
28014: Duplicate outline.
Cause: The outline name cannot be used because the name is already in use.
Action: Use another outline name.
28015: Column ‘%1$s.%2$s’ has invalid statistics.
Cause: Column ‘%1$s.%2$s’ has invalid statistics.
Action: Delete or regather statistics using the dbms_stat package.
28016: Feature not yet implemented.
Cause: This feature is not yet implemented.
Action: Check whether a feature which is not yet implemented was used.
28017: Logical error in transformer.
Cause:
Action:
28018: Invalid ndv on column ‘%1$s.%2$s’ frequency histogram (Current value: %3$d).
Cause: Each frequency histogram ndv value must be 0 or 1.
Action: Delete or regather statistics using the dbms_stats package.
28019: Maximum number of group keys(128) has been reached.
Cause: No morder than 128 group keys are allow for parallel group by.
Action: Set the parameter _OPT_ENABLE_GROUP_BY_PARALLEL to N.
28020: Too many expressions used.
Cause: Too many expressions are used, which may cause out-of-memory in optimizer.
Action: Reduce the number of expressions in the SQL statement, or adjust the value of parameter _OPT_BM_MEMORY_LIMIT_RATIO (if OOM is not expected).
28021: Too many number of pp nodes.
Cause: Too many number of pp nodes used.
Action: Reduce the number of pp nodes in the SQL statement, or adjust the value of parameter _OPT_PPN_ID_MAX_SIZE.
