Cause

It is the cause of an error.

Action

It is the action.

Cause

Insufficient privilege to access the file or directory.

Action

Use the chown or chmod command to change the access privileges.

Cause

This error corresponds to EOF and is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

File locking has failed.

Action

Check for other processes using the file and try again after a short wait.

Cause

Failed to unlock the file.

Action

Check the file lock status and unlock the file with appropriate privileges.

Cause

The file descriptor is invalid or an I/O error has occurred.

Action

Verify that the file has been opened correctly and check the condition of the disk.

Cause

The file system synchronization failed, or a disk I/O error has occurred.

Action

Verify the disk status and perform a file system integrity check.

Cause

The file does not exist, or the privilege to retrieve its status has not been granted.

Action

Verify the file path and privileges.

Cause

Failed to create a pipe due to insufficient system resources.

Action

Check system resource usage and terminate unnecessary processes.

Cause

Failed to wait for the child process because no child process exists.

Action

Check the process relationships and inspect the signal handling status.

Cause

System resources are insufficient.

Action

Check system resource usage and terminate unnecessary processes.

Cause

The attempt to send a signal failed because the target process does not exist.

Action

Verify that the target process exists and check signal privileges.

Cause

Failed to set signal handler.

Action

Check whether the system supports signals.

Cause

Failed to block the signal.

Action

Check the signal mask settings and verify that the system supports the signal.

Cause

Failed to set thread attributes.

Action

Check the thread attribute values and verify the system's thread limits.

Cause

Failed to wait for thread termination due to an invalid thread ID.

Action

Check the thread status and verify whether a deadlock has occurred.

Cause

Failed to set the Thread Once Code.

Action

Review the thread synchronization code.

Cause

The given name is too long.

Action

Shorten the name length to comply with system limitations.

Cause

Failed to connect to shared memory due to an invalid segment ID.

Action

Verify the shared memory segment ID and check the process privileges.

Cause

Failed to destroy shared memory due to insufficient privileges.

Action

Check the ownership privileges of the shared memory.

Cause

Failed to create semaphore due to insufficient system resources.

Action

Check the system limits for semaphores and clean up IPC resources.

Cause

A deadlock occurred due to failure in acquiring a semaphore.

Action

Verify the semaphore usage patterns and implement logic to prevent deadlocks.

Cause

The semaphore has already been released, so the semaphore release failed.

Action

Check the semaphore status to prevent duplicate releases.

Cause

Failed to destroy the semaphore due to insufficient privileges.

Action

Check the ownership privileges of the semaphore.

Cause

The resource is currently in use.

Action

Wait until the resource is no longer in use, then retry.

Cause

The operation has timed out.

Action

Adjust the timeout value and check the system performance.

Cause

The requested object does not exist.

Action

Check the object name and path.

Cause

The two objects do not match.

Action

Verify if the objects being compared match.

Cause

The disk space is insufficient.

Action

Delete unnecessary files to free up disk space, or consider expanding the storage.

Cause

An unsupported feature was used.

Action

Use an alternative feature or upgrade the system.

Cause

The given buffer does not have enough space.

Action

Check the data size and increase the buffer capacity.

Cause

The network address is invalid.

Action

Check the network address format and use a valid IP address.

Cause

The recvfrom() system call failed.

Action

Check the network connection status and inspect the socket state.

Cause

Failed to retrieve the socket address using getsockname().

Action

Check the socket binding status.

Cause

Failed to retrieve the peer address using getpeername().

Action

Check the socket connection status.

Cause

Failed to manipulate the file descriptor using fcntl().

Action

Check the validity of the file descriptor and the requested operation.

Cause

Failed to set socket options using setsockopt().

Action

Check the socket option values and the socket status.

Cause

The feature is not implemented.

Action

Use a supported alternative feature.

Cause

Failed to manipulate device parameters using ioctl().

Action

Check the device status and the requested parameters.

Cause

Failed to retrieve the host name.

Action

Check the network settings and verify the host name configured on the system.

Cause

Failed to close the socket.

Action

Check the socket status and then properly terminate the network connection.

Cause

Failed to shutdown the socket.

Action

Check the socket connection status.

Cause

Socket creation failed due to insufficient system resources.

Action

Check the system socket limit and verify the network settings.

Cause

Failed to retrieve the attributes of the file descriptor.

Action

Check the validity of the file descriptor.

Cause

Failed to set file descriptor attributes.

Action

Check the validity of the file descriptor and its configuration values.

Cause

Failed to listen on the socket due to an error in the backlog queue configuration.

Action

Check the socket status and network configuration.

Cause

Failed to accept the connection due to a network error.

Action

Check the network connection status and review the firewall settings.

Cause

The system call was interrupted due to a signal.

Action

Check the signal handling logic and retry the system call.

Cause

Failed to retrieve the socket options.

Action

Check the socket status and the validity of the options.

Cause

Failed to connect to the host because the target server is unreachable.

Action

Check the status of the target server and network, and review the firewall settings.

Cause

This is an error code used within the server.

Action

Check the system logs and contact our customer service department.

Cause

The sendmsg() system call failed.

Action

Check the message structure and the socket status.

Cause

The recvmsg() system call failed.

Action

Check the message buffer and the socket status.

Cause

The socketpair() system call failed.

Action

Check the system socket resource.

Cause

The converted value is out of range. (overflow/underflow)

Action

Check the range of the input value and use an appropriate data type.

Cause

The given string is not a valid number.

Action

Check the format of the input string and convert it to a numeric format.

Cause

An invalid file descriptor was used.

Action

Check whether the file was opened properly and reassign the file descriptor.

Cause

The resource is temporarily unavailable.

Action

Try again after a short while.

Cause

The address is already in use.

Action

Either use a different port or terminate the existing process before trying again.

Cause

Failed to initialize the communication context.

Action

Check the network configuration and system resources.

Cause

Failed to finalize the communication context

Action

Check the context status and clean up the resources.

Cause

Failed to connect to the communication context.

Action

Check the network connection and the status of the target server.

Cause

Failed to poll the communication context.

Action

Check the network connection and the status of the context.

Cause

Failed to write a packet using the communication context.

Action

Check the network connection status and the packet size.

Cause

Failed to read a packet using the communication context.

Action

Check the network connection status and the buffer size.

Cause

Failed to transmit the descriptor using the communication context.

Action

Check the status of the context and the data to be transmitted.

Cause

Failed to receive the descriptor using the communication context.

Action

Check the status of the context and the receive buffer.

Cause

Failed to retrieve the current file path.

Action

Check the file privilege and the validity of the path.

Cause

Failed to open the library.

Action

Check whether the library file exists and verify the path.

Cause

Failed to close the library.

Action

Check the status of the library.

Cause

Failed to retrieve the symbol address.

Action

Check the symbol name and the status of the library.

Cause

The query is not supported.

Action

Use a supported query syntax.

Cause

Failed to check the existence of the file.

Action

Verify the file path and check the file system privileges.

Cause

The input value is too long.

Action

Shorten the input value to meet the allowed length limit.

Cause

A system call error occurred.

Action

Check the system logs and inspect the system status.

Cause

Attempted to divide by zero.

Action

Check whether the denominator in the division operation is zero.

Cause

Failed to open the semaphore.

Action

Verify the semaphore name and privileges.

Cause

Failed to close the semaphore.

Action

Check the semaphore status.

Cause

Failed to unlink the semaphore.

Action

Check the semaphore status and privileges.

Cause

Access permission to the file was denied.

Action

Check the file access privileges and verify the user's privileges.

Cause

Unsupported operating system.

Action

Run on a supported operating system.

Cause

Environment variable is not defined.

Action

Set the required environment variable.

Cause

License file does not exist.

Action

Check the license file path and install the license file.

Cause

License validity period has not started yet.

Action

Check the system time and install the correct license file.

Cause

The license has expired.

Action

Renew the license and install the new license file.

Cause

License core count does not match system core count.

Action

Acquire a license appropriate for the system's core count.

Cause

The license key is corrupted or invalid.

Action

Reinstall a valid license file.

Cause

Licensed hostname does not match system hostname.

Action

Verify the hostname and acquire an appropriate license for it.

Cause

Unable to configure thread affinity.

Action

Check the system CPU configuration and thread privileges.

Cause

Failed to create timer.

Action

Check the system timer resources.

Cause

Failed to set timer.

Action

Check the timer value and system status.

Cause

Failed to delete timer.

Action

Check the timer status.

Cause

Address not provided.

Action

Provide the required address information.

Cause

Failed to access the message queue.

Action

Verify the message queue privileges and its existence.

Cause

Message queue already exists.

Action

Use the existing message queue or specify a different name.

Cause

Failed to create message queue.

Action

Check the system IPC resource limits.

Cause

Message queue has been removed.

Action

Recreate the message queue or use a different one.

Cause

Failed to delete the message queue.

Action

Check the message queue privileges and the queue status.

Cause

Failed to send the message.

Action

Check the message size and the queue status.

Cause

Failed to receive the message.

Action

Check the message queue status and buffer size.

Cause

No available messages in the message queue.

Action

Try again later or use blocking mode.

Cause

Failed to retrieve file status attributes.

Action

Check the validity of the file descriptor.

Cause

Failed to set file status attributes.

Action

Check the file descriptor and the configuration values.

Cause

InfiniBand verbs interface error.

Action

Check the status of the InfiniBand hardware and drivers.

Cause

InfiniBand device not found.

Action

Check the installation and recognition status of the InfiniBand hardware.

Cause

Specified InfiniBand device not found.

Action

Check the device name and configuration.

Cause

Suitable memory region not found for the specified pointer and size.

Action

Verify that the memory region is properly registered and configured.

Cause

Failed to retrieve semaphore value.

Action

Check the status of the semaphore.

Cause

Failed to control the pollset.

Action

Check the pollset status and control commands.

Cause

Failed to create the pollset.

Action

Check the system resources and pollset configuration.

Cause

The system has reached the limit of file descriptors.

Action

Increase the system’s file descriptor limit.

Cause

The INI file format is invalid.

Action

Check the INI file syntax and correct the file format.

Cause

The path does not exist.

Action

Verify if the path exists and create the directory if necessary.

Cause

Failed to retrieve the maximum number of undo semaphores per array.

Action

Check the system semaphore settings.

Cause

Failed to create undo semaphore.

Action

Check the system semaphore resources.

Cause

Failed to bind the undo semaphore.

Action

Check the semaphore status and privileges.

Cause

Failed to unbind the undo semaphore.

Action

Check the binding status of the semaphore.

Cause

Failed to retrieve the status of the undo semaphore.

Action

Check the validity of the semaphore.

Cause

Failed to delete the undo semaphore.

Action

Check the semaphore status and privileges.

Cause

Failed to suspend asynchronous I/O.

Action

Check the status of the asynchronous I/O.

Cause

Failed to control the shared memory segment.

Action

Check the shared memory privileges and status.

Cause

Failed to detach the thread because it is already detached.

Action

Check the status of the thread.

Cause

Communication link failure occurred.

Action

Check the network connection status and communication infrastructure.

Cause

The specified process does not exist.

Action

Check the existence of the process and verify the process ID.

Cause

Failed to execute the getaddrinfo() system call.

Action

Check the hostname and DNS configuration.

Cause

The address is unavailable.

Action

Check the network interface and address configuration.

Cause

The semaphore set already exists.

Action

Use the existing semaphore or choose a different key.

Cause

Failed to create the semaphore set.

Action

Check the system semaphore limits.

Cause

Failed to return the semaphore set.

Action

Check the semaphore key and privileges.

Cause

Failed to set the semaphore value.

Action

Check the semaphore index and value.

Cause

Failed to perform semaphore operation.

Action

Check the semaphore operation command and status.

Cause

Failed to remove the semaphore set.

Action

Check the semaphore privileges and status.

Cause

Failed to create the directory.

Action

Check privilege settings and ensure sufficient disk space.

Cause

Failed to remove the directory.

Action

Check privilege settings and ensure the directory is empty.

Cause

Failed to open the directory and read its contents.

Action

Check privilege settings and ensure that the directory exists.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The bytes bigger than the column length were input.

gSQL> CREATE TABLE t1 ( c1 VARCHAR(3) );

gSQL> INSERT INTO t1 VALUES ( 'abcd' );

ERR-22001(12002): byte length of data greater than column length :

INSERT INTO t1 VALUES ( 'abcd' )

*

ERROR at line 1:

Input the data which matches the column length as follows.

gSQL> INSERT INTO t1 VALUES ( 'abc' );

1 row created.

The characters whose length is longer than the character length of the column was input.

gSQL> CREATE TABLE t1 ( c1 VARCHAR(2 char) );

gSQL> INSERT INTO t1 VALUES ( '두글자' );

ERR-22001(12003): character length of data greater than column length :

INSERT INTO t1 VALUES ( '두글자' )

*

ERROR at line 1:

Check the number of characters allowed for the column.

gSQL> INSERT INTO t1 VALUES ( '두자' );

1 row created.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

It is the conversion causing data loss.

gSQL> SELECT TO_NATIVE_BIGINT( '9223372036854775808' ) AS RESULT FROM DUAL;

ERR-22001(12005): conversion of data would result in loss of whole digits :

SELECT TO_NATIVE_BIGINT( '9223372036854775808' ) AS RESULT FROM DUAL

*

ERROR at line 1:

Use an input which does not cause data loss.

gSQL> SELECT TO_NATIVE_BIGINT( '9223372036854775807' ) AS RESULT FROM DUAL;

RESULT

-------------------

9223372036854775807

1 row selected.

The characters which can not be converted to the number were used.

gSQL> SELECT 1 + 'a' FROM dual;

ERR-22018(12006): data value is not a numeric literal :

SELECT 1 + 'a' FROM dual

*

ERROR at line 1:

Use characters which can be converted to numbers or use numbers as follows.

gSQL> SELECT 1 + '2' FROM dual;

1 + '2'

-------

3

1 row selected.

gSQL> SELECT 1 + 2 FROM dual;

1 + 2

-----

3

1 row selected.

The value is out of the data type range when converting.

gSQL> SELECT TO_NATIVE_SMALLINT( '32768' ) AS RESULT FROM DUAL;

ERR-22003(12007): data is outside the range of the data type to which the number is being converted :

SELECT TO_NATIVE_SMALLINT( '32768' ) AS RESULT FROM DUAL

*

ERROR at line 1:

Input the value that is within the data type range as follows.

gSQL> SELECT TO_NATIVE_SMALLINT( '32767' ) AS RESULT FROM DUAL;

RESULT

------

32767

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The invalid hexadecimal value was used.

gSQL> SELECT UNHEX( '41424' ) FROM DUAL;

ERR-22003(12011): data value is not a hexadecimal value :

SELECT UNHEX( '41424' ) FROM DUAL

*

ERROR at line 1:

Use the valid hexadecimal value as follows.

gSQL> SELECT UNHEX( '414243' ) FROM DUAL;

UNHEX( '414243' )

-----------------

414243

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The input timestamp string is out of the column's valid range.

gSQL> CREATE TABLE t1 ( c1 TIMESTAMP(3) );

Table created.

gSQL> INSERT INTO T1 VALUES( '9999-12-31 23:59:59.999999' );

ERR-22018(12013): data value is not a valid date literal or timestamp literal :

INSERT INTO T1 VALUES( '9999-12-31 23:59:59.999999' )

*

ERROR at line 1:

Input the value within the column's valid range as follows.

gSQL> INSERT INTO T1 VALUES( '9999-12-31 23:59:59.999' );

1 row created.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

The time string input in the application is out of the time's valid range.

Action

Use the time string which is within the time's valid range.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The wrong INTERVAL literal was used.

SELECT INTERVAL'1-11' YEAR FROM DUAL;

ERR-22015(12018): data value is a valid interval value; the value in one of the fields is truncated :

SELECT INTERVAL'1-11' YEAR FROM DUAL

*

ERROR at line 1:

Use the correct INTERVAL literal as follows.

gSQL> SELECT INTERVAL'1' YEAR FROM DUAL;

INTERVAL'1' YEAR

----------------

+01-00

1 row selected.

The INTERVAL literal expression is wrong.

gSQL> SELECT INTERVAL'1' YEAR TO MONTH FROM DUAL;

ERR-22018(12019): data value is not a valid interval literal :

SELECT INTERVAL'1' YEAR TO MONTH FROM DUAL

*

ERROR at line 1:

Use the correct INTERVAL literal expression.

gSQL> SELECT INTERVAL'1-1' YEAR TO MONTH FROM DUAL;

INTERVAL'1-1' YEAR TO MONTH

---------------------------

+01-01

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The number is out of the data type's range.

CREATE TABLE t1( c1 NATIVE_BIGINT );

INSERT INTO t1 VALUES( 9223372036854775807 );

COMMIT;

gSQL> SELECT CAST( c1 AS NATIVE_INTEGER ) FROM t1;

ERR-22003(12023): data is outside the range of the data type to which the number is being converted :

SELECT CAST( c1 AS NATIVE_INTEGER ) FROM t1

*

ERROR at line 1:

Check the range of the data type which allows the number.

gSQL> SELECT CAST( c1 AS NUMBER ) FROM t1;

CAST( C1 AS NUMBER )

--------------------

9223372036854775807

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The byte length of the binary data exceeds the column length.

gSQL> SELECT CAST(X'01AF' AS BINARY(1)) FROM dual;

ERR-22001(12027): byte length of data greater than column length :

SELECT CAST(X'01AF' AS BINARY(1)) FROM dual

*

ERROR at line 1:

Use the binary data of the valid byte length as follows.

gSQL> SELECT CAST(X'AF' AS BINARY(1)) FROM dual;

CAST(X'AF' AS BINARY(1))

------------------------

AF

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The datetime value of the operation result, is out of the supported date range.

The value range: '4714-11-24 BC' ~ '9999-12-31 AD'

gSQL> SELECT TO_CHAR( c1, 'YYYY-MM-DD HH24:MI:SS' ) FROM t1;

TO_CHAR( C1, 'YYYY-MM-DD HH24:MI:SS' )

--------------------------------------

9999-12-31 23:59:59

1 row selected.

--# The result of executing the following example exceeds '9999-12-31'.

gSQL> SELECT ROUND( c1, 'HH' ) AS RESULT FROM t1;

ERR-22007(12042): data value does not contain a valid date :

SELECT ROUND( c1, 'HH' ) AS RESULT FROM t1

*

ERROR at line 1:

Check if the datetime value of the operation result is out of the supported date range.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

The datetime value is invalid. (This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The value that was out of the INTERVAL type range was used.

gSQL> CREATE TABLE T1 ( I1 INTERVAL YEAR TO MONTH );

gSQL> INSERT INTO T1 VALUES ( '100-01' );

ERR-22015(12050): one or more fields of data value were truncated during conversion :

INSERT INTO T1 VALUES ( '100-01' )

*

ERROR at line 1

Use the value within the interval type range.

gSQL> INSERT INTO T1 VALUES ( '99-01' );

1 row created.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

When checking the interval value, the interval indicator or the fractional second precision is invalid.

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The value that was out of the interval type range was used.

gSQL> CREATE TABLE T1( I1 INTERVAL DAY );

gSQL> INSERT INTO T1 VALUES ( '100' );

ERR-22015(12054): one or more fields of data value were truncated during conversion :

INSERT INTO T1 VALUES ( '100' )

*

ERROR at line 1:

Use the value within the interval type range.

gSQL> INSERT INTO T1 VALUES ( '99' );

1 row created.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The strings which can not be converted to the number were used.

gSQL> SELECT TO_NATIVE_DOUBLE( 'a' ) FROM DUAL;

ERR-22018(12059): data is not numeric literal :

SELECT TO_NATIVE_DOUBLE( 'a' ) FROM DUAL

*

ERROR at line 1:

Use the numeric string.

gSQL> SELECT TO_NATIVE_DOUBLE( '123.45' ) FROM DUAL;

TO_NATIVE_DOUBLE( '123.45' )

----------------------------

123.45

1 row selected.

The value that was out of the data type range was used.

gSQL> SELECT TO_NUMBER( '1E+1000', '9EEEE' ) FROM DUAL;

ERR-22003(12060): data is outside the range of the data type to which the number is being converted :

SELECT TO_NUMBER( '1E+1000', '9EEEE' ) FROM DUAL

*

ERROR at line 1:

Use the value within the data type range.

gSQL> SELECT TO_NUMBER( '1E+100', '9EEEE' ) FROM DUAL;

TO_NUMBER( '1E+100', '9EEEE' )

------------------------------

1E+100

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The number of numeric digits is bigger than the buffer size.

gSQL> SELECT CAST( 2.43e307D AS CHAR(8) ) FROM dual;

ERR-22003(12072): number of whole digits is greater than buffer length :

SELECT CAST( 2.43e307D AS CHAR(8) ) FROM dual

*

ERROR at line 1:

Use the buffer size which can include the number of numeric digits.

gSQL> SELECT CAST( 2.43e307D AS CHAR(10) ) FROM dual;

CAST( 2.43E307D AS CHAR(10) )

-----------------------------

2.43E+307

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

It is the number that is out of the data type range.

gSQL> SELECT CAST(40000 AS NATIVE_SMALLINT) FROM T1;

ERR-22003(12075): data is outside the range of the data type to which the number is being converted :

SELECT CAST(40000 AS NATIVE_SMALLINT) FROM T1

*

ERROR at line 1:

Use the number within the data type range.

gSQL> SELECT CAST(30000 AS NATIVE_SMALLINT) FROM T1;

CAST(30000 AS NATIVE_SMALLINT)

------------------------------

30000

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The data length is longer than the buffer length.

gSQL> SELECT CAST( 0.0000949525 AS CHAR( 10 ) ) from t1;

ERR-22003(12078): byte length of data is greater than buffer length :

SELECT CAST( 0.0000949525 AS CHAR( 10 ) ) from t1

*

ERROR at line 1:

Use the buffer size that is bigger or the same size as the data length.

gSQL> SELECT CAST( 0.0000949525 AS CHAR( 11 ) ) from t1;

CAST( 0.0000949525 AS CHAR( 11 ) )

----------------------------------

.0000949525

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

When converting the datetime value to a string, the storage for the string is insufficient.

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The range of the TIME ZONE value is invalid.

gSQL> SELECT TIMESTAMP'2000-01-01 23:59:59.999999 +14:59' FROM dual;

ERR-22009(12116): invalid time zone displacement value :

SELECT TIMESTAMP'2000-01-01 23:59:59.999999 +14:59' FROM dual

*

ERROR at line 1:

The range of the TIME ZONE value has to be '-14:00' ~ '+14:00'.

gSQL> SELECT TIMESTAMP'2000-01-01 23:59:59.999999 +09:00' FROM dual;

TIMESTAMP'2000-01-01 23:59:59.999999 +09:00'

--------------------------------------------

2000-01-01 23:59:59.999999 +09:00

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The data type combination which can not be executed as a function argument was used.

gSQL> SELECT 4 * DATE'2024-01-01' FROM dual;

ERR-42000(12118): inconsistent datatype of function parameters: NUMBER, DATE :

SELECT 4 * DATE'2024-01-01' FROM dual

*

ERROR at line 1:

Use the data type which can be used as a function argument.

gSQL> SELECT 4 + DATE'2024-01-01' FROM dual;

4 + DATE'2024-01-01'

--------------------

2024-01-05

1 row selected.

The data type combination which can not be compared was used.

gSQL> SELECT 'OK' FROM dual WHERE 100 = DATE'2024-01-01';

ERR-42000(12119): comparison is not applicable: NUMBER and DATE :

SELECT 'OK' FROM dual WHERE 100 = DATE'2024-01-01'

*

ERROR at line 1:

Use the data type combination which can be compared.

gSQL> SELECT 'OK' FROM dual WHERE 100 = INTERVAL '10' YEAR;

no rows selected.

It is the data type which can not be converted.

gSQL> SELECT CAST( 100 AS BOOLEAN ) FROM dual;

ERR-42000(12120): conversion is not applicable: from NUMBER to BOOLEAN :

SELECT CAST( 100 AS BOOLEAN ) FROM dual

*

ERROR at line 1:

Use the convertible data type.

gSQL> SELECT CAST( 'TRUE' AS BOOLEAN ) FROM dual;

CAST( 'TRUE' AS BOOLEAN )

-------------------------

TRUE

1 row selected.

It is required to check if the character belongs to the specified character set, which does not apply.

Check if the character belongs to the specified character set.

The value 0 was used as the denominator.

gSQL> SELECT 5 / 0 FROM dual;

ERR-22012(12122): divisor is equal to zero :

SELECT 5 / 0 FROM dual

*

ERROR at line 1:

Do not use 0 as the denominator when executing division operation.

It is the string which can not be converted to boolean type.

gSQL> SELECT CAST( 'a' AS BOOLEAN ) FROM dual;

ERR-22018(12123): data is not boolean literal :

SELECT CAST( 'a' AS BOOLEAN ) FROM dual

*

ERROR at line 1:

Use the string that can be converted to boolean type such as TRUE, FALSE.

gSQL> SELECT CAST( 'TRUE' AS BOOLEAN ) FROM dual;

CAST( 'TRUE' AS BOOLEAN )

-------------------------

TRUE

1 row selected.

It is the value that can not be used as an argument for FACTORIAL() function.

gSQL> SELECT factorial(0.6) FROM dual;

ERR-HY000(12124): invalid argument for factorial function :

SELECT factorial(0.6) FROM dual

*

ERROR at line 1:

Use an integer value as follows.

gSQL> SELECT factorial(5) FROM dual;

FACTORIAL(5)

------------

120

1 row selected.

Only one character is allowed for the trim set.

gSQL> SELECT TRIM( BOTH 'ab' FROM 'abca' ) FROM dual;

ERR-22027(12125): trim set should have only one character :

SELECT TRIM( BOTH 'ab' FROM 'abca' ) FROM dual

*

ERROR at line 1:

Describe only one character in the trim set as follows.

gSQL> SELECT TRIM( BOTH 'a' FROM 'abca' ) FROM dual;

TRIM( BOTH 'a' FROM 'abca' )

----------------------------

bc

1 row selected.

It is out of datetime value range.

gSQL> SELECT DATEADD( YEAR, 7999, DATE'2001-01-01' ) FROM DUAL;

ERR-22008(12126): datetime field overflow :

SELECT DATEADD( YEAR, 7999, DATE'2001-01-01' ) FROM DUAL

*

ERROR at line 1:

The operation must not exceed the datetime value range.

gSQL> SELECT DATEADD( YEAR, 7998, DATE'2001-01-01' ) FROM DUAL;

DATEADD( YEAR, 7998, DATE'2001-01-01' )

---------------------------------------

9999-01-01

1 row selected.

ROWID which can not exist was used.

gSQL> CREATE TABLE t1 ( c1 ROWID );

Table created.

gSQL> INSERT INTO T1 VALUES ( '*-ADuwAAAAAAACAAAAAiAAC' );

ERR-HY000(12127): invalid ROWID :

INSERT INTO T1 VALUES ( '*-ADuwAAAAAAACAAAAAiAAC' )

*

ERROR at line 1:

Input ROWID value that exists.

gSQL> INSERT INTO t1 SELECT t2.ROWID FROM t2;

1 row created.

The escape is wrongly used.

gSQL> SELECT c1 FROM t1 WHERE c1 LIKE '____%' ESCAPE '__';

ERR-22019(12128): invalid escape character :

SELECT c1 FROM t1 WHERE c1 LIKE '____%' ESCAPE '__'

*

ERROR at line 1:

gSQL> SELECT c1 FROM t1 WHERE c1 LIKE '____%' ESCAPE '_';

C1

---------

____%____

____A____

2 rows selected.

When specifying the character set or the host variable related to the language while creating DB, the character set that was not supported was specified by the server.

The server supports the character set such as SQL_ASCII, UTF8, UHC, GB18030.

The field to extract does not exist.

gSQL> SELECT c1, EXTRACT( YEAR FROM c1 ) FROM t1;

ERR-HY000(12130): invalid extract field for extract source :

SELECT c1, EXTRACT( YEAR FROM c1 ) FROM t1

*

ERROR at line 1:

Use the field which can be extracted as follows.

gSQL> SELECT c1, EXTRACT( HOUR FROM c1 ) FROM t1;

C1 EXTRACT( HOUR FROM C1 )

--------------- -----------------------

18:18:25.868024 18

1 row selected.

A non-comparable data type was used.

gSQL> SELECT GREATEST( DATE'2024-03-31', 8080 ) FROM dual;

ERR-42000(12131): inconsistent datatypes: argument[2] expected DATE :

SELECT GREATEST( DATE'2024-03-31', 8080 ) FROM dual

*

ERROR at line 1:

Use the identical data type as follows.

gSQL> SELECT GREATEST( DATE'2024-03-31', DATE'2024-04-01' ) FROM dual;

GREATEST( DATE'2024-03-31', DATE'2024-04-01' )

----------------------------------------------

2024-04-01

1 row selected.

It exceeded the maximum length of the date format.

gSQL>

SELECT TO_CHAR( DATE'1999-01-01'

, 'YYYY/1234567890123456789012345678901234567890/MM/1234567890123456789012345678901234567890/DD' )

FROM DUAL;

ERR-HY000(12132): date format value exceeds maximum length (80) :

SELECT TO_CHAR( DATE'1999-01-01'

*

ERROR at line 1:

Decrease the length of the date format as follows.

gSQL>

SELECT TO_CHAR( DATE'1999-01-01'

, 'YYYY / MM / DD' )

FROM DUAL;

TO_CHAR( DATE'1999-01-01'

-------------------------

1999 / 01 / 01

1 row selected.

An invalid date format was used.

gSQL>

SELECT TO_CHAR( DATE'1999-01-01', 'YYYY/FF/DD' ) FROM dual;

ERR-HY000(12133): date format not recognized :

SELECT TO_CHAR( DATE'1999-01-01', 'YYYY/FF/DD' ) FROM dual

*

ERROR at line 1:

Use the valid date format as follows.

gSQL>

SELECT TO_CHAR( DATE'1999-01-01', 'YYYY/MM/DD' ) FROM dual;

TO_CHAR( DATE'1999-01-01', 'YYYY/MM/DD' )

-----------------------------------------

1999/01/01

1 row selected.

The identical format code was used twice.

gSQL>

SELECT TO_DATE( '1999-01-01', 'YYYY-DD-DD' ) FROM dual;

ERR-HY000(12134): format code appears twice :

SELECT TO_DATE( '1999-01-01', 'YYYY-DD-DD' ) FROM dual

*

ERROR at line 1:

Use the valid date format as follows.

gSQL>

SELECT TO_DATE( '1999-01-01', 'YYYY-MM-DD' ) FROM dual;

TO_DATE( '1999-01-01', 'YYYY-MM-DD' )

-------------------------------------

1999-01-01

1 row selected.

The date information about the input string is wrong.

gSQL> SELECT TO_DATE( '2024-02-28 SUNDAY', 'YYYY-MM-DD DAY' ) FROM dual;

ERR-HY000(12135): day of week conflicts with Julian date :

SELECT TO_DATE( '2024-02-28 SUNDAY', 'YYYY-MM-DD DAY' ) FROM dual

*

ERROR at line 1:

Describe the input string about the correct date information.

gSQL> SELECT TO_DATE( '2024-02-28 WEDNESDAY', 'YYYY-MM-DD DAY' ) FROM dual;

TO_DATE( '2024-02-28 wednesday', 'yyyy-mm-dd day' )

---------------------------------------------------

2024-02-28

1 row selected.

The string is not appropriate for the format string.

gSQL>

SELECT DATE'2024' FROM dual;

ERR-HY000(12136): literal does not match format string :

SELECT DATE'2024' FROM dual

*

ERROR at line 1:

Use the valid string as follows.

gSQL>

SELECT DATE'2024-02-28' FROM dual;

DATE'2024-02-28'

----------------

2024-02-28

1 row selected.

The length of the input value is smaller than the date format.

gSQL>

SELECT CAST( '2024' AS DATE ) AS result FROM dual;

ERR-HY000(12137): input value not long enough for date format :

SELECT CAST( '2024' AS DATE ) AS result FROM dual

*

ERROR at line 1:

Use the input value that is appropriate for the date format as follows.

gSQL>

SELECT CAST( '2024-03-01' AS DATE ) AS result FROM dual;

RESULT

----------

2024-03-01

1 row selected.

The date format is smaller than the input value.

gSQL> SELECT TO_DATE ( '2000', 'YYY' ) FROM dual;

ERR-HY000(12138): date format picture ends before converting entire input string :

SELECT TO_DATE ( '2000', 'YYY' ) FROM dual

*

ERROR at line 1:

Use the date format which can interpret the input value as follows.

gSQL> SELECT TO_DATE ( '2000', 'YYYY' ) FROM dual;

TO_DATE ( '2000', 'YYYY' )

--------------------------

2000-01-01

1 row selected.

The year does not exist.

gSQL> SELECT TO_DATE ( '0', 'YYYY' ) FROM dual;

ERR-HY000(12139): year must be between 4714 BC and 9999 AD, and not be 0 :

SELECT TO_DATE ( '0', 'YYYY' ) FROM dual

*

ERROR at line 1:

Use the year within the valid range.

gSQL> SELECT TO_DATE ( '1', 'YYYY' ) FROM dual;

TO_DATE ( '1', 'YYYY' )

-----------------------

0001-01-01

1 row selected.

'_' or '%' must be described after the escape character.

gSQL> SELECT c1 FROM t1 WHERE c1 LIKE '_A%' ESCAPE '_';

ERR-2200C(12140): missing or illegal character following the escape character :

SELECT c1 FROM t1 WHERE c1 LIKE '_A%' ESCAPE '_'

*

ERROR at line 1:

Describe the specified escape character before '_' or '%' of the pattern.

gSQL> SELECT c1 FROM t1 WHERE c1 LIKE '__A%' ESCAPE '_';

C1

----

_ABC

1 row selected.

The input value does not correspond to a month.

gSQL> SELECT TO_DATE( '13', 'MM' ) FROM DUAL;

ERR-HY000(12141): not a valid month :

SELECT TO_DATE( '13', 'MM' ) FROM DUAL

*

ERROR at line 1:

Use the valid value corresponding to a month.

gSQL> SELECT TO_DATE( '12', 'MM' ) FROM DUAL;

TO_DATE( '12', 'MM' )

---------------------

2024-12-01

1 row selected.

The character which can not be converted to numbers was used.

gSQL> SELECT CAST( 'ABC' AS DATE ) FROM dual;

ERR-HY000(12142): a non-numeric character was found where a numeric was expected :

SELECT CAST( 'ABC' AS DATE ) FROM dual

*

ERROR at line 1:

Use the string consisting of numbers that are appropriate for the data type as follows.

gSQL> SELECT CAST( '2024-01-01' AS DATE ) FROM dual;

CAST( '2024-01-01' AS DATE )

----------------------------

2024-01-01

1 row selected.

The value which can not be used as a date was used.

gSQL> INSERT INTO t1 VALUES ( '2024-02-00' );

ERR-HY000(12143): day of month must be between 1 and last day of month :

INSERT INTO t1 VALUES ( '2024-02-00' )

*

ERROR at line 1:

Input the valid day of the month as follows.

gSQL> INSERT INTO t1 VALUES ( '2024-02-01' );

1 row created.

The input day of the week value is wrong.

gSQL> SELECT NEXT_DAY( DATE'2017-05-31', '3' ) FROM dual;

ERR-HY000(12144): not a valid day of the week :

SELECT NEXT_DAY( DATE'2017-05-31', '3' ) FROM dual

*

ERROR at line 1:

Describe the day of the week as follows, or use numbers.

gSQL> SELECT NEXT_DAY( DATE'2017-05-31', 'TUESDAY' ) FROM dual;

NEXT_DAY( DATE'2017-05-31', 'TUESDAY' )

---------------------------------------

2017-06-06

1 row selected.

gSQL> SELECT NEXT_DAY( DATE'2017-05-31', 3 ) FROM dual;

NEXT_DAY( DATE'2017-05-31', 3 )

-------------------------------

2017-06-06

1 row selected.

The number of the days value exceeding the range of the year was used.

gSQL> SELECT TO_DATE( '2024 367', 'YYYY DDD' ) FROM DUAL;

ERR-HY000(12145): day of year must be between 1 and 365 (366 for leap year) :

SELECT TO_DATE( '2024 367', 'YYYY DDD' ) FROM DUAL

*

ERROR at line 1:

Use the number of the days value within the range of the year.

gSQL> SELECT TO_DATE( '2024 365', 'YYYY DDD' ) FROM DUAL;

TO_DATE( '2024 365', 'YYYY DDD' )

---------------------------------

2024-12-30

1 row selected.

The format element which was not allowed for to_datetime function was used.

gSQL> SELECT TO_DATE( '1999-01-01', 'CC' ) FROM dual;

ERR-HY000(12146): format code cannot appear in date input format :

SELECT TO_DATE( '1999-01-01', 'CC' ) FROM dual

*

ERROR at line 1:

Use the format element which is allowed for to_datetime function.

gSQL> SELECT TO_DATE( '2000-01-01', 'YYYY-MM-DD' ) FROM dual;

TO_DATE( '2000-01-01', 'YYYY-MM-DD' )

------------------------------------

2000-01-01

1 row selected.

• Get the value for the format element by using to_char function.

gSQL> SELECT c1, TO_CHAR( c1, 'CC' ) FROM t1;

C1 TO_CHAR( C1, 'CC' )

-------------- -------------------

2000-01-01 20

1 row selected.

The input string is not same as BC/B.C. or AD/A.D. format element.

gSQL> SELECT TO_DATE( '2000-01-01 A', 'YYYY-MM-DD AD' ) FROM DUAL;

ERR-HY000(12147): BC/B.C. or AD/A.D. required :

SELECT TO_DATE( '2000-01-01 A', 'YYYY-MM-DD AD' ) FROM DUAL

*

ERROR at line 1:

Describe the input string which is same as BC/B.C. or AD/A.D. format element

gSQL> SELECT TO_DATE( '2000-01-01 AD', 'YYYY-MM-DD AD' ) FROM DUAL;

TO_DATE( '2000-01-01 AD', 'YYYY-MM-DD AD' )

-------------------------------------------

2000-01-01

1 row selected.

It is not a valid date which can be expressed in format element J.

gSQL> SELECT TO_DATE( ' 5373485 ', 'J' ) FROM DUAL;

ERR-HY000(12148): julian date must be between 0 and 5373484 :

SELECT TO_DATE( ' 5373485 ', 'J' ) FROM DUAL

*

ERROR at line 1:

Specify the valid value that can be expressed in format element J.

( BC 4714-11-24 ( 0 ) ~ 9999-12-31 ( 5373484 ) )

gSQL> SELECT TO_DATE( ' 5373484 ', 'J' ) FROM DUAL;

TO_DATE( ' 5373484 ', 'J' )

---------------------------

9999-12-31

1 row selected.

The identical hour format code was used twice.

gSQL> SELECT TO_TIME( '11:22:33', 'HH:MI:HH24' ) FROM DUAL;

ERR-HY000(12149): hour may only be specified once :

SELECT TO_TIME( '11:22:33', 'HH:MI:HH24' ) FROM DUAL

*

ERROR at line 1:

Use the correct format code as follows.

gSQL> SELECT TO_TIME( '11:22:33', 'HH:MI:SS' ) FROM DUAL;

TO_TIME( '11:22:33', 'HH:MI:SS' )

---------------------------------

11:22:33.000000

1 row selected.

J and DDD can not be used together as a format element.

gSQL> SELECT TO_DATE( '2456653 360', 'J DDD' ) FROM DUAL;

ERR-HY000(12150): Julian date precludes use of day of year :

SELECT TO_DATE( '2456653 360', 'J DDD' ) FROM DUAL

*

ERROR at line 1:

Delete J or DDD from the format element.

gSQL> SELECT TO_DATE( '2456653', 'J' ) FROM DUAL;

TO_DATE( '2456653', 'J' )

-------------------------

2013-12-26

1 row selected.

gSQL> SELECT TO_DATE( '360', 'DDD' ) FROM DUAL;

TO_DATE( '360', 'DDD' )

-----------------------

2024-12-25

1 row selected.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

The time value should be between 0 ~ 23.

gSQL> SELECT TIME '25:10:10.000000' FROM DUAL;

ERR-HY000(12152): hour must be between 0 and 23 :

SELECT TIME '25:10:10.000000' FROM DUAL

*

ERROR at line 1:

Use the value between 0 ~ 23 as follows.

gSQL> SELECT TIME '23:10:10.000000' FROM DUAL;

TIME '23:10:10.000000'

----------------------

23:10:10.000000

1 row selected.

The minute value should be between 0 ~ 59.

gSQL> SELECT TIME '10:60:00.000000' FROM DUAL;

ERR-HY000(12153): minute must be between 0 and 59 :

SELECT TIME '10:60:00.000000' FROM DUAL

*

ERROR at line 1:

Use the value between 0 ~ 59 as follows.

gSQL> SELECT TIME '11:00:00.000000' FROM DUAL;

TIME '11:00:00.000000'

----------------------

11:00:00.000000

1 row selected.

The second value should be between 0 ~ 59.

gSQL> SELECT TIME '10:00:60.000000' FROM DUAL;

ERR-HY000(12154): second must be between 0 and 59 :

SELECT TIME '10:00:60.000000' FROM DUAL

*

ERROR at line 1:

Use the value between 0 ~ 59 as follows.

gSQL> SELECT TIME '10:01:00.000000' FROM DUAL;

TIME '10:01:00.000000'

----------------------

10:01:00.000000

1 row selected.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

The time value of the time zone should be between -14 ~ 14.

gSQL> SELECT TIME WITH TIME ZONE '12:23:34.567 +24:00' FROM DUAL;

ERR-HY000(12156): time zone hour must be between -14 and 14 :

SELECT TIME WITH TIME ZONE '12:23:34.567 +24:00' FROM DUAL

*

ERROR at line 1:

Use the value between -14 ~ 14 as follows.

gSQL> SELECT TIME WITH TIME ZONE '12:23:34.567 +09:00' FROM DUAL;

TIME WITH TIME ZONE '12:23:34.567 +09:00'

-----------------------------------------

12:23:34.567000 +09:00

1 row selected.

The second value in a day should be between 0 ~ 86399.

gSQL> SELECT TO_TIME( '86400', 'SSSSS' ) FROM DUAL;

ERR-HY000(12158): seconds in day must be between 0 and 86399 :

SELECT TO_TIME( '86400', 'SSSSS' ) FROM DUAL

*

ERROR at line 1:

Use the value between 0 ~ 86399 as follows.

gSQL> SELECT TO_TIME( '3600', 'SSSSS' ) FROM DUAL;

TO_TIME( '3600', 'SSSSS' )

--------------------------

01:00:00.000000

1 row selected.

It is not the input string which is same as AM/A.M. or PM/P.M. format element.

gSQL> SELECT TO_TIMESTAMP( '2014-07-10 10:00:00 A.M.', 'YYYY-MM-DD HH12:MI:SS AM' ) FROM DUAL;

ERR-HY000(12159): AM/A.M. or PM/P.M. required :

SELECT TO_TIMESTAMP( '2014-07-10 10:00:00 A.M.', 'YYYY-MM-DD HH12:MI:SS AM' ) FROM DUAL

*

ERROR at line 1:

Describe the input string which is same as AM/A.M. or PM/P.M. format element.

gSQL> SELECT TO_TIMESTAMP( '2014-07-10 10:00:00 AM', 'YYYY-MM-DD HH12:MI:SS AM' ) FROM DUAL;

TO_TIMESTAMP( '2014-07-10 10:00:00 AM', 'YYYY-MM-DD HH12:MI:SS AM' )

--------------------------------------------------------------------

2014-07-10 10:00:00.000000

1 row selected.

HH24 and (AM/PM) can not be used together.

gSQL> SELECT TO_TIME( '12:59:59.999999 AM', 'HH24:MI:SS.FF6 AM' ) FROM DUAL;

ERR-HY000(12160): HH24 precludes use of meridian indicator :

SELECT TO_TIME( '12:59:59.999999 AM', 'HH24:MI:SS.FF6 AM' ) FROM DUAL

*

ERROR at line 1:

Do not use (AM/PM) as follows.

gSQL> SELECT TO_TIME( '12:59:59.999999', 'HH24:MI:SS.FF6' ) FROM DUAL

TO_TIME( '12:59:59.999999', 'HH24:MI:SS.FF6' )

----------------------------------------------

12:59:59.999999

1 row selected.

The datetime format elements can not be mixed.

For example, AM/PM and A.M./P.M. can not be used together.

gSQL> SELECT TO_TIMESTAMP( '2000-01-01 11:22:33 A.M. AM', 'YYYY-MM-DD HH:MI:SS A.M. AM' ) FROM DUAL;

ERR-HY000(12161): AM/PM conflicts with use of A.M./P.M. :

SELECT TO_TIMESTAMP( '2000-01-01 11:22:33 A.M. AM', 'YYYY-MM-DD HH:MI:SS A.M. AM' ) FROM DUAL

*

ERROR at line 1:

Use the valid datetime format as follows.

gSQL> SELECT TO_TIMESTAMP( '2000-01-01 11:22:33 A.M.', 'YYYY-MM-DD HH:MI:SS A.M.' ) FROM DUAL;

TO_TIMESTAMP( '2000-01-01 11:22:33 A.M.', 'YYYY-MM-DD HH:MI:SS A.M.' )

----------------------------------------------------------------------

2000-01-01 11:22:33.000000

1 row selected.

xid of the target xa transaction to execute in-doubt commit/rollback is invalid..

gSQL> COMMIT FORCE '0.';

ERR-HY000(16259): the XID string is not valid:

COMMIT FORCE '0.'

*

ERROR at line 1:

ERR-HY000(12162): invalid XID string

gSQL> ROLLBACK FORCE '0.';

ERR-HY000(16259): the XID string is not valid:

ROLLBACK FORCE '0.'

*

ERROR at line 1:

ERR-HY000(12162): invalid XID string

Check xa transaction to execute commit/rollback by viewing V$XA_TRANSACTION (V$XA_TRANSACTION).

The date which can not exist in November was used.

gSQL> SELECT TO_DATE( '2011-11-31' ) FROM DUAL;

ERR-HY000(12163): date not valid for month specified :

SELECT TO_DATE( '2011-11-31' ) FROM DUAL

*

ERROR at line 1:

Use the date which exists in the corresponding month.

gSQL> SELECT TO_DATE( '2011-11-30' ) FROM DUAL;

TO_DATE( '2011-11-30' )

-----------------------

2011-11-30

1 row selected.

SYYYY and BC/AD can not be used together.

gSQL> SELECT TO_DATE( '2013-09-24 AD', 'SYYYY-MM-DD AD' ) FROM DUAL;

ERR-HY000(12164): signed year precludes use of BC/AD :

SELECT TO_DATE( '2013-09-24 AD', 'SYYYY-MM-DD AD' ) FROM DUAL

*

ERROR at line 1:

Do not use SYYYY and BC/AD together as follows.

gSQL> SELECT TO_DATE( '2013-09-24', 'SYYYY-MM-DD' ) FROM DUAL;

TO_DATE( '2013-09-24', 'SYYYY-MM-DD' )

--------------------------------------

2013-09-24

1 row selected.

The format string length exceeds the maximum length.

gSQL> SELECT TO_CHAR( c1, 'FM99999999999999999999999999999999999999999999999999999999999999999999999' ) FROM t1;

ERR-HY000(12165): number format value exceeds maximum length (64) :

SELECT TO_CHAR( c1, 'FM99999999999999999999999999999999999999999999999999999999999999999999999' ) FROM t1

*

ERROR at line 1:

Set the format string length within the maximum length.

gSQL> SELECT TO_CHAR( c1, 'FM999999' ) FROM t1;

TO_CHAR( C1, 'FM999999' )

-------------------------

123

99999

2 rows selected.

The format which can not be converted to a number was used.

gSQL> SELECT TO_NUMBER( '12345 ', '99999 ' ) FROM DUAL;

ERR-HY000(12166): invalid number format model :

SELECT TO_NUMBER( '12345 ', '99999 ' ) FROM DUAL

*

ERROR at line 1:

Remove the white space as follows.

gSQL> SELECT TO_NUMBER( '12345', '99999' ) FROM DUAL;

TO_NUMBER( '12345', '99999' )

-----------------------------

12345

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Some number format elements can not be mixed.

gSQL> SELECT TO_CHAR( -12, 'S999MI' ) FROM DUAL;

ERR-HY000(12168): cannot use MI and S PR together :

SELECT TO_CHAR( -12, 'S999MI' ) FROM DUAL

*

ERROR at line 1:

Describe the number format element independently.

gSQL> SELECT TO_CHAR( -12, 'S999' ) FROM DUAL;

TO_CHAR( -12, 'S999' )

----------------------

-12

1 row selected.

gSQL> SELECT TO_CHAR( -12, '999MI' ) FROM DUAL;

TO_CHAR( -12, '999MI' )

-----------------------

12-

1 row selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

The argument value of INSTR() function is wrong.

gSQL> SELECT INSTR( 'AB AB AB AB', 'AB', 1, -1 ) FROM t1;

ERR-HY000(12170): argument '-1' is out of range :

SELECT INSTR( 'AB AB AB AB', 'AB', 1, -1 ) FROM t1

*

ERROR at line 1:

The fourth argument of INSTR() function should be an integer 1 or bigger.

gSQL> SELECT INSTR( 'AB AB AB AB', 'AB', 1, 3 ) FROM t1;

INSTR( 'AB AB AB AB', 'AB', 1, 3 )

----------------------------------

7

1 row selected.

datepart (DAY) which can not be applied to the data type was used.

gSQL> SELECT DATEADD( DAY, 1, TIME'11:22:33.123456' ) FROM DUAL;

ERR-HY000(12171): invalid datepart for data type TIME WITHOUT TIME ZONE :

SELECT DATEADD( DAY, 1, TIME'11:22:33.123456' ) FROM DUAL

*

ERROR at line 1:

Use datepart (HOUR) which can be applied to the data type as follows.

gSQL> SELECT DATEADD( HOUR, 1, TIME'11:22:33.123456' ) FROM DUAL;

DATEADD( HOUR, 1, TIME'11:22:33.123456' )

-----------------------------------------

12:22:33.123456

1 row selected.

This is an error code used within the server.

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

The argument value of the function is wrong.

gSQL> SELECT LOG(0) FROM dual;

ERR-22023(12174): The argument of LOG function is invalid :

SELECT LOG(0) FROM dual

*

ERROR at line 1:

The argument of the function should be a positive number.

gSQL> SELECT LOG(100) FROM dual;

LOG(100)

--------

2

1 row selected.

The argument value of the function is wrong.

gSQL> SELECT LOG(0, 4) FROM dual;

ERR-22023(12175): The argument [1] of LOG function is invalid :

SELECT LOG(0, 4) FROM dual

*

ERROR at line 1:

Use the valid argument value of the function as follows.

gSQL> SELECT LOG(2, 4) FROM dual;

LOG(2, 4)

---------

2

1 row selected.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

The type which can not be used together was used.

gSQL>

SELECT 'A' FROM dual

UNION ALL

SELECT 1 FROM dual

;

ERR-42000(12185): CHAR and NUMBER cannot be matched :

SELECT 'A' FROM dual

*

ERROR at line 1:

Use the type which can be used together as follows.

gSQL>

SELECT 'A' FROM dual

UNION ALL

SELECT '1' FROM dual

;

'A'

---

A

1

2 rows selected.

Number can not be used as an argument of HEX() function.

gSQL> SELECT HEX( 123 ) FROM dual;

ERR-0A000(12186): not supported function argument numeric types : Use to_char(num, 'XXXX') instead of hex(num) :

SELECT HEX( 123 ) FROM dual

*

ERROR at line 1:

Use TO_CHAR( number, 'XXXX' ) function.

gSQL> SELECT TO_CHAR( 123, 'XXXX' ) FROM dual;

TO_CHAR( 123, 'XXXX' )

----------------------

7B

1 row selected.

--# result: failed to open library

SELECT MOJ_MATCH_FP( X'111111', X'AABBCCDDEEFF' ) FROM DUAL;

ERR-39000(12187): failed to open customer built-in function library ($GOLDILOCKS_HOME/lib/libMojMatchFP.so) :

SELECT MOJ_MATCH_FP( X'111111', X'AABBCCDDEEFF' ) FROM DUAL

*

ERROR at line 1:

Action

The function can be performed only when a specific library exists.

NULL value can not be used as a window frame offset.

gSQL>

SELECT c1

, MIN(c1) OVER ( ORDER BY c1

RANGE NULL PRECEDING ) min_value

FROM t1;

ERR-42000(12188): window frame offset must not be null :

RANGE NULL PRECEDING )

*

ERROR at line 3:

Use numbers such as RANGE 2 PRECEDING as follows.

gSQL>

SELECT c1

, MIN(c1) OVER ( ORDER BY c1

RANGE 2 PRECEDING ) min_value

FROM t1;

C1 MIN_VALUE

-----------

1 1

2 1

3 1

4 2

5 3

5 rows selected.

A negative number can not be used as a window frame offset.

gSQL>

SELECT c1

, MIN(c1) OVER ( ORDER BY c1

RANGE -2 PRECEDING ) min_value

FROM t1;

ERR-42000(12189): window frame offset must not be negative :

RANGE -2 PRECEDING ) min_value

*

ERROR at line 3:

Use positive numbers such as RANGE 2 PRECEDING as follows.

gSQL>

SELECT c1

, MIN(c1) OVER ( ORDER BY c1

RANGE 2 PRECEDING ) min_value

FROM t1;

C1 MIN_VALUE

------------

1 1

2 1

3 1

4 2

5 3

5 rows selected.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

The database has not been fully initialized.

Action

Retry the operation after the initialization is complete.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

An incorrect shared memory type was specified.

Action

If this error occurs, contact our customer service department.

Cause

The shared memory segment is corrupted.

Action

Shut down the system properly and restart the database.

Cause

Too many shared memory segments have been created.

Action

Increase the system's shared memory limits.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

This error is managed internally by the server, so it is not visible to the client.

Action

If this error occurs, contact our customer service department.

Cause

This is an error code used within the server.

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

An invalid SCOPE parameter was used.

Action

Use a valid SCOPE parameter (MEMORY / SPFILE / BOTH) for the property.

Cause

The GOLDILOCKS_DATA environment variable is invalid.

Action

Verify that the GOLDILOCKS_DATA environment variable is correctly defined.

Cause

deprecated

Action

If this error occurs, contact our customer service department.

Cause

This is an internally controlled server error.

Action

If this error occurs, contact our customer service department.

Cause