This chapter documents messages that DB2 Spatial Extender returns to users. Each message has an identifier. Identifiers that end in the letter E are for error messages; those that end in W are for warnings; and those that end in I are for general information.
| DBA7200E | More than 10 columns are selected as input to a geocoder |
Explanation: Up to 10 columns can be selected as input to a geocoder.
User Reponse: Move column names from the Selected columns box to the Available columns box until the Selected Columns box lists ten names or fewer.
| DBA7201E | The database is not enabled for Spatial Extender operation. |
Explanation: The database must be enabled for Spatial Extender before you can use Spatial Extender.
User Reponse: Right-click the database and select Spatial Extender --> Enable from the menus.
| GSE0000I | The operation is completed successfully. |
| GSE0001E | Spatial Extender could not perform the requested operation ("<operation-name>") under user ID "<user-id>". |
Explanation: You requested this operation under a user ID that does not hold the privilege or authority to perform the operation.
User Reponse: Consult the documentation to find out what the proper authorization is or obtain it from a Spatial Extender administrator.
| GSE0002E | "<value>" is not a valid value for the "<argument-name>" argument. |
Explanation: The value that you entered was incorrect or misspelled.
User Reponse: Consult the documentation or a Spatial Extender administrator to find out what value or range of values you need to specify.
| GSE0003E | Spatial Extender could not perform the requested operation because argument "<argument-name>" was not specified. |
Explanation: You did not specify an argument that is required for this operation.
User Reponse: Specify argument "<argument-name>" with the value that you want; then request the operation again.
| GSE0004W | The argument "<argument-name>" was not evaluated. |
Explanation: The operation you requested does not use argument "<argument-name>".
User Reponse: None required.
| GSE0005E | Spatial Extender could not process your request to create an object named "<object-name>". |
Explanation: Either object "<object-name>" already exists, or you do not have the proper permission to create it. It could be a table, column, trigger, index, file, or other kind of object.
User Reponse: If "<object-name>" is the object that you want, do nothing. Otherwise, specify the name correctly and verify that you have the right permission to create the object.
| GSE0006E | Spatial Extender could not perform the requested operation on an enabled or registered object named "<object-name>". |
Explanation: Object "<object-name>" is already enabled or registered, or it already exists. It could be a layer, index, spatial reference system, coordinate system, geocoder, or other kind of object.
User Reponse: Make sure that object "<object-name>" exists and resubmit your request.
| GSE0007E | Spatial Extender could not perform the requested operation on "<object-name>", an object that has not yet been enabled or registered. |
Explanation: Object "<object-name>" has not been enabled or registered. It could be a layer, index, spatial reference system, spatial coordinate system, geocoder, or other kind of object.
User Reponse: Enable or register object "<object-name>". Then resubmit your request.
| GSE0008E | An unexpected SQL error ("<sql-error-message>") has occurred. |
User Reponse: Look up detailed message associated with SQLCODE in the SQL error message "<sql-error-message>". If necessary, contact your IBM service representative.
| GSE0009E | The requested operation could not be performed on an object named "<object-name>" that already exists. |
Explanation: "<object-name>" already exists in the database or the operating system. It could be a file, table, view, column, index, trigger, or other kind of object.
User Reponse: Make sure that you specify the object correctly when you try to access it. If necessary, delete the object.
| GSE0010E | The requested operation could not be performed on an object named "<object-name>" that might not exist. |
Explanation: "<object-name>" does not exist in the database or in the operating system. It could be a file, table, view, column, index, trigger, file, or other kind of object.
User Reponse: Make sure that you have the right permission to access the object. If you have this permission and the object does not exist, then you need to create it.
| GSE0011E | Spatial Extender could not disable or unregister object "<object-name>". |
Explanation: "<object-name>" is dependent on another object. "<object-name>" could be a spatial reference system, layer, geocoder, or other kind of object.
User Reponse: Consult the documentation to find what kinds of objects "<object-name>" can be dependent on. Then remove the specific object that "<object-name>" is dependent on.
| GSE0012E | Spatial Extender could not process your request because the fully qualified spatial column "<layer-schema.layer-name.layer-column>" is not registered as a table layer. |
Explanation: The fully qualified spatial column "<layer-schema.layer-name.layer-column>" must be registered as a table layer before you can perform certain operations associated with it (for example, enabling its index, enabling a geocoder to populate it in batch mode or to update it automatically).
User Reponse: Make sure that the fully qualified spatial column "<layer-schema.layer-name.layer-column>" is registered as a table layer by checking the DB2GSE.GEOMETRY_COLUMNS view in the Spatial Extender catalog. Also make sure that the table that contains this column also includes valid corresponding attribute columns.
| GSE0013E | The database is not enabled for spatial operations. |
Explanation: The database is not enabled for spatial operations. Therefore, the Spatial Extender catalog does not exist.
User Reponse: Enable the database for spatial operations.
| GSE0014E | The database has already been enabled for spatial operations. |
Explanation: The database has already been enabled for spatial operations.
User Reponse: Verify that the database has been enabled as you expected. If necessary, disable the database.
| GSE0498E | The following error occurred: "<error-message>". |
| GSE0499W | Spatial Extender issued the following warning: "<warning-message>". |
| GSE0500E | The operation mode that you specified ("<operation-mode>") is invalid. |
Explanation: The specified mode is not supported by the operation that you requested.
User Reponse: Consult the documentation to find out what modes are supported by the operation.
| GSE1001E | Spatial Extender was unable to register a view layer that is named "<schema-name.view-name.column-name>" and that is based on spatial column "<schema-name.table-name.column-name>". |
Explanation: The spatial column that you specified ("<schema-name.table-name.column-name>") has not been registered as a table layer.
User Reponse: Register column "<schema-name.table-name.column-name>" as a table layer.
| GSE1002E | Spatial Extender was unable to register a view layer that is named "<schema-name.view-name.column-name>" and that is based on table "<schema-name.table-name>". |
Explanation: The table that you specified ("<schema-name.table-name>") does not underlie view "<schema-name.view-name.column-name>", either directly or indirectly.
User Reponse: Find out what the base table for view "<schema-name.view-name.column-name>" is, and specify this table.
| GSE1003E | Spatial Extender was unable to access a column named "<column-name>" in a table or view named "<schema-name.object-name>". |
Explanation: Table or view "<schema-name.object-name>" does not have a column named "<column-name>".
User Reponse: Check the definition of table or view "<schema-name.object-name>" to find out the proper name of the column that you want.
| GSE1004E | Spatial Extender was unable to register the fully qualified spatial column "<schema-name.table-name.column-name>" as a table layer. |
Explanation: Column "<schema-name.table-name.column-name>" does not have a spatial data type, or is not associated with a base table.
User Reponse: Define a spatial data type for column "<schema-name.table-name.column-name>", or make sure that this column is part of a local base table.
| GSE1005E | The spatial reference system ("<view-layer-spatial-reference-id>") that you specified for a view layer differs from the spatial reference system ("<table-layer-spatial-reference-id>") that is used for this layer's underlying table layer. |
Explanation: A view layer's spatial reference system must be the same as the underlying table layer's spatial reference system.
User Reponse: Specify the underlying table layer's spatial reference system for the view layer.
| GSE1006E | Because "<spatial-reference-id>" is an invalid spatial reference system ID, Spatial Extender was unable to register the layer that you requested. |
Explanation: The spatial reference system that you specified ("<spatial-reference-id>") has not been enabled or registered.
User Reponse: Enable or register the spatial reference system. Then resubmit your request to register the layer.
| GSE1007E | An SQL error (SQLSTATE "<sqlstate>") might have occurred when Spatial Extender tried unsuccessfully to add a spatial column ("<column-name>") to table "<schema-name.table-name>". |
User Reponse: Look up the message associated with SQLSTATE "<sqlstate>".
| GSE1008E | DB2 Spatial Extender was unable to register a view layer"<layer-schema.layer-name.layer-column>" because the spatial data type "<layer-column-type>" of the view layer does not match the spatial data type "<geo-column-type>" of the underlying table layer "<geo-schema.geo-name.geo-column>". |
Explanation: The spatial data type of a view layer "<layer-schema.layer-name.layer-column>" must match the spatial data type of the layer's underlying table layer "<geo-schema.geo-name.geo-column>". The inconsistency between these two data types causes ambiguity when spatial data is processed.
User Reponse: Make sure that the spatial data types of the view layer and its underlying table layer are the same.
| GSE1020E | "<'spatial-reference-id>" is an invalid spatial reference system ID. |
Explanation: A spatial reference system with an identifier of "<'spatial-reference-id>" has not been enabled.
User Reponse: Make sure that the specified spatial reference has been enabled.
| GSE1021E | Spatial Extender could not enable spatial reference system "<spatial-reference-id>" because the corresponding spatial coordinate system ID "<spatial-coordinate-id>" is invalid. |
Explanation: A coordinate system with an identifier of "<spatial-coordinate-id>" is not defined in the Spatial Extender catalog.
User Reponse: Verify the coordinate system identifier "<spatial-coordinate-id>" by checking the DB2GSE.COORD_REF_SYS view in the Spatial Extender catalog.
| GSE1030E | Because "<schema-name.table-name>" is not a base table, Spatial Extender could not enable a geocoder for it. |
Explanation: The object that contains the source data that you want geocoded must be a base table.
User Reponse: Be sure that the columns that contain the source data that you want geocoded are part of a base table.
| GSE1031E | Spatial Extender could not enable geocoder "<geocoder-id>" to operate automatically in create mode for layer "<layer-schema.layer-name.layer-column>". |
Explanation: Possible explanations are:
User Reponse: If the geocoder has been temporarily invalidated, enable it to operate automatically in "Recreate" mode.
| GSE1032E | Spatial Extender could not enable geocoder "<geocoder-id>" to operate automatically in recreate mode for layer "<layer-schema.layer-name.layer-column>". |
Explanation: Possible explanations are:
User Reponse: If the geocoder was previously disabled in drop mode, or if it was never defined for this layer, enable it to operate automatically in "Create" mode.
| GSE1033E | An SQL error occurred when Spatial Extender tried to add triggers to a table that contains the column for layer "<layer-schema.layer-name.layer-column>" (SQLSTATE "<sqlstate>"). |
Explanation: The purpose of the triggers is to maintain data integrity between the attribute columns that the geocoder's input comes from and the spatial column that its output goes into. The SQL error occurred when DB2 tried to create these triggers.
User Reponse: Look up the message associated with SQLSTATE "<sqlstate>".
| GSE1034E | Spatial Extender could not disable geocoder "<geocoder-id>" in drop mode for layer "<layer-schema.layer-name.layer-column>". |
Explanation: Possible explanations are:
User Reponse: Determine the state of the geocoder before you tried to disable it. For example, was it registered? was it enabled? Then decide whether it needs to be disabled in drop mode. For example, if it was never enabled, there would be no need to disable it at all.
| GSE1035E | Spatial Extender could not disable geocoder "<geocoder-id>" in invalidate mode for layer "<layer-schema.layer-name.layer-column>". |
Explanation: Possible explanations are:
User Reponse: Determine the state of the geocoder before you tried to disable it. For example, was it registered? Was it enabled? Then decide whether it needs to be disabled in invalidate mode. For example, if it was already disabled in invalidate mode, there would be no need to disable it in this mode a second time.
| GSE1036E | An SQL error occurred when Spatial Extender tried to drop triggers from a table that contains the column for layer "<layer-schema.layer-name.layer-column>" (SQLSTATE "<sqlstate>"). |
Explanation: The triggers were created to maintain data integrity between the attribute columns that the geocoder's input comes from and the spatial column that its output goes into. The SQL error occurred when DB2 tried to drop these triggers.
User Reponse: Look up the message associated with SQLSTATE "<sqlstate>".
| GSE1037E | Spatial Extender could not geocode source data for table layer "<layer-schema.layer-name.layer-column>", possibly because an incorrect value "<number-of-attributes>" was assigned to the argument that specifies how many attribute columns are to provide source data for this layer. |
Explanation: The number of attribute columns associated with this layer was specified incorrectly, or the name of one or more of these columns was specified incorrectly.
User Reponse: Make sure that this layer is registered with the correct number and names of associated attribute columns, or verify the correctness of input and output data for the geocoder.
| GSE1038E | An SQL error occurred when Spatial Extender tried to geocode source data for table layer "<layer-schema.layer-name.layer-column>" in batch mode (SQLSTATE "<sqlstate>"). |
User Reponse:
| GSE1050E | The grid size that you specified ("<grid-size>") is invalid for the first grid level. |
Explanation: You specified zero or a negative number as the grid size for the first grid level.
User Reponse: Specify a positive number as the grid size.
| GSE1051E | The grid size that you specified ("<grid-size>") is invalid for the second and third grid levels. |
Explanation: You specified a negative number as the grid size for the second or the third grid level.
User Reponse: Specify zero or a positive number as the grid size.
| GSE1052E | An SQL error occurred when the Spatial Extender tried to create spatial index "<index-schema.index-column>" for a table layer "<layer-schema.layer-name.layer-column>" (SQLSTATE "<sqlstate>"). |
User Reponse:
| GSE1500I | Source record "<record-number>" was successfully geocoded. |
Explanation: A record containing attribute data was successfully geocoded.
| GSE1501W | Source record "<record-number>" was not geocoded. |
Explanation: The precision level was too high.
User Reponse: Geocode with a lower precision level.
| GSE1502W | Source record "<record-number>" was not found. |
User Reponse: Determine whether the record exists in the database.
| GSE2001E | The specified transfer file ("<filename>") is not valid. |
User Reponse: Verify that the specified file is an SDE transfer file, and that the pathname is properly specified.
| GSE2002E | The supplied SQL WHERE clause ("<SQL-where-clause>") is not valid. |
User Reponse: Check the WHERE clause for proper SQL syntax, spelling errors, and invalid column names.
| GSE2003E | The supplied shape value is not legal. |
User Reponse: Check to be sure that the supplied shape matches the specified type of the spatial column. If the types match, or are compatible, then the form of the geometry is illegal. Check for overlapping polygons, single point arcs, etc.
| GSE2004E | The transfer file schema is incompatible with the schema of the specified layer. |
User Reponse: Check to be sure that the schema and layer names are properly specified. If the schemas do not match, load the data as a new table and resolve the schema differences.
| GSE2005E | The transfer file geometry type is incompatible with the geometry type of the specified layer. |
User Reponse: Check to be sure that the schema and layer names are properly specified.
| GSE2006E | An I/O error for a file named "<filename>" has occurred. |
User Reponse: Verify that the file exists, that you have the appropriate access to the file, and that the file is not in use by another user.
| GSE2007E | An attribute conversion error has occurred. |
User Reponse: Check to be sure that all attribute types in the table are supported - for example, BLOB data is not supported in shape files. Also check for out-of-range data values, or illegal data values such as bad dates.
| GSE2008E | The import/export function has run out of memory. |
User Reponse: Verify that you adequate memory available.