cancel
Showing results for 
Search instead for 
Did you mean: 

Content Server : IMPORT USER problem

Former Member
0 Kudos

Hi,

I exported my content server content by loadercli on a Linux system to import it in a sun solaris system.

I followed intstructions in "[SAP Note 962019 - System copy of MaxDB Content Server Storage|https://service.sap.com/sap/support/notes/962019]" with the heterogeneous copy.

The export was well created by the sql script :

EXPORT USER
catalog outstream file '/depot/SAPR3.cat'
data outstream file '/depot/SAPR3.data' PAGES
package outstream file '/depot/SAPR3.pack'

and the command line : .

/loadercli -d DCS -u SAPR3,SAP -n localhost -b /depot/export_content_server.sql

But my import does not work with the command line :

# ./loadercli -u SAPR3,SAP -d RCS -b /oracle/RBW/sapdata3/export_content_server/import.sql
Loader Server Protocol File:    '/sapdb/data/wrk/loader.prt'

User SAPR3 connected to database RCS on local host.
IMPORT USER
CATALOG INSTREAM FILE '/oracle/RBW/sapdata3/export_content_server/SAPR3.cat'
DATA INSTREAM FILE '/oracle/RBW/sapdata3/export_content_server/SAPR3.data' PAGES
PACKAGE OUTSTREAM FILE '/oracle/RBW/sapdata3/export_content_server/SAPR3.pack' CSV
Error during execution
-->-25010
SQL error -3005 = Invalid SQL statement (error position: 1)

Defined maximum number of errors (1) reached


1 error(s) during execution of command file '/oracle/RBW/sapdata3/export_content_server/import.sql'.
---> See log file(s) for more information.


Some error(s) occurred running command.
---> See log file(s) for more information.

What can I do to resolve my problem ?

Regards.

Accepted Solutions (1)

Accepted Solutions (1)

Ayax
Participant
0 Kudos

From SAP Note 962019:

Important: You must use the same binary-compatible loader for the entire export an import; for example, you cannot start the export with a Windows 'little endian' loader and then carry out the import with a loader under AIX 'big endian'. For the entire process (export and import) you must only use the loader of the source system or only the loader of the target system. Using a combination of both will later cause a termination due to missing binary compatibility.

Did you use the same loader?

Regards,

Ayax

Former Member
0 Kudos

Hi,

Tahnks for this answer.

I see the problem, but I cannot execute a Linux loader on a solaris system, right?

Regards.

Former Member
0 Kudos

HI,

I found the lxrun solution, I try to make it work.

Lxrun should let me be able to run a linux binary on solaris.

Regards.

Former Member
0 Kudos

Hi,

Lxrun was a bad idea, it runs on 32bits architechtures only.

I installed a Linux to run loadercli from it.

It looked great until I get this error ça I don't understand :

# ./loadercli.linux -u SAPR3,SAP -d RCS -n 172.21.96.11 -b import.sql
Loader protocol: '/root/sdb/rapiaghrcs1/loader/log/loader.log'
Loader packages: '/root/sdb/rapiaghrcs1/loader/packages'

User SAPR3 connected to database RCS schema SAPR3 on 172.21.96.11.
IMPORT USER
        CATALOG INSTREAM FILE '/export/SAPR3.cat'
        DATA INsTREAM FILE '/export/SAPR3.data' PAGES
Error during execution
-->-25801
Internal error [vls28_TLTable.cpp, 3035, -25801]; contact technical support
---
Total number of tables (definition) imported: 3
Total number of tables (data)       imported: 0 (excluded: 0, failed: 0)

Defined maximum number of errors (1) reached


1 error(s) while processing command file 'import.sql'.
---> See Loader log file for more information.

Here is my import.sql :

IMPORT USER
        CATALOG INSTREAM FILE '/export/SAPR3.cat'
        DATA INsTREAM FILE '/export/SAPR3.data' PAGES

That was my export.sql :

EXPORT USER
catalog outstream file '/depot/SAPR3.cat'
data outstream file '/depot/SAPR3.data' PAGES
package outstream file '/depot/SAPR3.pack'

It generated the files below :

-rw-r--r--  1 root root         856 Jan 22 11:37 SAPR3.cat
-rw-r--r--  1 root root         802 Jan 23 01:40 SAPR3.data0000
-rw-r--r--  1 root root 64482108416 Jan 23 01:29 SAPR3.data0001
-rw-r--r--  1 root root   453903360 Jan 23 01:40 SAPR3.data0002
-rw-r--r--  1 root root        2296 Jan 23 01:40 SAPR3.pack

Does anyone know about this error ?

Regards.

Answers (1)

Answers (1)

Former Member
0 Kudos

HI,

In fact I had a bad loadercli on sun solaris.

I replaced it, and I have this error :

# ./loadercli -u SAPR3,SAP -d RCS -b /oracle/RBW/sapdata3/export_content_server/import.sql
Loader protocol: '//sdb/sapibdm1/loader/log/loader.log'
Loader packages: '//sdb/sapibdm1/loader/packages'

User SAPR3 connected to database RCS schema SAPR3 on local host.
IMPORT USER
        CATALOG INSTREAM FILE '/oracle/RBW/sapdata3/export_content_server/SAPR3.cat'
        DATA INsTREAM FILE '/oracle/RBW/sapdata3/export_content_server/SAPR3.data' PAGES
Error during execution
-->-25348
Different byte swap of source and target machine; Loader must run on same processor memory architecture machine for EXPORT and IMPORT in PAGE Format.
---
Total number of tables (definition) imported: 3
Total number of tables (data)       imported: 0 (excluded: 0, failed: 0)

Defined maximum number of errors (1) reached


1 error(s) while processing command file '/oracle/RBW/sapdata3/export_content_server/import.sql'.
---> See Loader log file for more information.

I followed a SAP Note and it didn't work. I don't know what to do anymore.

Regards.