Skip to main content

Search

Welcome to Tibero GTS!

Tibero6 to Tibero7 GIS column tbimport hang issue document type failure resolution

Document Type | TroubleShooting 

Field | Migration

Applicable Product Version | 7FS02PS

Document Number | TMITS001

 

Issue

When performing tbexport/tbimport from Tibero 6 with a specific patch to Tibero 7, no particular error appears in sys.log, but callstack and out files are generated and the system enters a hang state. 
Especially when tbimporting from Tibero 6 to Tibero 7 with GIS columns included, the operation does not proceed and hangs, followed by callstack generation.
 
-- Parameters: username=sys password=xxxx sid=susong port=5826 fromuser=ICSIGNAL touser=TIBERO table=SOITSCNCTEDGE ignore=y file=test.dmp log=test.log

-- Import character set: UTF-8

-- FROM_USER ICSIGNAL TO_USER TIBERO: Wed Nov 09 08:46:14 KST 2022

-- Import national character set: UTF-16

--   importing from schema: "ICSIGNAL" to schema "TIBERO"

--     importing table "SOITSCNCTEDGE"

-- [FAILED] ("SOITSCNCTEDGE") TBR-10030: JDBC-10030:Invalid WKB geometry data.

-- [FAILED] ("SOITSCNCTEDGE") TBR-10030: JDBC-10030:Invalid WKB geometry data.

............(Repeated same error)

-- [FAILED] ("SOITSCNCTEDGE") TBR-10030: JDBC-10030:Invalid WKB geometry data.

--   importing index "PK_SOITSCNCTEDGE"

--   importing constraint "PK_SOITSCNCTEDGE"

--   importing constraint "_ICSIGNAL_CON385200161"

--   importing constraint "_ICSIGNAL_CON385300747"

--   importing constraint "_ICSIGNAL_CON385400322"

--   importing constraint "_ICSIGNAL_CON385500891"

--   importing constraint "_ICSIGNAL_CON385600448"

--   importing constraint "_ICSIGNAL_CON385700019"

--   importing constraint "_ICSIGNAL_CON385800568"

--   importing constraint "_ICSIGNAL_CON385900136"

--   Import completed with error: Wed Nov 09 08:47:51 KST 2022

 

Cause

This can occur if the geometry storage structure was changed to provide the geography feature in a specific patch (227917). 
 

Case 1. Tibero 6 (patch 227917 applied) - Tibero 7

During tbimport and tbexport, the geom_from_wkb function (a function to verify Geometry data integrity) should not be called, but it was called, so contact Tmax Tibero for resolution.
 

Case 2. Tibero 6 (patch 227917 not applied) - Tibero 7

Calling the geom_from_wkb function is normal, and there is abnormal data stored in Tibero 6, so the customer needs to check the data.
 

Solutions

  1. When performing tbexport, use the geom_asbytes parameter with Y to transfer.
  2. After applying the patch, modify or verify data using the ST_IsValidGeomFormat and ST_IsValidWKB functions. (Applied patch: 294359a)

 

Method to convert WKB format data suitable for Tibero 7 (Tibero 6 format)

SQL> update TBL set geom=st_geomfromwkb(geom) where st_isvalidwkb(geom)=1;

 

Method to check data not supported in Tibero 7 and not in WKB format (Tibero 6 format)

 SQL> select * from TBL where ST_IsValidGeomFormat(geom) = 0 and ST_IsValidWKB(geom) = 0;
Note
After migration, confirm whether the operating application recognizes the change in Geometry data format and collects data accordingly.
Caution
Apply the patch through technical support provided by TmaxTibero.

 

 

 

Related to