Loader Internal Error

[Former Member]

Hi!

I'm trying to import a large table dump (including several LOBs), but the loader gives the following error message:

loadercli>ERR -25801
Internal error [05, 876, -25870]; contact technical support

The message initially occured with MaxDB 7.6.00. I upgraded to 7.6.03, but this did not help.

Any pointers or help is greatly appreciated. Thank you very much in advance!

Matthias <matthias@wuttke.eu>

Query:

import table abda_fdmv_object data instream 'abda_fdmv_object.csv' lob instream dosierung 'abda_fdmv_object_dosierung.data' utf8 lob instream hinweise 'abda_fdmv_object_hinweise.data' utf8 lob instream indikationen 'abda_fdmv_object_indikationen.data' utf8 lob instream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' utf8 lob instream nebenwirkungen 'abda_fdmv_object_nebenwirkungen.data' utf8

Kernel version:

sqlcli=> select * from version
| OPERATINGSYSTEM                                                  | PROCESSORTYPE
        | ADDRESSINGMODE         | ID                                       | MAJORVERSION        | MINORVERSION        | CORR
ECTIONLEVEL         | BUILD      | KERNELVARIANT |
| ---------------------------------------------------------------- | ---------------------------------------------------------
------- | ---------------------- | ---------------------------------------- | ------------------- | ------------------- | ----
------------------- | ---------- | ------------- |
| Linux 2.6.16.46-0.12-bigsmp #1 SMP Thu May 17 14:00:09 UTC 2007  | i686
        |                     32 | Kernel    7.6.03   Build 015-121-173-107 |                   7 |                   6 |
                  3 |         15 | fast          |
1 row selected (1 msec)

Excerpt from loader log:

// M    Loader    7.6.03   Build 015-121-173-107
// *
// M    Loader    instance started at drugt for database MAXDB1
// *
// M    Starting protocol at 2008030800210810
// *
// M    START   20080308        00210810
// *
SET
// *
// M    START   20080308        00210810
// *
USE USER "PHOENIX" * SCHEMA PHOENIX SERVERDB "MAXDB1" ON localhost
// *
// M    USER:   'PHOENIX'       on DB:  'MAXDB1'        ISOLATION LEVEL: 3
// *
// M    START   20080308        00210810
// *
import table abda_fdmv_object data instream 'abda_fdmv_object.csv'  lob instream dosierung 'abda_fdmv_object_dosierung.data' u
tf8 lob instream hinweise 'abda_fdmv_object_hinweise.data' utf8 lob instream indikationen 'abda_fdmv_object_indikationen.data'
 utf8 lob instream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' utf8 lob instream nebenwirkungen 'abda_fdmv_o
bject_nebenwirkungen.data' utf8
// *
// M    Import    PACKAGE x'010000002AF2D247012D000079B94C53010C0AC0FFFFFFFF'
// *
// M    Execute   PACKAGE  to transform  DATA
// *
// M    Number of TABLES   to transform: 0
// *
// E -25801:    Internal error [05, 876, -25870]; contact technical support
// M    Last transaction committed at input record 16
// *
// M    Number of ROWS     inserted    : 16, number of RECORDS rejected : 1
// *
// M    Number of NULL values inserted: 25 (NULL representation in data file is '?                   ')
// *

[Former Member]

The update the last night was successful, and now I can transfer dump files in UCS2 encoding between the servers, too. As far as I am concerned, the problem has been solved (worked around) for me. The UTF8 loader code seems to be buggy, though. Thank you a lot for your help, Steffen!

Best regards, Matthias

[Former Member]

Hi Steffen,

thanks a lot for your quick reply that was quite helpful.

I can recreate the table from an external data source so that I can dump and re-import it again. It still does not work with UTF8 encoding, but works (as you suggested) with UCS2. As I may choose the file encoding, now I have got a working dump.

We have got a test database server with MaxDB 7.6.03 and a production server with MaxDB 7.6.00. I tried all these things on our test server, but I am afraid the UCS2 dump from the test server (7.6.03) cannot be imported into the production server (7.6.00). Hopefully, this problem will be fixed by updating the latter one (which I hope will be able to do this night).

Here are the dumps from the loader log file.

1) Table import (external source) was successful:

sqlcli=> select count(*) from abda_fdmv_object
| EXPRESSION1        |
| ------------------ |
|               7448 |
1 row selected (0 msec)

2) Export the table (UTF8)

// M    Loader    7.6.03   Build 015-121-173-107
// *
// M    Loader    instance started at drugt for database MAXDB1
// *
// M    Starting protocol at 2008031100170502
// *
// M    START   20080311        00170502
// *
SET
// *
// M    START   20080311        00170502
// *
USE USER "PHOENIX" * SCHEMA PHOENIX SERVERDB "MAXDB1" ON localhost
// *
// M    USER:   'PHOENIX'       on DB:  'MAXDB1'        ISOLATION LEVEL: 3
// *
// M    START   20080311        00170502
// *
export table abda_fdmv_object data outstream 'abda_fdmv_object.csv'  lob outstream dosierung 
'abda_fdmv_object_dosierung.data' utf8 lob outstream hinweise 'abda_fdmv_object_hinweise.data' utf8 lob outstream indikationen 
'abda_fdmv_object_indikationen.data' utf8 lob outstream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' utf8 lob outstream nebenwirkungen 'abda_fdmv_object_nebenwirkungen.data' utf8
// *
// M    Import    PACKAGE x'01000000AEADD647C0590000D228F94F010C0AC0FFFFFFFF'
// *
// M    Execute   PACKAGE  to transform  DATA
// *
// M    Number of TABLES   to transform: 1
// *
// M    Number of RECORDS  transformed : 7448,  where 0 ROWS were transformed with errors.
// *
// M    Export    PACKAGE x'01000000AEADD647C0590000D228F94F010C0AC0FFFFFFFF'

This worked very well, 7448 rows exported without problems.

# cat abda_fdmv_object.csv | wc -l
7448

3) Import the dump:

// M    Loader    7.6.03   Build 015-121-173-107
// *
// M    Loader    instance started at drugt for database MAXDB1
// *
// M    Starting protocol at 2008031100171335
// *
// M    START   20080311        00171335
// *
SET
// *
// M    START   20080311        00171335
// *
USE USER "PHOENIX" * SCHEMA PHOENIX SERVERDB "MAXDB1" ON localhost
// *
// M    USER:   'PHOENIX'       on DB:  'MAXDB1'        ISOLATION LEVEL: 3
// *
// M    START   20080311        00171335
// *
import table abda_fdmv_object data instream 'abda_fdmv_object.csv'  lob instream dosierung 'abda_fdmv_object_dosierung.data' utf8 lob instream hinweise 'abda_fdmv_object_hinweise.data' utf8 lob instream indikationen 
'abda_fdmv_object_indikationen.data' utf8 lob instream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' utf8 lob instream nebenwirkungen 'abda_fdmv_object_nebenwirkungen.data' utf8
// *
// M    Import    PACKAGE x'01000000AFAFD647B75C00000589997C010C0AC0FFFFFFFF'
// *
// M    Execute   PACKAGE  to transform  DATA
// *
// M    Number of TABLES   to transform: 0
// *
// E -25801:    Internal error [05, 876, -25870]; contact technical support
// M    Last transaction committed at input record 3324
// *
// M    Number of ROWS     inserted    : 3324, number of RECORDS rejected : 1
// *
// M    Number of NULL values inserted: 2618 (NULL representation in data file is '?                   ')

This obviously did not work as expected.

sqlcli=> select count(*) from abda_fdmv_object
| EXPRESSION1        |
| ------------------ |
|               3324 |
1 row selected (0 msec)

4) UCS2 Export/Import

Works as expected:

// M    Loader    7.6.03   Build 015-121-173-107
// *
// M    Loader    instance started at drugt for database MAXDB1
// *
// M    Starting protocol at 2008031100172419
// *
// M    START   20080311        00172419
// *
SET
// *
// M    START   20080311        00172419
// *
USE USER "PHOENIX" * SCHEMA PHOENIX SERVERDB "MAXDB1" ON localhost
// *
// M    USER:   'PHOENIX'       on DB:  'MAXDB1'        ISOLATION LEVEL: 3
// *
// M    START   20080311        00172419
// *
export table abda_fdmv_object data outstream 'abda_fdmv_object.csv'  lob outstream dosierung 'abda_fdmv_object_dosierung.data'
 ucs2 lob outstream hinweise 'abda_fdmv_object_hinweise.data' ucs2 lob outstream indikationen 
'abda_fdmv_object_indikationen.data' ucs2 lob outstream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' ucs2 lob outstream nebenwirkungen 'abda_
fdmv_object_nebenwirkungen.data' ucs2
// *
// M    Import    PACKAGE x'0100000033B2D647C55D0000AAFE7822010C0AC0FFFFFFFF'
// *
// M    Execute   PACKAGE  to transform  DATA
// *
// M    Number of TABLES   to transform: 1
// *
// M    Number of RECORDS  transformed : 7448,  where 0 ROWS were transformed with errors.
// *
// M    Export    PACKAGE x'0100000033B2D647C55D0000AAFE7822010C0AC0FFFFFFFF'

Reimport

// M    Loader    7.6.03   Build 015-121-173-107
// *
// M    Loader    instance started at drugt for database MAXDB1
// *
// M    Starting protocol at 2008031100173042
// *
// M    START   20080311        00173042
// *
SET
// *
// M    START   20080311        00173042
// *
USE USER "PHOENIX" * SCHEMA PHOENIX SERVERDB "MAXDB1" ON localhost
// *
// M    USER:   'PHOENIX'       on DB:  'MAXDB1'        ISOLATION LEVEL: 3
// *
// M    START   20080311        00173042
// *
import table abda_fdmv_object data instream 'abda_fdmv_object.csv'  lob instream dosierung 
'abda_fdmv_object_dosierung.data' ucs2 lob instream hinweise 'abda_fdmv_object_hinweise.data' ucs2 lob instream indikationen 'abda_fdmv_object_indikationen.data' ucs2 lob instream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' ucs2 lob instream nebenwirkungen 'abda_fdmv_object_nebenwirkungen.data' ucs2
// *
// M    Import    PACKAGE x'01000000B2B3D647DB6000005CFF2144010C0AC0FFFFFFFF'
// *
// M    Execute   PACKAGE  to transform  DATA
// *
// M    Number of TABLES   to transform: 0
// *
// M    Last transaction committed at input record 7448
// *
// M    Number of ROWS     inserted    : 7448, number of RECORDS rejected : 0
// *
// M    Number of NULL values inserted: 5423 (NULL representation in data file is '?                   ')
// *
// M    Export    PACKAGE x'01000000B2B3D647DB6000005CFF2144010C0AC0FFFFFFFF'

5) Now trying to import the UCS2 dump on the other 7.6.00 server:

// M    Loader    7.6.00   Build 037-121-149-748
// *
// M    Loader    instance started at drugp for database MAXDB1
// *
// M    Starting protocol at 2008031100175130
// *
// M    START   20080311        00175130
// *
SET
// *
// M    START   20080311        00175130
// *
USE USER "PHOENIX" * SCHEMA PHOENIX SERVERDB "MAXDB1" ON localhost
// *
// M    USER:   'PHOENIX'       on DB:  'MAXDB1'        ISOLATION LEVEL: 3
// *
// M    START   20080311        00175130
// *
import table abda_fdmv_object data instream 'abda_fdmv_object.csv'  lob instream dosierung 'abda_fdmv_object_dosierung.data' ucs2 lob instream hinweise 'abda_fdmv_object_hinweise.data' ucs2 lob instream indikationen 'abda_fdmv_object_indikationen.data' ucs2 lob instream kontraindikationen 'abda_fdmv_object_kontraindikationen.data' ucs2 lob instream nebenwirkungen 'abda_fdmv_object_nebenwirkungen.data' ucs2
// *
// M    Import    PACKAGE x'0100000092B8D6472831000081FCDE64010B0AC0FFFFFFFF'
// *
// M    Execute   PACKAGE  to transform  DATA
// *
// M    Number of TABLES   to transform: 0
// *
// M    Error at record 1 in infile.
// E -25010:    SQL error -8046 = Conversion from UNICODE impossible: 3F3F (error position: 1)
// M    Number of ROWS     inserted    : 0, number of RECORDS rejected : 1
// *
// M    Number of NULL values inserted: 11 (NULL representation in data file is '?                   ')
// *

Any further help is greatly appreciated!

Best regards,

Matthias

Edited by: Matthias Wuttke on Mar 11, 2008 6:46 PM

[steffen_schildberg]

Hi Matthias,

it looks as if the data has not correctly been exported. Did you check the log file of the export? Any errors? How did you do the Export?

The error occurs when converting the UTF8 data to UCS2 where the UTF8 source data is incomplete. Is there a possibility to store the data upon

export UCS2 encoded? Why forcing an additional conversion step during Import?

If you can't export again is there a possibility I could check your data?

Best regards,

Steffen