‘Ctrl+F’로 에러 메시지 번호를 검색하시면 문제 발생 원인과 해결 방법을 빠르게 확인하실 수 있습니다.

---

Tibero Error Message 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.

---

Tibero Error Message 2000~2999

2001: Completed successfully with warnings or additional information.
Cause: The function has concluded successfully but with warnings or additional information related to the results.
Action: Check the warnings and additional information with the GetDiagField() function.

2002: DSN (Database Source Name) file was not found.
Cause: DSN file could not be found.
Action: Check the dsn file in the ‘client/config’ directory under the database home directory.

2003: DSN (Database Source Name) file is corrupted.
Cause: DSN file is corrupted.
Action: Check the dsn file in the ‘client/config’ directory under the database home directory.

2004: DSN (Database Source Name) file format is invalid.
Cause: DSN file format is invalid.
Action: Check the dsn file in the ‘client/config’ directory under the database home directory.

2005: Username is too long: must be less than 128 bytes.
Cause: The user name is too long. User names may not be longer than 128 bytes.
Action: Check the size of the user name in the argument.

2006: Password is too long: must be less than 64 bytes.
Cause: The password is too long. Passwords may not be longer than 63 bytes.
Action: Check the size of the password in the argument.

2007: Table name is too long: must be less than 128 bytes.
Cause: The table name is too long. Table names may not be longer than 128 bytes.
Action: Check the size of the table name in the argument.

2008: Column name is too long: must be less than 128 bytes.
Cause: The column name is too long. Column names may not be longer than 127 bytes.
Action: Check the size of the column name in the argument.

2009: Schema name is too long: must be less than 128 bytes.
Cause: The schema name is too long. Schema names may not be longer than 127 bytes.
Action: Check the size of the schema name in the parameter.

2010: String data was right-truncated.
Cause: Actual data is larger than the buffer.
Action: Check the size of the data buffer.

2011: Wrong parameter number given.
Cause: Invalid parameter number.
Action: Check the parameter number.

2012: Prepared statement is not a cursor specification.
Cause: The prepared statement does not provide a valid cursor specification.
Action: Verify the statement is a SELECT statement.

2013: Invalid column index at descriptor.
Cause: Invalid column index.
Action: Check the descriptor column index.

2014: Invalid record index at descriptor.
Cause: Invalid record index.
Action: Check the descriptor record index.

2015: Client was unable to establish connection.
Cause: Cannot connect to the server.
Action: Verify that the server is running, and check the DB connection settings.

2016: OCIServer or OCISession is not set in OCISvcCtx.
Cause: Server or session handle is not registered as an attribute of OCISvcCtx.
Action: Verify that the OCISvcCtx handle is correctly created.

2017: Open connection already exists.
Cause: Already connected to the server.
Action: Disconnect the server and retry, or continue with desired actions.

2018: No open connection.
Cause: Not connected to the server.
Action: Reconnect to the server and try action again.

2019: Program type out of range.
Cause: The SQL_C type is not supported.
Action: Check the SQL_C type and change it.

2020: Invalid SQL data type.
Cause: Unsupported SQL data type.
Action: Check the SQL data type and change it.

2021: Associated statement is not prepared.
Cause: SQL statement has not been prepared.
Action: Execute when SQL statement is prepared.

2022: Invalid use of null pointer.
Cause: Invalid null pointer was used.
Action: Check the null pointer.

2023: Invalid argument type.
Cause: Invalid argument type.
Action: Check the argument type.

2024: Invalid argument value.
Cause: Invalid argument value.
Action: Check the argument value.

2025: Function sequence error.
Cause: Invalid function sequence.
Action: Check the sequence of functions.

2026: Attribute was not set.
Cause: Failed to set attributes.
Action: Check the attributes.

2027: Invalid transaction operation.
Cause: Invalid transaction operation.
Action: Check whether the current transaction operation is valid.

2028: Cannot modify the implementation row descriptor.
Cause: Cannot modify IRD (Implementation Row Descriptor).
Action: Check the target descriptor type to modify.

2029: Invalid use of an automatically allocated descriptor handle.
Cause: Invalid use of an automatically allocated descriptor handle.
Action: Create a new descriptor handle.

2030: Inconsistent descriptor information.
Cause: Invalid descriptor information.
Action: Check the binding descriptor.

2031: Invalid attribute value.
Cause: Invalid attribute value.
Action: Confirm that the value can be specified for the current attribute.

2032: Invalid string or buffer length.
Cause: Invalid length of character string.
Action: Change the length of the string.

2033: Invalid descriptor field identifier.
Cause: The descriptor field identifier is undefined or not implemented.
Action: Check the descriptor field identifier.

2034: Invalid descriptor field identifier.
Cause: The specified descriptor field is read-only.
Action: Check the attributes of the descriptor field.

2035: Invalid attribute/option identifier.
Cause: Invalid attribute or option.
Action: Recheck the attribute or option.

2036: Invalid parameter index.
Cause: Invalid parameter index.
Action: Check the parameter index.

2037: Invalid parameter type.
Cause: Invalid parameter type.
Action: Check the parameter type.

2038: Invalid cursor position.
Cause: Invalid cursor position.
Action: Verify that the cursor position is correct.

2039: Optional feature not yet implemented.
Cause: The function has not yet been implemented.
Action: Use an alternative function.

2040: Invalid cursor state.
Cause: Invalid cursor state.
Action: Check the cursor state.

2041: Required indicator variable was not specified.
Cause: No indicator has been specified.
Action: Specify the indicator.

2042: Savepoint exception.
Cause: Invalid name for the savepoint.
Action: Check the name of the savepoint.

2043: Duplicate cursor name exists.
Cause: Duplicate cursor name detected.
Action: Change the cursor name.

2044: Invalid cursor name.
Cause: Invalid cursor name
Action: Change the cursor name.

2045: Invalid record index number.
Cause: Invalid diagnostics record index
Action: Check the diagnostics record index.

2046: Not yet implemented.
Cause: The function has not been implemented.
Action: Use an alternative function.

2047: Attribute has not been implemented.
Cause: The attribute has not been implemented.
Action: Use an alternative attribute.

2048: Data source was not found.
Cause: Unable to find DSN.
Action: Check whether DSN configuration is valid.

2049: Invalid offset for LOB.
Cause: Invalid offset value for large object (LOB).
Action: Check the offset value of LOB.

2050: Invalid length for LOB.
Cause: Invalid LOB length
Action: Check the LOB length.

2051: Invalid authorization.
Cause: Not authorized to perform this task.
Action: Check the user name and password.

2052: Invalid parameter.
Cause: Invalid environment parameter type.
Action: Check the environment parameter type.

2053: Invalid plan executed.
Cause: Invalid plan was executed.
Action: Check whether the plan ID is valid.

2054: Cursor is already open.
Cause: The cursor is already open.
Action: Check the cursor state.

2055: Cursor is not open.
Cause: Cursor is not open.
Action: Check the cursor state.

2056: Specified SQL statement is NULL.
Cause: Executed SQL statement is NULL.
Action: Check the SQL statement again.

2057: Invalid scroll option.
Cause: Invalid scrollable cursor fetch.
Action: Check whether the cursor type is scrollable.

2058: Invalid data type.
Cause: Data type is unsupported by server.
Action: Check the data type again.

2059: Invalid data length.
Cause: Exceeds the maximum data length supported by server.
Action: Check the data length.

2060: Invalid diagnostics index.
Cause: Invalid diagnostics index
Action: Check the diagnostics index.

2061: Data type is currently unsupported.
Cause: Data type is currently unsupported.
Action: Use an alternative data type.

2062: Type casting is not allowed.
Cause: Unable to change the data type.
Action: Check the data type.

2063: Invalid parameter in/out mode.
Cause: Invalid parameter mode.
Action: Check the parameter mode.

2064: Trailing NULL missing from string bind value.
Cause: There is no NULL at the end of string bind value.
Action: Check the bind value.

2065: Data was truncated.
Cause: Data was too long and was truncated.
Action: Check the data length.

2067: Index out of range.
Cause: Index value was out of range.
Action: Check the index.

2068: Invalid indicator type.
Cause: Invalid indicator type.
Action: Check the indicator type.

2069: I/O read error.
Cause: There is a problem reading from the server.
Action: Check the connection.

2070: I/O write error.
Cause: There is a problem writing to the server.
Action: Check the connection.

2071: I/O close error.
Cause: There is a problem closing the communication with server.
Action: Check the connection.

2072: Invalid buffer length.
Cause: Invalid buffer length.
Action: Check the buffer length.

2073: Invalid handle.
Cause: Invalid handle.
Action: Check whether the handle is valid.

2074: Invalid handle type.
Cause: Invalid handle type.
Action: Check whether or not the handle type is valid.

2075: Invalid DBC handle.
Cause: Invalid connection handle.
Action: Check the connection handle.

2076: Invalid statement handle.
Cause: Invalid statement handle.
Action: Check the statement handle.

2077: Failed to initialize the handle manager.
Cause: Failed to initialize the handle manager.
Action: Check the handle allocation.

2080: CLI Driver manager has not been initialized.
Cause: CLI Driver manager has not been initialized.
Action: Initialize the CLI Driver Manager.

2081: Invalid attempt to fetch before the first row of the result set.
Cause: The specified fetch location is before the first record of the result set.
Action: Specify a valid fetch location.

2082: Invalid socket file descriptor.
Cause: Invalid socket file descriptor.
Action: Check the connection with the server.

2083: Failed to close socket.
Cause: Failed to close socket.
Action: Verify the connection with the server is still available.

2084: Invalid protocol.
Cause: Invalid server connection protocol.
Action: Check the condition of the server and clients.

2085: Invalid LOB locator from server.
Cause: Invalid LOB locator received from server.
Action: Check the LOB locator.

2086: No data.
Cause: No data.
Action: Check the fetch state.

2087: Data is needed.
Cause: The server requires some data.
Action: Ensure the data to be sent is available.

2088: Connection failed.
Cause: Failed to connect to server.
Action: Check the server state.

2089: Failed to disconnect.
Cause: Failed to disconnect.
Action: Check the server state.

2090: Execution failed.
Cause: Failed to execute SQL statements.
Action: Recheck the SQL statements.

2091: Fetching failed.
Cause: Failed to fetch.
Action: Check the cursor state.

2092: Preparation failed.
Cause: Failed to prepare a statement.
Action: Check the execution statement.

2093: Failed to close the cursor.
Cause: Failed to close the cursor.
Action: Check the cursor state.

2094: Failed to commit.
Cause: Failed to commit.
Action: Check the transaction state.

2095: Failed to close session.
Cause: Failed to close the session.
Action: Check the server state.

2096: Session kill failed.
Cause: Failed to end the session.
Action: Check the server state.

2097: Rollback failed.
Cause: Failed to roll back.
Action: Check the transaction state.

2098: Savepoint failed.
Cause: Failed to set a savepoint.
Action: Check the transaction state.

2099: Put data failed.
Cause: Failed to transfer the data.
Action: Verify the data is valid.

2100: Cancel failed.
Cause: Failed to cancel.
Action: Check the transaction state.

2101: Failed to get the length of LOB.
Cause: Failed to obtain the LOB type length.
Action: Check the LOB locator.

2102: Failed to read LOB data.
Cause: Failed to read LOB data.
Action: Check the LOB locator.

2103: Failed to write LOB data.
Cause: Failed to write LOB data.
Action: Check the LOB locator.

2104: Failed to truncate LOB data.
Cause: Failed to truncate LOB data.
Action: Check the LOB locator.

2105: Unable to find specified cursor.
Cause: Unable to find a cursor with the specified name.
Action: Verify the cursor is valid.

2107: DPL is unprepared.
Cause: Failed to prepare DPL.
Action: Verify the operation is valid.

2108: Failed to load stream.
Cause: DPL load stream operation failed.
Action: Verify the operation is valid.

2109: Failed to save data.
Cause: DPL data save operation failed.
Action: Verify the operation is valid.

2110: Failed to abort
Cause: DPL abort operation failed.
Action: Verify the operation is valid.

2111: Failed to finish.
Cause: DPL finish operation failed.
Action: Verify the operation is valid.

2112: Failed to flush rows.
Cause: Failed to flush a particular record.
Action: Verify the operation is valid.

2113: More rows needed after loadstream().
Cause: Additional data is needed after DPL load stream operation.
Action: Provide the necessary data.

2114: No rows to be inserted after loadstream().
Cause: No data has been inserted after DPL load stream operation.
Action: Verify the data is valid.

2115: Failed to read DSN info from ODBC.INI.
Cause: Failed to read DSN information from ODBC.INI.
Action: Check the DSN information.

2116: Completed row delivery to users.
Cause: Data fetch process is complete.
Action: Perform the next required action.

2118: Invalid communication ID.
Cause: Invalid communication ID.
Action: Check the communication ID.

2119: Shutdown failed.
Cause: Failed to shut down.
Action: Check the server state.

2120: Unable to get information about the last SQL statement.
Cause: Failed to obtain information on the last executed SQL statement.
Action: Check whether the operation was valid.

2121: Duplicate request exists.
Cause: The request is a duplicate.
Action: Verify the operation is valid.

2122: Handle is in use.
Cause: The handle is in use.
Action: Check the handle state.

2123: No accessible element exists in data structure.
Cause: There is no error of the descriptor.
Action: Check the index.

2127: Invalid chunk index.
Cause: The chunk index is invalid.
Action: Check the chunk index.

2131: Generic I/O error.
Cause: There is a problem communicating with the server.
Action: Check the connection with the server.

2133: Specified index is greater than number of diagnostics records.
Cause: There are more indexes than diagnostics records.
Action: Check the diagnostics record index.

2134: More data exists for this column.
Cause: There is additional data for the column.
Action: Receive the remaining data by calling the SQLGetData() function.

2135: Current cursor is not updatable.
Cause: The cursor is not updatable.
Action: Change to an updatable cursor and retry.

2136: Row index is out of range.
Cause: The record index is out of range.
Action: Specify a record index smaller than the total number of records in the result set.

2137: Invalid integer buffer size.
Cause: An invalid size was specified for the integer buffer.
Action: Choose a value between 1 to 8 bytes.

2138: Invalid floating point buffer size.
Cause: An invalid size was specified for the floating point buffer.
Action: Choose a value between 4 and 8 bytes.

2139: Connection to server was interrupted but the fail-over successfully reconnected.
Cause: The server connection was terminated but a new connection was made to a server instance with the same DNS name.
Action: The job being executed by the user was canceled and must be restarted.

2140: Unable to connect to unsupported DBMS server.
Cause: An attempt was made to connect to a server that is not supported by the current client.
Action: Use a client that supports connections to this server.

2141: IP address specified in DSN file is too long: cannot be longer than 128 bytes.
Cause: The length of the IP address in the DSN file is longer than 128 bytes.
Action: Check the length of the IP address.

2142: Invalid date/time format.
Cause: Invalid date/time format.
Action: Check the date/time format.

2143: Out of range for numeric.
Cause: Out of range for numeric.
Action: Check the buffer size or the data type.

2144: Invalid bookmark value.
Cause: Invalid bookmark value.
Action: Check if the bookmark value is null or a valid value.

2145: Invalid fetch direction for the current cursor type.
Cause: Invalid fetch direction for the current cursor type.
Action: Verify the cursor type is scrollable.

2146: Current result set cursor type downgraded.
Cause: The current cursor type does not support this query type. The query type will be changed.
Action: Check the query type.

2147: Fractional truncation.
Cause: The numbers after the decimal point are truncated.
Action: Check the buffer size or the data type.

2148: Invalid character value for casting the type.
Cause: Invalid character string value for changing the type.
Action: Verify the character string is valid to change to the specified type.

2149: No available connection exists in the connection pool.
Cause: No available connection exists in the connection pool.
Action: Modify the parameter to change the number of connections available in the connection pool.

2150: Failed to create a daemon thread.
Cause: Failed to create a daemon thread.
Action: Internal error. Contact the technical support team.

2151: Failed to detach the daemon thread.
Cause: Failed to detach the daemon thread.
Action: Internal error. Contact the technical support team.

2152: Invalid descriptor index.
Cause: Invalid descriptor index.
Action: Check if the column/parameter exists for the descriptor index.

2153: Date/time field overflow.
Cause: Invalid date type value.
Action: Check the data value of the date type.

2154: Invalid chunk index.
Cause: The chunk index is invalid.
Action: Check the chunk index.

2155: Option value changed.
Cause: The specified option is not supported. The option value has been changed to other one.
Action: Check the option value.

2156: Cannot find connection information of JEPA (JAVA External Procedure Agent).
Cause: Cannot find connection information of JEPA.
Action: Check the dsn file in the ‘client/config’ directory under the database home directory.

2157: Failed to execute psm.
Cause: Failed to execute psm.
Action: Internal error. Contact the technical support team.

2158: Cannot set the size of TCP Send Buffer.
Cause: Failed to set the size of TCP Send Buffer.
Action: Contact the technical support team.

2159: Cannot set the size of TCP Receive Buffer.
Cause: Failed to set the size of TCP Receive Buffer.
Action: Contact the technical support team.

2160: Unable to set the size of TCP Send Buffer.
Cause: Failed to set the size of TCP Send Buffer.
Action: Contact the technical support team.

2161: Unable to set the size of TCP Receive Buffer.
Cause: Failed to set the size of TCP Receive Buffer.
Action: Contact the technical support team.

2162: Unable to get the size of TCP Send Buffer.
Cause: Failed to get the size of TCP Send Buffer.
Action: Contact the technical support team.

2163: Unable to get the size of TCP Receive Buffer.
Cause: Failed to get the size of TCP Receive Buffer.
Action: Contact the technical support team.

2164: Unable to set the size of TCP Send Buffer.
Cause: Failed to set the size of TCP Send Buffer.
Action: Contact the technical support team.

2165: Unable to set the size of TCP Receive Buffer.
Cause: Failed to set the size of TCP Receive Buffer.
Action: Contact the technical support team.

2166: Unable to get the size of TCP Send Buffer.
Cause: Failed to get the size of TCP Send Buffer.
Action: Contact the technical support team.

2167: Unable to get the size of TCP Receive Buffer.
Cause: Failed to get the size of TCP Receive Buffer.
Action: Contact the technical support team.

2168: Unable to determine the speed of data transmission between server and client.
Cause: Failed to determine the speed of data transmission between server and client.
Action: Contact the technical support team.

2169: Multi thread mode is not set.
Cause: Multi thread mode is not set.
Action: Use the SQLAllocHandle2 or SQLAllocEvn2 API with a true value in the last argument when allocating the env handle.

2170: The necessary attributes are not set in subs handle.
Cause: Topic, callback functions, and listen port information are not set in subscription.
Action: Set all the necessary attributes for the subscription.

2171: The subscription topic has already been registered.
Cause: A client tried to register the same topic using the same DBC handle.
Action: Registering the same topic in the same dbc handle is not allowed.

2172: The subscription topic has not been registered.
Cause: The topic to unregister is not in the list of subscriptions.
Action: Register the topic first.

2173: Unable to find the listener.
Cause: There is no listener listening for the port of the unregistering subscription.
Action: Check if the port of the subscription and the subscription are registered.

2174: Failed to recover select.
Cause: An I/O error occurred during select failover.
Action: Try again later.

2175: Failed to fetch a row.
Cause: Application fetched too many rows.
Action: Reduce the number of fetch request.

2176: Unable to use the parallel DPL option.
Cause: The current server does not support the parallel DPL option.
Action: Use the latest version of the server.

2177: The password has expired(grace).
Cause: The password has expired(grace).
Action: Update the password and then try again.

2178: Unable to fetch subsequent rows.
Cause: Failover was not able to restore the result set to its original state to continue fetching rows.
Action: Re-execute the query to fetch from the first row.

2179: Invalid subscription name.
Cause: The subscription name is invalid or too long.
Action: Use a valid subscription name.

2180: Failed to register the subscription.
Cause: An unregistered subscription name is used or there is a server error.
Action: Use a valid subscription name and check if TQ can be used on the server.

2181: Failed to unregister the subscription.
Cause: There is a server error.
Action: Check if TQ can be used on the server.

2182: DSN configuration is invalid or incomplete .
Cause: Connection information is incorrect or insufficient.
Action: Check if the DSN configuration is incorrect or incomplete.

2183: Unable to handle unexpected incoming message type %1$d.
Cause: An unexpected protocol was received.
Action: Check that the protocol is from a valid context.

2184: Cannot read a LOB object in a remote server.
Cause: Cannot read a LOB object in a remote server.
Action: Change the query.

2185: The password will expire within %1$s days.
Cause: The password will expire within %1$s days.
Action: Update the password.

2186: Failed to compress batch update messages.
Cause: Failed to compress batch update messages.
Action: Check the client library.

2187: Failed to compress DPL messages.
Cause: Failed to compress DPL messages.
Action: Check the client library.

2188: Too many rows returned on exact fetch mode.
Cause: Too many rows returned on exact fetch mode.
Action: Check the requested rows.

2189: Information type out of range.
Cause: Information type is not valid.
Action: Check the information type.

2190: Ending byte of string is invalid.
Cause: Character set cannot interpret the ending of string.
Action: Check the client charset.

2191: Kerberos authentication failed.
Cause: Establishing a GSS-API context was unsuccessful.
Action: Check the kerberos configuration and the service name in the DSN file.

---

Tibero Error Message 3000~3999

3001: Out of memory (shared memory).
Cause: Insufficient shared memory remaining.
Action: To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter.

3002: Out of memory (unable to allocate %1$d bytes of shared pool memory).
Cause: Insufficient shared pool memory remaining.
Action: To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter.

3003: Out of memory (unable to allocate in system memory).
Cause: Insufficient system memory remaining. It maybe one of three cases. 1) The OS memory is full. 2) Total allocated size in DB system is closed to memory limit. 3) Total allocated size in a session is closed to session limit.
Action: Increase the system memory space and close other running programs, or specify a larger value for the MEMORY_TARGET(DB version is above 7).

3004: Unable to open log file.
Cause: Cannot open the log file.
Action: Check the log file path and permissions.

3005: Insufficient space in buffer.
Cause: Insufficient buffer space.
Action: Increase the size of the buffer.

3006: Feature not yet implemented.
Cause: This feature is not yet implemented.
Action: Check whether a feature which is not yet implemented was used.

3007: Environment variable (database home and database sid) is not set.
Cause: An environment variable (database home and database sid) has not been defined.
Action: Define the variable.

3009: Unable to change log directory because the target directory is the same as the old destination.
Cause: The target directory is the same as the log directory currently being used.
Action: Specify a directory that is different from the current log directory.

3010: Unable to change log directory because of a failure in renaming log file.
Cause: Unable to rename the log file. Refer to the server error log for more detail.
Action: Examine the log file permissions and check the server error log. For more information, contact the technical support team.

3011: Unable to change log directory because of a failure in generating new log file.
Cause: The target directory has insufficient space.
Action: Examine the target directory space and initial parameters such as LOG_TOTAL_SIZE_LIMIT. Ensure the directory has sufficient space by deleting or moving unnecessary files. For more information, contact the technical support team.

3012: Unable to change log directory.
Cause: An error occurred while remapping a new log file. Check the error log at server.
Action: Examine the error log in the server. For more information, contact the technical support team.

3013: Unable to change log directory because filenames conflict.
Cause: There is already a log file with identical name in the target directory.
Action: Modify the filename or remove the log file in the target directory.

3014: Unable to create a directory for the new log file.
Cause: Unable to create a directory for the new log file due to invalid path or authority.
Action: Check whether a path and its authority of the new log file are valid. Also examine the error log of the server. For more information, contact the technical support team.

3015: Type of the JSON value is different from expected type.
Cause: Type of the JSON value is different from expected type.
Action: Examine the error log in the server. For more information, contact the technical support team.

3016: Expected JSON key not found.
Cause: Expected JSON key not found.
Action: Check the inventory of Horde.

3017: Too many objects referred (%1$d).
Cause: Too many objects referred (%1$d).
Action: Contact the technical support team.

3018: Out of memory (unable to allocate %1$d bytes of shared pool memory for %2$s).
Cause: Insufficient shared pool memory remaining.
Action: To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter.

3019: String buffer overflow detected.
Cause: An overflow occurred while generating a text string.
Action: Contact Technical Support.

---

Tibero Error Message 4000~4999

4001: Invalid DBA found.
Cause: Invalid DBA (Database Administrator) has been entered.
Action: Enter valid DBA.

4002: Invalid row number.
Cause: Invalid row number was entered.
Action: Enter a valid row number.

4003: Invalid serialized long locator discovered.
Cause: Invalid serialized long locator was entered.
Action: Enter a valid serialized long locator.

4004: Duplicate unique key found during index fast build.
Cause: A duplicate key exists in the table; the index cannot be made.
Action: Delete the duplicate key or make a non-unique index.

4005: Referential constraint violation: foreign key exists.
Cause: A foreign key exists with the same value; the primary key cannot be deleted.
Action: Delete the foreign key and then delete the primary key.

4006: Referential constraint violation: primary key not found.
Cause: A foreign key cannot be inserted; the primary key does not exist.
Action: Enter the primary key and then insert the foreign key.

4007: Unable to find LONG cursor.
Cause: In order to use the LONG function, an open cursor is necessary.
Action: Call the LONG function before closing the cursor.

4008: Duplicate unique key found during multi insert.
Cause: Cannot insert the entered key into the index, as the key is a duplicate.
Action: Check the duplicate key.

4009: LOB snapshot too old
Cause: The LOB value for CR was overwritten by another tx.
Action: Check the cause of the failure and try again.

4010: LOB information requested by a client is invalid.
Cause: LOB directory information is no longer valid.
Action: Because the directory of the table in which LOB exists is changed, the LOB locator cannot be used for the access.

4011: Data being inserted into an index-organized table via mutli insert must be sorted.
Cause: The data being inserted into the index-organized table is not sorted.
Action: Sort data before using mutli insert to insert rows into an index-organized table.

4012: unsupported operation on multi-column compressed tables
Cause: unsupported update/delete operation on multi-column compressed tables
Action: uncompress tables before update/delete operation

4013: Level of the index has reached maximum depth allowed.
Cause: The index has deficient nodes and the shape of the index is skewed.
Action: Index reorganization is required.

4014: Directory object was not found.
Cause: Directory object could not be found.
Action: Check the directory name.

4015: File path is too long.
Cause: File path is too long.
Action: Check the directory name and the file name.

4016: Can’t open empty file.
Cause: The file to open is empty.
Action: Check the parameter.

4017: Can’t open the specified binary file.
Cause: Can’t open the specified binary file.
Action: Check the parameter.

4018: Can’t get the length of the specified binary file.
Cause: Can’t get the length of the specified binary file.
Action: Check the parameter.

4019: Failed to lseek because of the invaild offset
Cause: Failed to lseek because of the invaild offset
Action: Check the parameter.

4020: Failed to read the specified binary file.
Cause: Failed to read the specified binary file.
Action: Check the parameter.

4021: Failed to open the binary file
Cause: The specified binary file is not openend.
Action: Check the parameter.

4022: Specified binary file does not exist.
Cause: Specified binary file does not exist.
Action: Check the parameter.

4027: Acess to the directory object was denied.
Cause: Acess to the directory object was denied.
Action: Check the directory object and modify the permission.

4028: Stored data in long type column is too long
Cause:
Action:

4029: Shared pool memory space for a sort segment extent list cannot be allocated.
Cause: Insufficient shared pool memory remaining.
Action: To increase the shared memory space, specify a larger value for the TOTAL_SHM_SIZE parameter.

---

Tibero Error Message 5000~5999

5001: Datetime/interval precision is out of range.
Cause: The values of DATETIME and INTERVAL do not match with the specified precision.
Action: Correct the specified precision and try again.

5002: Invalid data type for this operation.
Cause: An invalid data type was entered for an operation or function.
Action: Check the entered data type.

5003: Invalid TIME value.
Cause: Invalid TIME value.
Action: Check each field of TIME.

5004: Invalid TIMESTAMP value.
Cause: Invalid TIMESTAMP value.
Action: Check each field of TIMESTAMP.

5005: Invalid DATE value.
Cause: Invalid DATE value.
Action: Check each field of DATE.

5006: Invalid DATETIME unit type.
Cause: Invalid unit type for the entered DATETIME type.
Action: Check the entered unit type.

5007: Invalid string length.
Cause: Invalid format string or input string length.
Action: Check if format string or input string is null or less than than 0.

5008: Invalid precision specified for fractions of a second.
Cause: The precision specified for fraction of a second in TIMESTAMP and TIME is invalid.
Action: Check whether the precision is between 0 and 9.

5009: Input string is too short for DATE format.
Cause: The input string to be converted into the specified format string is incomplete.
Action: Lengthen the input string to match the given format string.

5010: Format ends before the entire input string is converted.
Cause: Additional unconverted data exists in the input string after conversion.
Action: Check the definition of the DATETIME format code and correct the input string.

5011: Invalid DATE format.
Cause: Invalid format code for DATE type is entered.
Action: Verify the DATE format code used is valid.

5012: Invalid TIME format.
Cause: Invalid format code for TIME/TIMESTAMP type is entered.
Action: Verify the TIME/TIMESTAMP format code used is valid.

5013: Specified format code cannot be used as input format.
Cause: The given format code cannot be used as input format.
Action: Delete the invalid format code from format string.

5014: Specified format code is invalid.
Cause: Unable to verify the specified format code.
Action: Delete the invalid format code from format string.

5015: Duplicated YEAR format exists.
Cause: A YEAR format code has already been provided.
Action: Delete the duplicate YEAR format code.

5016: Duplicated MONTH format exists.
Cause: A MONTH format code has already been provided.
Action: Delete the duplicate MONTH format code.

5017: Duplicated DAY format exists.
Cause: A DAY format code has already been provided.
Action: Delete the duplicate DAY format code.

5018: Duplicated HOUR format exists.
Cause: An HOUR format code has already been provided.
Action: Delete the duplicate HOUR format code.

5019: Duplicated MINUTE format exists.
Cause: A MINUTE format code has already been provided.
Action: Delete the duplicate MINUTE format code.

5020: Duplicated SECOND format exists.
Cause: A SECOND format code has already been provided.
Action: Delete the duplicate SECOND format code.

5021: Duplicated fractions of a second format exists.
Cause: Fractions of a second format code has already been provided.
Action: Delete the duplicate fractions of a second format code.

5022: Duplicated AD/BC format exists.
Cause: An AD/BC format code has already been provided.
Action: Delete the duplicate AD/BC format code.

5023: Duplicated AM/PM format exists.
Cause: An AM/PM format code has already been provided.
Action: Delete the duplicate AM/PM format code.

5024: Month conflicts with Julian date.
Cause: DDD format code and month-related format code cannot be used together.
Action: Delete the month-related format code to use the DDD format code.

5025: Day of the month conflicts with Julian date.
Cause: DDD format code and date-related format code cannot be used together.
Action: Delete the date-related format code to use the DDD format code.

5026: Hour of the day conflicts with seconds in the day.
Cause: SSSSS format code and hour-related format code cannot be used together.
Action: Delete the hour-related format code to use the SSSSS format code.

5027: Minutes of the hour conflicts with seconds in the day.
Cause: SSSSS format code and minute-related format code cannot be used together.
Action: Delete the minute-related format code to use the SSSSS format code.

5028: Seconds of the minute conflicts with seconds in the day.
Cause: SSSSS format code and second-related format code cannot be used together.
Action: Delete the second-related format code to use the SSSSS format code.

5029: Invalid year value: must be a non-zero integer between -4713 and +9999.
Cause: Invalid value specified for the year.
Action: Input a non-zero integer value between -4713 and +9999.

5030: Invalid month value.
Cause: Invalid value specified for the month.
Action: Input an integer value between 1 and 12.

5031: Invalid month name.
Cause: Invalid value specified for the month name.
Action: Input a valid month name.

5032: Invalid day value.
Cause: Invalid value specified for the day name.
Action: Input a valid day name.

5033: Invalid hour value.
Cause: Invalid value specified for the hour.
Action: Input an integer value between 0 and 23.

5034: Invalid minute value.
Cause: Invalid value specified for the minutes.
Action: Input an integer value between 0 and 59.

5035: Invalid second value.
Cause: Invalid value specified for the seconds.
Action: Input an integer value between 0 and 60.

5036: Invalid fractions of a second value.
Cause: Invalid value specified for the fractions of a second.
Action: Input an integer value between 0 and 999999999.

5037: Invalid AD/BC value.
Cause: Invalid value specified for AD/BC.
Action: Input a valid value for AD/BC.

5038: Invalid AM/PM value.
Cause: Invalid value specified for AM/PM.
Action: Input a valid value for AM/PM.

5039: Signed year cannot be used with AD/BC.
Cause: The signed year format cannot be used with the AD/BC format.
Action: Delete one of the two formats to make a valid format string.

5040: HH24 cannot be used with AM/PM.
Cause: The HH24 format cannot be used with the AM/PM format simultaneously.
Action: Delete one of the two formats to make a valid format string.

5041: Invalid precision specified for fractions of a second.
Cause: The precision for fractions of a second in TIMESTAMP and TIME is invalid in the format string.
Action: Verify the precision is between 0 and 9.

5042: Invalid decimal input.
Cause: Invalid value specified for decimal.
Action: Input a valid decimal number (‘.’).

5043: Invalid seconds of the day input.
Cause: Invalid value was entered in SSSSS format.
Action: Input an integer value between 0 and 86400.

5044: Insufficient space in string buffer for DATETIME type.
Cause: The buffer is not large enough to convert the DATETIME type to a string.
Action: Increase the buffer size.

5045: Only TIME format can be omitted.
Cause: All format codes except hour/minute/second/fraction of a second are omitted from the input string.
Action: Input valid values for the format codes or delete the formats.

5046: Day of the year must be between 1 and 365 (366 for leap year).
Cause: Invalid value specified for a day of the year
Action: Input an integer value between 1 and 366.

5047: Invalid day name.
Cause: Invalid value specified for a day of the week
Action: Input a valid value for a day of the week.

5048: Too many truncation format specifiers.
Cause: More than one truncate format code is set.
Action: Input only one format code.

5049: Too many round-up format specifiers.
Cause: More than one round-up format code is set.
Action: Input only one format code.

5050: Invalid use of the escape character.
Cause: Invalid use of the escape character.
Action: Check the search pattern string of LIKE function.

5051: Invalid hexadecimal number.
Cause: The given character is not a valid hexadecimal number.
Action: Check the character to be converted to hexadecimal number.

5052: Invalid string sequence.
Cause: The character is not included in the given character set.
Action: Check the input string and character set.

5053: Invalid Unicode.
Cause: Invalid Unicode.
Action: Check the input string.

5054: Not implemented.
Cause: Unsupported format string.
Action: Check the input format string.

5055: Invalid type of UNIT used for INTERVAL.
Cause: Invalid UNIT type for the INTERVAL type that was entered.
Action: Check the UNIT type.

5056: Invalid input string for INTERVAL.
Cause: An error occurred while converting the input string to INTERVAL type.
Action: Check the input string.

5057: Invalid input precision for interval.
Cause: Invalid leading precision value.
Action: Check the leading precision value.

5058: Invalid precision value for fractions of a second.
Cause: Invalid precision value for fractions of a second.
Action: Input a valid precision value for fractions of a second.

5059: Invalid INTERVAL format.
Cause: Unsupported interval format string.
Action: Check the input format string.

5060: Month value is out of range.
Cause: Value of months in YEAR-TO-MONTH INTERVAL type is out of range.
Action: Input a valid month value.

5061: Hour value is out of range.
Cause: Value of hour in DAY-TO-SECOND INTERVAL type is out of range.
Action: Input a valid hour value.

5062: Minutes value is out of range.
Cause: Value of minutes in DAY-TO-SECOND INTERVAL type is out of range.
Action: Input a valid minutes value.

5063: Seconds value is out of range.
Cause: Value of seconds in DAY-TO-SECOND INTERVAL type is out of range.
Action: Input a valid seconds value.

5064: INTERVAL exceeds given precision value.
Cause: The INTERVAL value does not match the given precision value.
Action: Correct the values and try again.

5065: Divide by zero error.
Cause: The INTERVAL type was divided by 0.
Action: Modify the expression to remove the error.

5066: Insufficient space in buffer for conversion.
Cause: The buffer is not large enough to convert the INTERVAL type into string.
Action: Increase the buffer size.

5067: Output was altered or truncated to fit into buffer, resulting in a possible loss of precision.
Cause: The buffer is not large enough to contain the results of the converted string.
Action: Increase the buffer size.

5068: Overflow error.
Cause: Overflow occurred as a result of an operation.
Action: Decrease the value of an operand.

5069: Underflow error.
Cause: Underflow occurred as a result of an operation.
Action: Increase the value of an operand.

5070: Divide by zero error.
Cause: The NUMBER type was divided by 0.
Action: Modify the expression to remove the error.

5071: NUMBER exceeds given precision.
Cause: The NUMBER value does not match the given precision value.
Action: Correct the values and try again.

5072: Failure converting NUMBER to or from a native type.
Cause: An error occurred while converting the NUMBER value.
Action: Check that the value is within the appropriate range.

5073: Invalid NUMBER provided for the operation.
Cause: An invalid NUMBER value was entered for the operation or function.
Action: Change the value and try again.

5074: Given string does not represent a number in proper format.
Cause: The given string does not represent a proper number.
Action: Check the type of string.

5075: Invalid format string.
Cause: Invalid format string.
Action: Correct the format string.

5076: NUMBER is not printable in this format. Numbers were filled in output buffer.
Cause: The NUMBER value does not match the given format.
Action: Modify the NUMBER value or format string.

5077: NUMBER precision is out of range.
Cause: The precision of the NUMBER type is out of range.
Action: Specify a precision value for the NUMBER type between 1 and 38.

5078: NUMBER scale is out of range.
Cause: The scale of the NUMBER type is out of range.
Action: Specify a scale value for the NUMBER type between -125 and +130.

5079: Data type length is out of range.
Cause: The length is out of range.
Action: Modify the length to the one that is defined for each type.

5080: Invalid ROWID.
Cause: Invalid ROWID
Action: Choose a valid ROWID.

5081: Invalid ROWID segment info.
Cause: Invalid ROWID segment information.
Action: Input valid segment information for the ROWID.

5082: Invalid ROWID file.
Cause: Invalid ROWID file information.
Action: Input valid file information for the ROWID.

5083: Invalid ROWID block.
Cause: Invalid ROWID block information.
Action: Input valid block information for the ROWID.

5084: Invalid ROWID row.
Cause: Invalid ROWID row information.
Action: Input valid row information for the ROWID.

5085: Invalid IP string.
Cause: Invalid IP string.
Action: Check the input IP string.

5086: String buffer is too small for string conversion or copy.
Cause: The string buffer is too small to handle the task.
Action: Check the size of the input string.

5087: The date value is out of range.
Cause: The date value of the YEAR-TO-MONTH INTERVAL type is out of range.
Action: Input a valid date value.

5088: Numeric digits are not matched.
Cause: The number of digits of a given number and the length of the datetime format are not matched.
Action: Use the same number of digits as the length of the datetime format.

5089: Punctuation characters are not matched.
Cause: The character of a given punctuation mark does not match the character of the datetime format.
Action: Use the same character as that of the datetime format.

5090: Not a numeric value.
Cause: Cannot use a character for numeric data.
Action: Use numeric data.

5091: Invalid timezone format.
Cause: Invalid timezone format is used for the TIMESTAMP type.
Action: Verify that you have entered a valid timezone format.

5092: Duplicate TZH format.
Cause: The TZH format code already exists.
Action: Delete the duplicated timezone (hour) format code.

5093: Duplicate TZM format.
Cause: The TZM format code already exists.
Action: Delete the duplicated timezone (minute) format code.

5094: Duplicate TZR format.
Cause: The TZR format code already exists.
Action: Delete the duplicated timezone (region) format code.

5095: Duplicate TZD format.
Cause: The TZD format code already exists.
Action: Delete the duplicated timezone (abbreviation) format code.

5096: TZR/TZD format conflicts with TZH/TZM format.
Cause: timezone region format cannot be used with timezone time format.
Action: Delete the region format.

5097: TZH/TZM format conflicts with TZR/TZD format.
Cause: timezone time format cannot be used with timezone region format.
Action: Delete the time format.

5098: Invalid hour value of UTC offset.
Cause: The hour value of UTC offset must be between -12 and 14.
Action: Verify that you have entered a valid hour value of UTC offset.

5099: Invalid minute value of UTC offset.
Cause: The minute value of UTC offset must be between 0 and 59.
Action: Verify that you have entered a valid minute value of UTC offset.

5100: Invalid second value of UTC offset.
Cause: The second value of UTC offset must be between 0 and 59.
Action: Verify that you have entered a valid second value of UTC offset.

5101: Invalid hour value of daylight saving time.
Cause: The hour value of daylight saving time must be between 0 and 24.
Action: Verify that you have entered a valid hour value of daylight saving time.

5102: Invalid minute value of daylight saving time.
Cause: The minute value of daylight saving time must be between 0 and 59.
Action: Verify that you have entered a valid minute value of daylight saving time.

5103: Invalid timezone offset.
Cause: The timezone offset value must be in the format of ‘[+ -]hh:mm’.
Action: Verify that you have entered a valid timezone offset.

5104: Invalid timezone region value.
Cause: The timezone region value is invalid or unsupported.
Action: Verify that you have entered a valid timezone region value.

5105: Invalid timezone index ‘%1$d’.
Cause: The timezone index value is not supported.
Action: Contact the technical support team.

5106: Invalid timezone hour value.
Cause: The timezone hour value is invalid.
Action: Verify that you have entered a valid timezone hour value.

5107: Invalid timezone minute value.
Cause: The timezone minute value is invalid.
Action: Verify that you have entered a valid timezone minute value.

5108: Invalid timezone region value.
Cause: The timezone region value is invalid.
Action: Verify that you have entered a valid timezone region value.

5109: Invalid timezone abbreviation value.
Cause: The timezone abbreviation value is invalid.
Action: Verify that you have entered a valid timezone abbreviation value.

5110: Invalid date/time period according to the daylight saving time rule.
Cause: The date/time period is invalid according to the daylight saving time rule.
Action: Check the daylight saving time rule.

5111: NUMBER exceeds given precision. (n:%1$s, p:%2$d, s:%3$d)
Cause: The NUMBER value does not match the given precision value.
Action: Correct the values and try again.

5112: Duplicated ‘%1$s’ format exists.
Cause: A format code has already been provided.
Action: Delete the duplicated format code.

5113: Invalid %1$s value ‘%2$s’. (%3$s)
Cause: Invalid value specified for the %1$s.
Action: Input a valid value for %1$s.

5114: Invalid %1$s value ‘%2$d’: must be an integer between %3$d and %4$d.
Cause: Invalid value specified for the %1$s.
Action: Input a valid value for %1$s.

5115: Cannot find the timezone file.
Cause: The timezone file does not exist, or you don’t have permission to read the file.
Action: Check the timezone file.

5116: NULL object instance access violation.
Cause: An attempt was made to access the attributes of an object instance whose value is null.
Action: Check that the value of the object instance is not null.

5117: Invalid user-defined type.
Cause: The specified user-defined type does not exist or has been altered.
Action: Check if the user-defined type has been altered on the server.

5118: FLOAT precision is out of range.
Cause: The precision of the FLOAT type is out of range.
Action: Specify a precision value for the FLOAT type between 1 and 120.

5119: Invalid number type.
Cause: Invalid number type.
Action: Check the type.