‘Ctrl+F’로 에러 메시지 번호를 검색하시면 문제 발생 원인과 해결 방법을 빠르게 확인하실 수 있습니다.
Tibero Error Message 160000~160999
160001: The data file does not exist.
Cause: The data file to be used in the Export/Import utility functions does not exist.
Action: Verify the data file exists or the data file was specified correctly.
160002: The message file does not exist.
Cause: The message file to be used in the Export/Import utility functions does not exist.
Action: Verify the message file exists or the message file was specified correctly.
160003: The bad file does not exist.
Cause: The error file to be used in the Export/Import utility functions does not exist.
Action: Verify the error file exists or the error file was specified correctly.
160004: Meta information does not exist.
Cause: The meta information to be used in the Export/Import utility functions does not exist.
Action: Verify the meta information was set correctly in the API structure.
160005: The specified argument is NULL.
Cause: Null is used in the parameter of the Export/Import utility functions.
Action: Verify the parameter value used in API calls is NULL.
160006: The action string does not exist.
Cause: The command to be used in the Export/Import utility functions does not exist.
Action: Verify the command was set correctly in the API structure.
Tibero Error Message 190000~190999
190001: protocol failure (type=%1$d)
Cause: The communications protocol does not match client layer
Action: Verify the protocol is valid.
190002: socket read failure (errno=%1$d)
Cause: No response has arrived from client(listen thread)
Action: Verify the client(listen thread) is running
Tibero Error Message 400000~400999
400001: Java class loading has failed. (%1$s), for more details, refer to the stdout error file.
Cause: The jar files used in HBASE must be set in the environment variable.
Action: Modify the CLASSPATH.
400002: jni error (%1$s)
Cause: jni error
Action: jni error
400003: A table connection error (%1$s) has occurred in HBASE. For more details about the table connection error, check the stdout error file.
Cause: The table name and column family must exist in HBASE.
Action: Modify the definition of the HBASE table, and the column family of the query.
400004: The (%1$s) column is not assigned to a column family.
Cause: A column must be assigned to a column family in order to perform a query on an HBASE TABLE.
Action: Add the column, which is used in the query, to a column family. (columnfamily$column)
400005: The target column is not defined.
Cause: A target column must be specified when data is inserted into an HBASE TABLE.
Action: Specify the target column to insert the data. (columnfamily$column)
400006: A ROWKEY column is required.
Cause: A ROWKEY column must be specified when inserting data into an HBASE TABLE.
Action: Add a ROWKEY column.
Tibero Error Message 410000~410999
410001: The specified storage server name, ‘%1$s’, is not identical to the storage server name, ‘%2$s’, that was set in a tip file.
Cause: An invalid storage server name was used in a statement for creating a storage server.
Action: Set the storage server name identically to the name set in the SSVR_NAME of a tip file, or omit the name.
410002: This DDL statement is not permitted in storage server mode.
Cause: In the storage server mode, this DDL cannot be executed.
Action: This DDL cannot be executed.
410003: The disk name, ‘%1$s’, is invalid.
Cause: The name is duplicated or a disk with the specified name could not be found.
Action: Check the disk name.
410004: The disk path, ‘%1$s’, is invalid.
Cause: The path is invalid or a disk at the specified path could not be found.
Action: Check the disk path.
410005: Failed to create file.
Cause: Check the tracelog to view the causes of failure.
Action: Retry after resolving errors.
410006: Invalid fetch information.
Cause: Incorrect fetch information was fetched in DB.
Action: Retry after resolving error.
410007: Specified tip SSVR_WTHR_CNT value is too small.
Cause: SSVR_WTHR_CNT is smaller than sdisk count.
Action: Retry after increasing the SSVR_WTHR_CNT value.
410008: Invalid gdisk ID.
Cause: Invalid gdisk ID was used to request DB read/write.
Action: Retry after resolving error.
410009: Invalid gdisk ID.
Cause: Invalid gdisk ID was used to request DB read/write.
Action: Retry after resolving error.
410010: Insufficient permissions on the disk, ‘%1$s’.
Cause: Read/write permissions are required for the disk.
Action: Grant read/write permissions on the disk.
410011: Failed to create the disk.
Cause: Check the available disk space.
Action: Retry the operation after setting the disk size to a value within the available disk space.
410012: Failed to drop the storage disk.
Cause: There is a grid disk that is included in the storage disk.
Action: Retry the operation after dropping all grid disks that are included in the storage disk.
410013: Invalid gdisk arguments.
Cause: Specified gdisk information is invalid.
Action: Check whether the range overlaps with a previously created gdisk or whether the information fits 32k alightment.
410014: get IP by hostname failed.
Cause: Failed to get IP from hostname.
Action: Check whether _RDS_NW_IP is valid.
410015: send msg failed.
Cause: Failed to send message.
Action: Check the network status and log.
410016: send msg failed.
Cause: Failed to receive message.
Action: Check the network status and log.
410017: sync sfc failed.
Cause: Flashcache was not synchronized for the modified block.
Action: Check whether synchronization was performed in another session.
410018: create sfc failed.
Cause: Failed to create SFC.
Action: Check whether a duplicate SFC was created or whether SFC was created in MOUNT mode.
410019: drop sfc failed.
Cause: Failed to delete SFC.
Action: Check whether the SFC to be deleted exists or whether SFC was deleted in MOUNT mode.
410020: Insufficient permissions on the flash, ‘%1$s’.
Cause: Read/write permissions are required for the flash.
Action: Grant read/write permissions on the flash.
410021: The flash path, ‘%1$s’, is invalid.
Cause: The path is invalid or a flash at the specified path could not be found.
Action: Check the flash path.
410022: The share value is less than 1 or greater than %1$d.
Cause: The share value is invalid.
Action: Modify the share value.
410023: The level value is less than 1 or greater than %1$d.
Cause: The level value is invalid.
Action: Specify the level to a value between 1 and 8.
410024: The allocation value is less than 1 or greater than 100.
Cause: The allocation value is invalid.
Action: Modify the allocation value.
410025: The sum of the share values exceeds %1$d.
Cause: The sum of the share values is too large.
Action: Decrease the total share value.
410026: The allocation sum of level %1$d exceeds 100.
Cause: The allocation sum exceeds 100.
Action: Modify the allocation value.
410027: The number of directives of the DB plan that uses share exceeds %1$d.
Cause: The number of directives of the DB plan that uses share is too high.
Action: Decrease the number of directives of the DB plan that uses share.
410028: The number of directives of the DB plan that uses level exceeds %1$d.
Cause: The number of directives of the DB plan that uses level is too high.
Action: Decrease the number of directives of the DB plan that uses level.
410029: The number of directives of the category plan exceeds %1$d.
Cause: The number of directives of the category plan is too high.
Action: Decrease the number of directives of the category plan.
410030: The directive name ‘%1$s’ is a duplicate.
Cause: The directive name is a duplicate.
Action: Change the directive name.
410031: The OTHER directive is missing.
Cause: The OTHER directive is missing.
Action: Specify the OTHER directive.
410032: The flash log size, %1$d GB, is invalid.
Cause: The size of flash log is invalid.
Action: Change the directive flash log size.
410033: Specified flash device size, %1$d GB, is too small.
Cause: Specified flash device size is too small.
Action: Increase the directive flash device size.
410034: The specified disk path, ‘%1$s’, is already in use by another disk.
Cause: The specified disk path is already in use by another disk.
Action: Check the disk path.
410035: Not enough memory to load the Flashcache.
Cause: Check the storage server’s shared memory size.
Action: Retry the operation after increasing the shared memory size.
410036: Invalid Flashcache name length. (Name: %1$s, Max name length: %2$uBytes)
Cause: Failed to load because the name length of is too long.
Action: Retry the operation after setting the Flashcache name length to less than max name length.
410037: Invalid Flashcache path length. (Name: %1$s, Max path length: %2$uBytes)
Cause: Failed to load because the path length of is too long.
Action: Retry the operation after setting the Flashcache path length to less than max path length.
410038: Unable to find the Flashcache ‘%1$s’.
Cause: Check that the Flashcache path and permissions are set correctly.
Action: Retry the operation after setting the Flashcache path and permissions to valid values.
410039: Invalid Flashcache header.
Cause: Invalid Flashcache header format. The Flashcache has not been formatted.
Action: Retry the operation after checking that the Flashcache is not corrupt or has not been forcibly replaced.
410040: Invalid Flashcache version. (Version: %1$s(Previous), %2$s(Current))
Cause: Failed to load because the Flashcache header version and current version are not compatible.
Action: Switch to the previous version and drop the Flashcache, and then switch back to the current version and recreate the Flashcache.
410041: Invalid Flashcache journal size. (Journal size: %1$uBytes(Required) %2$uBytes(Parameter))
Cause: Failed to format the Flashcache because its journal size is less than the required minimum size.
Action: Retry the operation after setting the Flashcache journal size to at least the minimum size required.
410042: Invalid Flashcache meta block size. (Meta blocksize: %1$uBytes(Header), %2$uBytes(Parameter))
Cause: The meta block size specified in the parameter and the Flashcache header are different.
Action: Retry the operation after setting the meta block size parameter to the meta block size set in the Flashcache header.
410043: Invalid Flashcache bin block size. (Bin blocksize: %1$uBytes(Header), %2$uBytes(Parameter))
Cause: The bin block size specified in the parameter and the Flashcache header are different.
Action: Retry the operation after setting the bin block size parameter to the bin block size set in the Flashcache header.
410044: Invalid Flashcache bin size (Bin size: %1$uBytes(Header), %2$uBytes(Parameter)).
Cause: The bin size specified in the parameter and the Flashcache header are different.
Action: Retry the operation after setting the bin size parameter to the bin size set in the Flashcache header.
410045: Function offloading is not supported.
Cause: Unable to find a storage server to execute function offloading to.
Action: Function offloading is only supported in storage server mode.
410046: SDM is null.
Cause: SDM is null.
Action: A dump cannot be performed when SDM is null.
410047: The disk id, ‘%1$d’, is invalid.
Cause: The id is duplicated or a disk with the specified id could not be found.
Action: Check the disk id.
410048: The specified disk id, ‘%1$d’, is already in use by another disk.
Cause: The specified disk id is already in use by another disk.
Action: Check the disk id.
410049: Unable to process nondata block: file# %1$u, block# %2$u.
Cause: Unable to process nondata block.
Action: Check the invalid block.
410050: Unable to process inconsistent block: file# %1$u, block# %2$u.
Cause: Unable to process inconsistent block.
Action: Check the invalid block.
410051: Fail to concat in processing cu block: file# %1$u, block# %2$u.
Cause: Fail to concat in processing cu block.
Action: Check the invalid block.
410052: Failed to create a connection resource between the database server and storage server.
Cause: Failed to create a connection resource between the database server and storage server.
Action: Check memory usage and log(connection resource creation fail log).
410053: Failed to establish a connection with the database server due to an error on the storage server.
Cause: Failed to establish a connection with the database server due to an error on the storage server.
Action: Check whether the TCP/IB network is operating normally.
410054: An internal error occured in the executor layer on the storage server.
Cause: An internal error occured in the executor layer on the storage server.
Action: Check the pp dump for further details.
Tibero Error Message 528000~528999
528005: Logical error in optimizer.
Cause: Logical error in optimizer.
Action: Contact the technical support team.
