How to interpret Db2 Spatial Extender messages

Understanding how Db2 Spatial Extender messages are structured and how to obtain additional information for them can help you determine whether the spatial operation that you requested completed successfully or resulted in an error.

You can work with Db2 Spatial Extender by using any of the following interfaces:

Db2 Spatial Extender stored procedures
Db2 Spatial Extender functions
Db2 Spatial Extender Command Line Processor (CLP)

All these interfaces return Db2 Spatial Extender messages.

The following table explains each part of this sample Db2 Spatial Extender message text:


GSE0000I: The operation was completed successfully.

Table 1. The parts of the Db2 Spatial Extender message text
Message text part	Description
GSE	The message identifier. All Db2 Spatial Extender messages begin with the three-letter prefix GSE.
0000	The message number. A four digit number that ranges from 0000 through 9999.
I	The message type. A single letter that indicates the severity of message: C Critical error messages N Non-critical error messages W Warning messages I Informational messages
The operation was completed successfully.	The message explanation.

The explanation that appears in the message text is the brief explanation. You can retrieve additional information about the message that includes the detailed explanation and suggestions to avoid or correct the problem through the SYSPROC.GET_MESSAGE procedure, the Db2 CLP, or the message reference for Spatial Extender.

To display this additional information from the Db2 CLP:

Open an operating system command prompt.
Enter the Db2 help command with the message identifier and message number to display additional information about the message. For example:
```
db2 "? GSEnnnn"
```
where nnnn is the message number.

You can type the GSE message identifier and letter indicating the message type in uppercase or lowercase. Typing db2 "? GSE0000I" will yield the same result as typing db2 "? gse0000i".

You can omit the letter after the message number when you type the command. For example, typing db2 "? GSE0000" will yield the same result as typing db2 "? GSE0000I".

Suppose the message code is GSE4107N. When you type db2 "? GSE4107N" at the command prompt, the following information is displayed:


GSE4107N Grid size value "<grid-size>" is not valid where it is used. 

Explanation: The specified grid size "<grid-size>" is not valid.

	One of the following invalid specifications was made when the grid index 
	was created with the CREATE INDEX statement:

	 -  A number less than 0 (zero) was specified as the grid size for the 
	    first, second, or third grid level.

	 -  0 (zero) was specified as the grid size for the first grid level.

	 -  The grid size specified for the second grid level is less than the grid
	    size of the first grid level but it is not 0 (zero). 

	 -  The grid size specified for the third grid level is less than the grid 
	    size of the second grid level but it is not 0 (zero). 

	 -  The grid size specified for the third grid level is greater than 0 (zero)
	    but the grid size specified for the second grid level is 0 (zero).

User Response: Specify a valid value for the grid size.

msgcode: -4107

sqlstate: 38SC7

If the information is too long to display on a single screen and your operating system supports the more executable program and pipes, type this command:


db2 "? GSEnnnn" | more

Using the more program will force the display to pause after each screen of data so that you can read the information.