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

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.