GSE0000-0999
| GSE Message ID | Message | Explanation | User Response |
|---|---|---|---|
|
GSE0000I |
The operation was completed successfully. |
No errors were encountered during the execution of this operation. |
No action required. msgcode: 0 sqlstate: 00000 |
|
GSE0001C |
An internal error occurred. |
The spatial operation encountered an unexpected internal error. |
Repeat the command. If the problem persists, contact IBM Software Support. msgcode: -1 sqlstate: 38S01 |
|
GSE0002C |
The spatial operation could not access its memory pool. Reason code = reason-code. |
The spatial operation tried unsuccessfully to access its memory pool. |
Note the reason code reason-code and contact IBM Software Support. msgcode: -2 sqlstate: 38S02 |
|
GSE0003N |
The spatial operation could not allocate number bytes of memory. |
Not enough memory was available. Possible reasons are that the supply of memory was too low, or that memory was being used by other applications. |
Resolve the memory shortage and repeat the command. msgcode: -3 sqlstate: 38S03 |
|
GSE0004C |
An internal parameter error occurred. |
The spatial operation encountered an unexpected error in a parameter passed to an internal function. The operation cannot be completed successfully. |
Repeat the command. If the problem persists, contact IBM Software Support. msgcode: -4 sqlstate: 38S04 |
|
GSE0005N |
The spatial operation could not retrieve the instance path. |
The spatial operation could not retrieve the instance path. The operation cannot be completed successfully. |
Verify the database environment. If necessary, contact IBM Software Support. msgcode: -5 sqlstate: 38S05 |
|
GSE0006N |
An internal string error occurred. |
The spatial operation encountered an unexpected error in an internal string operation. The operation cannot be completed successfully. |
Repeat the command. If the problem persists, contact IBM Software Support. msgcode: -6 sqlstate: 38S06 |
|
GSE0007N |
The string string is missing either a closing quotation mark or a closing pair of quotation marks. |
This string lacks a closing delimiter and therefore is not terminated correctly. |
Terminate the string correctly. If it starts with a quotation mark, close it with a quotation mark. If it starts with a pair of quotation marks, close it with a pair of quotation marks. msgcode: -7 sqlstate: 38S07 |
|
GSE0008N |
An invalid error code error-code was used to raise an error. |
There was an attempt to raise an error identified by an invalid error-code. |
Contact IBM Software Support. msgcode: -8 sqlstate: 38S08 |
|
GSE0009N |
Not enough space is available in the database application heap. |
The available memory for the database application heap was exceeded. The operation cannot be completed successfully. |
On receipt of this message, terminate the application. Increase the database configuration parameter (APPLHEAPSZ) to allow a larger application heap. Refer to the Spatial documentation for more information. msgcode: -9 sqlstate: 38S09 |
|
GSE0010N |
Not enough log space is available to the database. |
All available space in the database transaction log is being used. The operation cannot be completed successfully. |
If the database is being used by other applications concurrently, retry the operation. Log space may be freed up when another application finishes a transaction. Increase the database configuration parameters to allow more log space. For example, the database configuration parameters LOGPRIMARY, LOGSECOND, and LOGFILSIZ can be modified to increase the size of the available logs. msgcode: -10 sqlstate: 38S0A |
|
GSE0100N |
The spatial operation could not open a file named file-name. Reason code = reason-code. |
Reasons why a file cannot be opened, preceded by their reason codes, are as follows:
All other reason codes indicate an internal error. |
Verify the authorization for the file and the directories, then repeat the command. If a reason code that indicates an internal error was encountered, contact IBM Software Support. msgcode: -100 sqlstate: 38S10 |
|
GSE0101N |
An I/O error occurred while a file named file-name was being processed. Reason code = reason-code. |
Reasons why an I/O error can occur during file processing, preceded by their reason codes, are as follows:
All other reason codes indicate an internal error. |
Verify that the file exists, that you have the appropriate access to the file, and that the file is not in use by another process. If a reason code that indicates an internal error was encountered, contact IBM Software Support. msgcode: -101 sqlstate: 38S11 |
|
GSE0102N |
The spatial operation could not close a file named file-name. Reason code = reason-code. |
Reasons why an error can occur during an attempt to close a file, preceded by their reason codes, are as follows:
All other reason codes indicate an internal error. |
Verify that the file system is in fully working condition and that enough disk space is available. If a reason code that indicates an internal error was encountered, contact IBM Software Support. msgcode: -102 sqlstate: 38S12 |
|
GSE0103N |
The spatial operation could not delete a file named file-name. Reason code = reason-code. |
Reasons why an error can occur during an attempt to delete a file, preceded by their reason codes, are as follows:
All other reason codes indicate an internal error. |
Given for each reason code:
If a reason code that indicates an internal error was encountered, contact IBM Software Support. msgcode: -103 sqlstate: 38S13 |
|
GSE0200N |
An attempt to connect to the database failed. SQLERROR = sql-error. |
The spatial operation was not able to connect to the database. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -200 sqlstate: 38S20 |
|
GSE0201W |
An attempt to disconnect from the database failed. SQLERROR = sql-error. |
The spatial operation was not able to disconnect from the database. The database returned sql-error. |
Refer to the description of sql-error. msgcode: +201 sqlstate: 38S21 |
|
GSE0202N |
No connection to a database exists. |
The spatial operation cannot connect to a database. The command cannot be executed successfully. |
Verify the spatial and database setup. Make sure that a connection to the database can be established. msgcode: -202 sqlstate: 38S22 |
|
GSE0203W |
The spatial operation was already connected to database database-name. |
The spatial operation tried to connect to the database database-name but was already connected to it. |
Contact IBM Software Support. msgcode: +203 sqlstate: 38S23 |
|
GSE0204N |
An attempt to commit a transaction failed. SQLERROR = sql-error. |
The spatial operation could not commit the current transaction successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -204 sqlstate: 38S24 |
|
GSE0205W |
An attempt to roll back a transaction failed. SQLERROR = sql-error. |
The spatial operation could not roll back the current transaction. The database returned sql-error. |
Refer to the description of sql-error. msgcode: +205 sqlstate: 38S25 |
|
GSE0206N |
A SELECT statement failed. SQLERROR = sql-error. |
The spatial operation could not execute a SELECT statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -206 sqlstate: 38S26 |
|
GSE0207N |
A VALUES statement failed. SQLERROR = sql-error. |
The spatial operation could not execute a VALUES statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -207 sqlstate: 38S27 |
|
GSE0208N |
A PREPARE statement failed. SQLERROR = sql-error. |
The spatial operation could not prepare an SQL statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -208 sqlstate: 38S28 |
|
GSE0209N |
An attempt to open an SQL cursor failed. SQLERROR = sql-error. |
The spatial operation could not open a cursor over a result set successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -209 sqlstate: 38S29 |
|
GSE0210W |
An attempt to close an SQL cursor failed. SQLERROR = sql-error. |
The spatial operation could not close a cursor over a result set successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: +210 sqlstate: 38S2A |
|
GSE0211N |
A fetch from an SQL cursor failed. SQLERROR = sql-error. |
The spatial operation could not fetch a result from a cursor successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -211 sqlstate: 38S2B |
|
GSE0212N |
An attempt to drop an object failed. SQLERROR = sql-error. |
The spatial operation could not drop the specified database object. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -212 sqlstate: 38S2C |
|
GSE0213N |
A bind operation failed. SQLERROR = sql-error. |
The spatial operation could not bind the specified file to the current database. The database returned sql-error. This error can occur if the size of the database application heap is too small. |
Verify that the database is enabled for spatial operations. If the error occurs during the enabling, verify the installation of the spatial feature. If the problem persists, increase the database configuration parameter (APPLHEAPSZ) for the size of the application heap. msgcode: -213 sqlstate: 38S2D |
|
GSE0214N |
An INSERT statement failed. SQLERROR = sql-error. |
The spatial operation could not execute an INSERT statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -214 sqlstate: 38S2E |
|
GSE0215N |
An UPDATE statement failed. SQLERROR = sql-error. |
The spatial operation could not execute an UPDATE statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -215 sqlstate: 38S2F |
|
GSE0216N |
A DELETE statement failed. SQLERROR = sql-error. |
The spatial operation could not execute a DELETE statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -216 sqlstate: 38S2G |
|
GSE0217N |
A LOCK TABLE statement failed. SQLERROR = sql-error. |
The spatial operation could not execute a LOCK TABLE statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -217 sqlstate: 38S2H |
|
GSE0218N |
A DECLARE GLOBAL TEMPORARY TABLE statement failed. SQLERROR = sql-error. |
The spatial operation could not execute a DECLARE GLOBAL TEMPORARY TABLE statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -218 sqlstate: 38S2I |
|
GSE0219N |
An EXECUTE IMMEDIATE statement failed. SQLERROR = sql-error. |
The spatial operation could not execute an EXECUTE IMMEDIATE statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -219 sqlstate: 38S2J |
|
GSE0220N |
The setting of a savepoint failed. SQLERROR = sql-error. |
The spatial operation could not set a savepoint successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -220 sqlstate: 38S2K |
|
GSE0221N |
No database name was specified. |
The spatial operation could not connect to a database because the name of the database was not specified. |
Specify a database name. msgcode: -221 sqlstate: 38S2L |
|
GSE0222N |
An attempt to retrieve the authorization list from the database failed. SQLERROR = sql-error. |
The spatial operation could not retrieve the authorization list for the current user. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -222 sqlstate: 38S2M |
|
GSE0223N |
An attempt to quiesce a table space failed. SQLERROR = sql-error. |
The spatial operation could not quiesce a table space successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -223 sqlstate: 38S2N |
|
GSE0224N |
An attempt to import data into a table failed. SQLERROR = sql-error. |
The spatial operation could not import data into a table successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -224 sqlstate: 38S2O |
|
GSE0225N |
An attempt to retrieve the database configuration or the database manager configuration failed. SQLERROR = sql-error. |
The spatial operation could not retrieve the configuration for the current database or the configuration for the database manager successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -225 sqlstate: 38S2P |
|
GSE0226N |
An attempt to create a trigger failed. SQLERROR = sql-error. |
The spatial operation could not create a trigger successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -226 sqlstate: 38S2Q |
|
GSE0227N |
An ALTER TABLE statement failed. SQLERROR = sql-error. |
The spatial operation could not execute an ALTER TABLE statement successfully. The database returned sql-error. |
Refer to the description of sql-error. msgcode: -227 sqlstate: 38S2R |
|
GSE0228N |
An attempt to retrieve the message for error gse-error and SQLCODE = sqlcode from the Spatial message catalog failed. |
The spatial operation could not retrieve the message for error gse-error and SQLCODE = sqlcode successfully. |
Verify the installation of the Spatial feature. Verify also that the message catalog in the language that you want to use is installed. msgcode: -228 sqlstate: 38S2S |
|
GSE0229N |
An attempt to bind a file named bind-file failed. Reason code = reason-code. |
The spatial operation failed in an attempt to use the sqlabndx function to bind the file named bind-file to the database. sqlabndx returned the reason code reason-code. |
Verify that the database is enabled for spatial operations. Refer to the description of reason-code for the function sqlabndx. msgcode: -229 sqlstate: 38S2T |
|
GSE0230N |
The system catalog could not be updated. |
The spatial operation encountered an error while attempting to use the database service to update the system catalog. |
Contact IBM Software Support. msgcode: -230 sqlstate: 38S2U |
|
GSE0231N |
A PREPARE statement encountered a warning condition. SQLWARNING = sql-warning. |
The spatial operation encountered a warning condition when preparing an SQL statement. The database returned sql-warning. The PREPARE statement was completed successfully. |
Refer to the description of sql-warning. msgcode: -231 sqlstate: 38S2V |
|
GSE0300N |
The specified password is too long. |
The password used in your attempt to connect to the database is too long. |
Verify that the password you specified is correct. If it is the correct password, then shorten it and try the operation again. msgcode: -300 sqlstate: 38S40 |
|
GSE0301N |
The specified schema name, schema-name, is too long. |
The requested operation cannot be completed successfully because the length of the schema name exceeds the database limit for schema names. |
Specify a valid, shorter schema name. For more information on the schema name length limit, refer to the Spatial documentation and try the operation again. msgcode: -301 sqlstate: 38S41 |
|
GSE0302N |
The specified table name, table-name, is too long. |
The requested operation cannot be completed successfully because the length of the table name exceeds the database limit for table names. |
Specify a valid, shorter table name. For more information on the table name length limit, refer to the Spatial documentation and try the operation again. msgcode: -302 sqlstate: 38S42 |
|
GSE0303N |
The specified column name, column-name, is too long. |
The requested operation cannot be completed successfully because the length of the column name exceeds the database limit for column names. |
Specify a valid, shorter column name. For more information on the column name length limit, refer to the Spatial documentation, and then try the operation again. msgcode: -303 sqlstate: 38S43 |
|
GSE0304N |
The specified index name, index-name, is too long. |
The requested operation cannot be completed successfully because the length of the index name exceeds the database limit for index names. |
Specify a valid, shorter index name. For more information on the index name length limit, refer to the Spatial documentation, and then try the operation again. msgcode: -304 sqlstate: 38S44 |
|
GSE0305N |
The specified data type name, type-name, is too long. |
The requested operation cannot be completed successfully because the length of the data type name exceeds the database limit for data type names. |
Specify a valid, shorter type name. For more information on the data type name length limit, refer to the Spatial documentation, and then try the operation again. msgcode: -305 sqlstate: 38S45 |
|
GSE0306N |
A complete path that starts with path would exceed the acceptable limit of limit bytes. |
The file in a path that starts with path cannot be accessed because the length of the complete path would exceed the limit of limit bytes. As a result, the statement that you submitted cannot be executed successfully. |
Change the location of the file to be accessed so that it can be found using a shorter path and re-submit the statement that you specified. On UNIX systems, symbolic links can be used to establish a shorter path name. msgcode: -306 sqlstate: 38S46 |
|
GSE0307N |
The length of a dynamic SQL statement statement-length would exceed the acceptable limit of limit bytes. |
The statement cannot be constructed because it would be too long. |
If the statement is constructed in the context of a stored procedure, verify that the WHERE clause is not too long. If necessary, shorten the WHERE clause and retry the operation. If the problem persists, contact IBM Software Support. msgcode: -307 sqlstate: 38S47 |
|
GSE0308N |
The string, string, exceeds the limit of limit bytes. |
The requested operation cannot be completed successfully because the string, string, is too long. |
Specify a shorter string. If necessary, contact IBM Software Support. msgcode: -308 sqlstate: 38S48 |