GSE2000-2999

GSE2100N

If you are importing columns that contain attribute data, you have the choice of either specifying or not specifying which attribute columns are being imported and which columns are in the target table. If you specify these values, this error occurs when the specified number of attribute columns being imported differs from the specified number of columns in the target table. If you do not specify these values, this error occurs when the actual number of columns being imported differs from the actual number of attribute columns in the target table.

Make sure that the number of specified or actual attribute columns being imported matches the number of specified or actual columns in the target table.

msgcode: -2100

sqlstate: 38S70

GSE2101N

The spatial data type schema-name.type-name cannot be used during the import of spatial data because it does not exist in the database.

Create the data type in the database or use a data type that exists.

msgcode: -2101

sqlstate: 38S71

GSE2102N

A table named schema-name.table-name does not exist in the database. Also, the spatial operation was not asked to create a table to hold the data that is to be imported. The data was not imported.

If the table is to be created by the spatial operation, specify the appropriate flag. Otherwise, create the table and retry the operation.

msgcode: -2102

sqlstate: 38S72

GSE2103N

The spatial operation was asked to create a table named schema-name.table-name for the imported data, but a table with that name already exists in the database. No data was imported.

If the table is not to be created by the spatial operation, do not indicate that the table is to be created. Otherwise, specify the name for a table which does not yet exist in the database.

msgcode: -2103

sqlstate: 38S73

GSE2104N

The column into which you want to import data column-name does not exist in the table schema-name.table-name. No data can be imported into it.

Correct the column name or create the column in the table that is to be imported, or correct the table name.

msgcode: -2104

sqlstate: 38S74

GSE2105W

The import operation completed successfully but not all records from the file were imported. The exception file contains the records that could not be imported, and the messages file the contains information why those records were not imported.

Consult the messages file for the reason why not all records were imported, correct the problem and repeat the operation with the original file or the exception file.

msgcode: +2105

sqlstate: 38S75

GSE2106N

The column column-name in the table schema-name.table-name to import data into has a declared type column-type. column-type does not match the type name expected-type for the data to be imported from the file. No data can be imported.

Verify the definition of the table with the structure of the file to be imported.

msgcode: -2106

sqlstate: 38S76

GSE2107N

The spatial operation was asked to create a table to import data into, but the table could not be created successfully. The database returned sql-error.

Refer to the description of this sql-error.

msgcode: -2107

sqlstate: 38S77

GSE2108N

Either no method specification was given or method is not a valid method specification. Only 'N' and 'P' are supported method specifications for importing spatial data from a file.

Correct the method specification and try the method again.

msgcode: -2108

sqlstate: 38S78

GSE2109N

An unexpected character found-char was found in the string that identifies the attribute columns to be imported from the file but expected-char was expected. The statement cannot be processed successfully.

Correct the string that identifies the attribute columns to be imported from the file.

msgcode: -2109

sqlstate: 38S79

GSE2110N

The column position identifier position specified in the string starting with string is not in the valid range. Only values greater than 0 (zero) and less than or equal to the number of columns in the file to be imported can be specified. The statement cannot be processed successfully.

Correct the column position identifier.

msgcode: -2110

sqlstate: 38S7A

GSE2111N

The name of column dbf-column-name in the dBASE file (.dbf) exceeds the database limit for column names.

Specify a dbf-column-name that does not exceed the length limit for column names in the database.

msgcode: -2111

sqlstate: 38S7B

GSE2112N

The name dbf-column-name does not identify an existing attribute column in the dBASE file (.dbf). The operation cannot be completed successfully.

Specify a column name that exists in the dBASE file.

msgcode: -2112

sqlstate: 38S7C

GSE2113N

The dBASE file data type dbf-data-type for the attribute column dbf-column-name in the dBASE file (.dbf) cannot be mapped to a data type in the database. The shape file cannot be imported.

Exclude the column from the column list.

msgcode: -2113

sqlstate: 38S7D

GSE2114N

The specified column position position must be a value within the valid range. A valid value must greater than 0 (zero) and less than or equal to the dbf-column-number.

Specify a valid position.

msgcode: -2114

sqlstate: 38S7E

GSE2115N

A spatial reference system whose numeric identifier is srs-id does not exist. The data cannot be imported.

Either specify an existing spatial reference system, or create the spatial reference system before attempting the import operation.

msgcode: -2115

sqlstate: 38S7F

GSE2116N

The coordinate system definition coordsys-def used for the spatial data to be imported is too long. It could not be verified with the coordinate system that underlies the spatial reference system that is to be used for the imported data.

Verify that the coordinate system defined in the projection file (.prj) is correct. To skip the verification step, do not supply the projection file.

msgcode: -2116

sqlstate: 38S7G

GSE2117N

The coordinate system coordsys-def does not match the coordinate system on which the spatial reference system srs-id is based. Both coordinate systems must be semantically identical.

Verify that the coordinate system defined in the projection file (.prj) matches the coordinate system of the spatial reference system. To skip the verification step, do not supply the projection file.

msgcode: -2117

sqlstate: 38S7H

GSE2118N

The spatial data covers an area that exceeds the minimum and maximum coordinates of the spatial reference system with the numeric identifier srs-id.

Specify a spatial reference system which may fully contain the spatial data to be imported. When using Spatial Extender, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, otherwise the SYSGEO.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, for the minimum and maximum coordinate values applicable for the spatial reference system.

msgcode: -2118

sqlstate: 38S7I

GSE2119N

The spatial column schema-name.table-name.column-name was registered with a spatial reference system srs-id2 assigned to it. This spatial reference system does not match the spatial reference system srs-id1, which is used for the spatial data to be imported into that column. The data cannot be imported.

Either unregister the spatial column, or specify the same spatial reference system for the data to be imported that the column uses.

msgcode: -2119

sqlstate: 38S7J

GSE2120N

None of the shape data could be imported. All rows were rejected and written to the exception file.

Consult the message file for the reasons why all the spatial data was rejected.

msgcode: -2120

sqlstate: 38S7K

GSE2121N

The specified restartCount restart-count must be a greater than or equal to 0 (zero), and less than or equal to record-count.

Specify a valid number for restartCount, or specify a null value for the resartCount.

msgcode: -2121

sqlstate: 38S7L

GSE2122N

The SQL statement used to import the shape data into the table does not fit into the internal buffer. A possible reason for this might be too many columns are in the file.

Import a smaller set of the attribute columns in the shape file.

msgcode: -2122

sqlstate: 38S7M

GSE2123N

The spatial operation tried to use a single INSERT statement to import at least row-count rows, but a buffer to hold the data for these rows could not be allocated. Too much memory was required.

Specify a commit count for the import that is less than row-count. Or, specify a smaller set of columns to be imported. This will reduce the amount of memory required.

msgcode: -2123

sqlstate: 38S7N

GSE2124N

The data in the shape file does not appear to have a valid spatial data type. The shape file is possibly corrupted. The data was not imported.

Verify that the shape file is valid.

msgcode: -2124

sqlstate: 38S7O

GSE2125N

The shape file contains a column whose data type is not supported. The shape file could not be imported.

Import only a smaller set of the columns of the shape file and omit the column with the unsupported data type.

msgcode: -2125

sqlstate: 38S7P

GSE2126N

The header of the shape file shape-file is invalid. The shape file cannot be imported.

Verify and correct the header of the shape file.

msgcode: -2126

sqlstate: 38S7Q

GSE2127N

The offset offset for the record record-number in the index file (.shx) shx-file is invalid. The offset must be greater than or equal to 50 and less than the total length of the main file (.shp) of the shape file. The offset is measured in 16 bit words.

Verify and correct the shape file.

msgcode: -2127

sqlstate: 38S7R

GSE2128N

The length of the shape in record record-number found in the shape index file shx-file is too short. Each shape must consist of at least 4 bytes (two 16 bit words).

Verify and correct the shape file.

msgcode: -2128

sqlstate: 38S7S

GSE2129N

The spatial operation found an incorrect record number record-number in the shape file shp-file when expecting record number expected-number.

Verify and correct the shape file.

msgcode: -2129

sqlstate: 38S7T

GSE2130N

The size of the shape data record-size indicated in the shape file shp-file does not match the size indicated in the shape index file index-size.

The main file of the shape file (.shp) is not consistent with the index file (.shx) and cannot be processed further.

Verify and correct the shape file.

msgcode: -2130

sqlstate: 38S7U

GSE2131N

The data for record record-number in the dBASE file dbf-file that contains the attribute information associated with the geometries in the shape file is invalid.

Verify and correct the dBASE file.

msgcode: -2131

sqlstate: 38S7V

GSE2132N

The data in shape file shape-file is corrupted. This shape file cannot be imported.

The file name shape-file indicates in which part of the shape file the error was encountered.

Verify and correct the shape file.

msgcode: -2132

sqlstate: 38S7W

GSE2133N

The definition of the column column-name in the existing table schema-name.table-name indicates that the column may not contain nulls. The column is not included in the list of columns to be imported and the database would not produce the values for that column by any other means like default values, a generated column definition or any triggers.

The import operation cannot be completed successfully.

Include the column in the list of columns to be imported, identify the column as id-column, or define an alternate way for the database manager to generate the values for that column during the import operation.

msgcode: -2133

sqlstate: 38S7X

GSE2134N

The spatial data in the file to be imported uses a spatial reference system with different offsets and scale factors than the spatial reference system with the numeric identifier srs-id. The data cannot be imported successfully.

Specify a spatial reference system which has the same definition as the spatial reference system required by the data in the file to be imported. When using Spatial Extender, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, otherwise the SYSGEO.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, for the minimum and maximum coordinate values and the offsets and scale factors applicable for the spatial reference system.

msgcode: -2134

sqlstate: 38S7Y

GSE2200N

The specified SELECT statement for export operations must reference exactly one spatial column. No data can be exported.

Correct the SELECT statement so that it references exactly one spatial column.

msgcode: -2200

sqlstate: 38S90

GSE2201N

The specified SELECT statement for export operations must specify exactly one spatial column. No data can be exported.

Correct the SELECT statement so that it references exactly one spatial column.

msgcode: -2201

sqlstate: 38S91

GSE2202N

The SQL data type data-type for column column-number in the fullselect describing the data to be exported is not supported for shape files. No data can be exported.

Do not specify a column with the unsupported type in the SELECT statement for the export shape operation. You can use the DESCRIBE command to verify the data types for all columns in the result of the SELECT statement.

msgcode: -2202

sqlstate: 38S92

GSE2203N

The data in column column-number has a length of length, which is too long to be exported to a shape file.

Change the length of the column to be shorter than 256 bytes. You can use the cast functions to shorten the length of the column.

msgcode: -2203

sqlstate: 38S93

GSE2204N

The column name column-name exceeds the restriction of 11 bytes for dBASE files. No data is exported.

Specify a column name with 11 or less bytes for the attribute data to be exported to the dBASE file (.dbf).

msgcode: -2204

sqlstate: 38S94

GSE2205W

The database returned a SQL warning sql-warning when the spatial operation fetched the data to be exported. The warning was ignored and the data exported.

Refer to the description of sql-warning. If the warning is not acceptable, correct the source of the warning and export the data again.

msgcode: +2205

sqlstate: 38S95

GSE2206W

The SELECT statement specified for the export did not retrieve any rows. No data was exported.

Specify a SELECT statement that returns at least one row to be exported.

msgcode: +2206

sqlstate: 38S96

GSE2207W

The SELECT statement identified more rows than were exported. This error can occur if an error is encountered during the export and the operation is terminated.

Consult the message file.

msgcode: +2207

sqlstate: 38S97

GSE2208N

In row row-number, a geometry to be exported is associated with a spatial reference system whose numeric identifier is srs-id1. This identifier does not match the numeric identifier srs-id2 of the spatial reference system used for geometries in the preceeding rows. The row row-number was not exported.

Verify that all geometries to be exported have the same spatial reference system identifier. If not, use the ST_Transform method in the SELECT statement to convert all geometries to the same spatial reference system.

msgcode: -2208

sqlstate: 38S98

GSE2209N

The notion of null values is not supported by the data in the file to which you want to export geometries. The geometry to be exported in row row-number is a null value and cannot be exported.

Exclude rows with geometries that are null values from the export by modifying the SELECT statement accordingly.

msgcode: -2209

sqlstate: 38S99

GSE2210N

In row row-number, the geometry that is to be exported uses an invalid spatial reference system. The geometry cannot be exported.

Correct the indicated geometry or exclude the row from the export operation by modifying the SELECT statement accordingly.

msgcode: -2210

sqlstate: 38S9A

GSE2211N

The spatial data to be exported is associated with a spatial reference system whose numeric identifier is srs-id. The coordinate system on which this spatial reference system is based does not match the coordinate system coordsys-def for the file to which the exported data is to be appended. No data was exported.

Append the data to a file which has a matching coordinate system, transform the spatial data to the corresponding coordinate system, or export the data to a separate file.

msgcode: -2211

sqlstate: 38S9B

GSE2212N

The specified SELECT statement for the export operation produces attribute data that does not match the dBASE file (.dbf).

Either correct the SELECT statement, or do not append to the specified dBASE file.

msgcode: -2212

sqlstate: 38S9C

GSE2213W

The geometry to be exported to the file in row row-number is a null value. The row was not exported.

Modify the SELECT statement to exclude geometries that have null values.

msgcode: +2213

sqlstate: 38S9D

GSE2214W

Not enough memory is available to export the geometry in row row-number. The row was not exported, but the exporting operation continued.

Provide more memory, or modify the SELECT statement to exclude the geometry from that row.

msgcode: +2214

sqlstate: 38S9E

GSE2215W

The geometry to be appended to the shape file as number record-number has an shape type geometry-shape-type which does not match the type in the shape file file-shape-type. The geometry cannot be exported to that file.

Convert the geometry to the correct type, or export it to another shape file.

msgcode: +2215

sqlstate: 38S9F

GSE2216N

Before the spatial operation exports geometries to a shape file, it converts them into shape data. This error was returned because the shape data into which a geometry was converted is invalid. The geometry was not exported.

Contact IBM Software Support.

msgcode: -2216

sqlstate: 38S9G

GSE2217N

The column name column-name appears more than once in the output column list. All column names in the list must be unique. No data is exported.

Specify a unique column name in the output column list.

All column names for dBASE files (.dbf) must at most consist of 11 bytes, and all column names for SDEX files must at most consist of 32 bytes.

msgcode: -2217

sqlstate: 38S9I

GSE2299N

Shape file file-name has an invalid file size. Shape files have a file size that is a multiple of 16-bit words. Therefore, their size is always even. The shape file might be corrupt. It cannot be used.

Verify and correct the shape file.

msgcode: -2299

sqlstate: 38S9H

GSE2500N

The header of the SDEX file file-name is invalid. The SDEX file cannot be opened successfully.

Verify and correct the header of the SDEX file.

msgcode: -2500

sqlstate: 38SA0

GSE2501N

The SDEX file file-name contains an invalid data for the coordinate system definition. The SDEX file cannot be opened successfully.

Verify and correct the coordinate system definition stored in the SDEX file.

msgcode: -2501

sqlstate: 38SA1

GSE2502N

The SDEX file file-name contains invalid data for the column definitions. The SDEX file cannot be opened successfully.

Verify and correct the column definitions stored in the SDEX file.

msgcode: -2502

sqlstate: 38SA2

GSE2503N

The SDEX file contains a column whose data type is not supported. The SDEX file could not be imported.

Import only a smaller set of the columns of the SDEX file and omit the column with the unsupported data type.

msgcode: -2503

sqlstate: 38SA3

GSE2504N

The specified column position position must be a value within the valid range. A valid value must greater than 0 (zero) and less than or equal to the column-number.

Specify a valid position.

msgcode: -2504

sqlstate: 38SA4

GSE2505N

The name of column column-name in the SDEX file exceeds the database limit for column names.

Specify a column-name that does not exceed the length limit for column names in the database.

msgcode: -2505

sqlstate: 38SA5

GSE2506N

The name column-name does not identify an existing attribute column in the SDEX file. The operation cannot be completed successfully.

Specify a column name that exists in the SDEX file.

msgcode: -2506

sqlstate: 38SA6

GSE2507N

The SDEX file data type data-type for the attribute column column-name in the SDEX file cannot be mapped to a data type in the database. The SDEX file cannot be imported.

Exclude the column from the column list.

msgcode: -2507

sqlstate: 38SA7

GSE2508N

The spatial operation detected the existence of more than one spatial column in the SDEX file file-name. Only one spatial column is allowed. The file cannot be imported successfully.

Correct the SDEX file so that it contains only one spatial column.

msgcode: -2508

sqlstate: 38SA8

GSE2509N

The record record-number could not be read from the SDEX file file-name.

Depending on the reason code, verify and correct the SDEX file, or resolve the memory shortage.

msgcode: -2509

sqlstate: 38SA9

GSE2600N

The header of the SDEX file file-name could not be written successfully.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -2600

sqlstate: 38SF0

GSE2601N

The coordinate system parameters could not be written to the SDEX file file-name successfully.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -2601

sqlstate: 38SF1

GSE2602N

The column definitions could not be written to the SDEX file file-name successfully.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -2602

sqlstate: 38SF2

GSE2603N

The column name column-name exceeds the restriction of 32 bytes for SDEX files. No data is exported.

Specify a column name with 32 or less bytes for the data to be exported to the SDEX file.

msgcode: -2603

sqlstate: 38SF3

GSE2604N

The SQL data type data-type for column column-number in the fullselect describing the data to be exported is not supported for SDEX files. No data can be exported.

Do not specify a column with the unsupported type in the SELECT statement for the export sde operation. You can use the DESCRIBE command to verify the data types for all columns in the result of the SELECT statement.

msgcode: -2604

sqlstate: 38SF4

GSE2605N

The record record-number could not be written to the SDEX file file-name successfully.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -2605

sqlstate: 38SF5