Error at copying database using dumps via loadercli: error -25364

[Former Member]

I would like to copy an entire user to another instance and tried it this way:

@source database:

loadercli -n source_db -u dba,dba -d the_user

dbextract catalog outstream file 'C:\temp\20081011.catalog' records data outstream file 'C:\temp\20081011.data' records

and then:

loadercli -n destination -u dba,dba -d the_user

dbload catalog instream file 'C:\temp\20081011.catalog' records

dbload data instream file 'C:\temp\20081011.data' records

The import of the catalog went ok, but on importing the data I was given:

ERR -25364

Names of table to import (ORDERS) and currently processing table in data file (AKTENZEICHEN) do not match

FYI: source database is 7.5

destination database is 7.6

loadercli binary is 7.6

What's the problem? I can't guess the meaning of this message. Seems like loadercli expected a different order of the tables, but the file was produced by loadercli itself a few minutes before, so I don't think I could do anything about it.

Could you please give me a hint what may be wrong?

TIA,

Alex

BTW:

This is the written loader log file:

-

---

START Log File -

---

// M Starting protocol at 2008011100130941

// *

// M START 20080111 00130941

// *

SET

// *

// M START 20080111 00130941

// *

USE USER "DBA" * SCHEMA DBA SERVERDB "APORTAL" ON uny-int-sap

// *

// M USER: 'DBA' on DB: 'APORTAL' ISOLATION LEVEL: 3

// *

// M START 20080111 00130946

// *

drop user aportal

// *

// M START 20080111 00130949

// *

dbload catalog instream file 'C:\temp\aportal\aportal_aportal_ipms_20080110.catalog' records

// *

// M Execute PACKAGE to transform CATALOG

/ *

// M Import PACKAGE x'010000008DED97FDCC0E0000A47E0000AE47319E49FCD3F2'

// *

// M Number of TABLES transformed : 56

// *

// M Export PACKAGE x'010000008DED97FDCC0E0000A47E0000AE47319E49FCD3F2'

// *

// M START 20080111 00130955

// *

dbload data instream file 'C:\temp\aportal\aportal_aportal_ipms_20080110.data' records

// *

// M Import PACKAGE x'0200000093ED97FDCC0E0000A47E0000AE47319E49FCD3F2'

// *

// M Execute PACKAGE to transform DATA

// *

// M Number of TABLES to transform: 56

// *

// E -25364: Names of table to import (ORDERS) and currently processing table in data file (AKTENZEICHEN) do not match

-

---

END Log File -

---

[Former Member · Accepted solution]

Hello,

could you please check if the paramter COLUMNCOMPRESSION and USEUNICODECOLUMNCOMPRESSION are set to NO in your target database.

Regards

Wolfgang

[Former Member · Accepted solution]

The parameter COLUMNCOMPRESSION is set to YES on the target database. Is this bad?

I seem to be not able to find the other parameter you mentioned, USEUNICODECOLUMNCOMPRESSION. How can I list all parameters of the database?

Alex

[Former Member · Accepted solution]

Hello,

the parameter USEUNICODECOLUMNCOMPRESSION should be in the extended section of the parameter list.

Regards

Wolfgang

[Former Member · Accepted solution]

The parameter USEUNICODECOLUMNCOMPRESSION is on none of the sections (General, Extended, Support), I only find (if this has something to do with the issue)

_UNICODE = YES

Regards,

Alex

[Former Member · Accepted solution]

Hello,

when you migrate tha data with the loader you should set the parameter COLUMNCOMPRESSION to NO.

After the migration you should reset the parameter to YES. New tables will use this parameter when data is stored.

Regards

Wolfgang

[Former Member · Accepted solution]

Hi Wolfgang,

I tried to:

- set COLUMNCOMPRESSION to NO (on the target database)

- set database to ADMIN mode and back to ONLINE in order for the parameter change to take effect

- import via loadercli

Unfortunately, this results in the same error:

ERR -25364 Names of table to import (ORDERS) and currently processing table in data file (AKTENZEICHEN) do not match

Regards,

Alex

[Former Member · Accepted solution]

Hi,

it seems that relation between catalog and data loader files is messed.

For a deeper analysis a colleague from the loader team will take over.

Sorry for inconvenience

Wolfgang

[Former Member · Accepted solution]

hi ,

can you please send me your email adress to hans-georg.bumes@sap.com ?

i would like to post you a workaround and test it before publishing it in this forum.

regards

hans-georg

[Former Member · Accepted solution]

hi alex,

the import error is a consequence of the error

E -25010: SQL error -2003 = Output columns too long (error position: 48)

that raises exporting the table ORDERS. this error will be fixed in a future release

of the loader.

meanwhile the following workaround does the job.

-

---

export sourcedb----

---

1.

loadercli -d <sourcedb> -u dba,dba

export db

catalog outstream file 'C:\temp\20080114.catalog' ddl

data outstream file 'C:\temp\20080114.data' pages

-

---

import targetdb----

---

1.drop catalogobjects imported by 20081011.catalog

2. dbmcli -d <targetdb> -u <dba>,<dbapassword>

param_put columncompression no

3.

loadercli -d <targetdb> -u dba,dba

import db

catalog instream file 'C:\temp\20080114.catalog' ddl

data instream file 'C:\temp\20080114.data' pages

-

---

regards

hgb

[Former Member]

This did the job!

Thank you very much!