Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC75510 Status: Closed

IMPORT SHAPE UTILITY FAILS WITH "INTERNAL ERROR"

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Running the 'db2se import_shape' spatial CLP operation or the 
db2gse.st_import_shape stored procedure fails with the error 
GSE0100n "Internal error occurred" if: 
1. there is an error in one of the shapefile input records 
2. no .shx file is provided as part of the shapefile 
3. an exception file is specified 
 
The error occurs because we need to back up to re-read the 
failing record to write it to the exception file and then 
restart processing. 
If the .shx file is available, we position to the correct place 
but if it is not available, the current record number is set 
incorrectly and does not match the current record index 
resulting in the reporting of an error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Spatial Extender using import_shape command              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Running the 'db2se import_shape' spatial CLP operation or    * 
* the                                                          * 
* db2gse.st_import_shape stored procedure fails with the error * 
*                                                              * 
* GSE0100n "Internal error occurred" if:                       * 
*                                                              * 
* 1. there is an error in one of the shapefile input records   * 
*                                                              * 
* 2. no .shx file is provided as part of the shapefile         * 
*                                                              * 
* 3. an exception file is specified                            * 
*                                                              * 
* This failure may also occur if the -restartCount parameter   * 
* is specified and no .shx file exists.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply V9.7 fix pack 5                                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Apply V9.7 fix pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.04.2011
13.12.2011
13.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.