cancel
Showing results for 
Search instead for 
Did you mean: 

Error export abap from ms-sql with sapinst

Former Member
0 Kudos

Hi

during a test export off a BW system ( systemcopy with sapinst) one of the 35 steps in the abap export fails with this errormessages

ERROR: 2010-02-01 14:48:23 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPAPPL1_1' export package is interrupted with R3load error.

Process 'E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL1_1.cmd -datacodepage 4103 -l SAPAPPL1_1.log -stop_on_error' exited with return code 2.

For mode details see 'SAPAPPL1_1.log' file.

Standard error output:

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

The sapsystemname is set in the instance profile

from the log

(EXP) ERROR: DbSlPrepare/BegRead failed

rc = 103, table "/BI0/0200000001"

(SQL error 208)

error message returned by DbSl:

Invalid object name '/BI0/0200000001'.

Statement(s) could not be prepared.

(DB) INFO: disconnected from DB

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100201141907

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100201144725

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#7 $ SAP

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]

Compiled Aug 11 2009 00:02:15

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL1_1.cmd -datacodepage 4103 -l SAPAPPL1_1.log -stop_on_error

(DB) INFO: connected to DB

(DB) INFO: Export without hintfile

(GSI) INFO: dbname = "BSSWIN-2CC-S-079 "

(GSI) INFO: vname = "MSSQL "

(GSI) INFO: hostname = "WIN-2CC-S-079 "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "WIN-2CC-S-079"

(GSI) INFO: release = "5.2"

(GSI) INFO: version = "3790 Service Pack 2"

(GSI) INFO: machine = "AMD64 Level 6 (Mod 15 Step 7)"

(GSI) INFO: instno = "INITIAL "

(EXP) ERROR: DbSlPrepare/BegRead failed

rc = 103, table "/BI0/0200000001"

(SQL error 208)

error message returned by DbSl:

Invalid object name '/BI0/0200000001'.

Statement(s) could not be prepared.

(DB) INFO: disconnected from DB

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100201144730

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100201144818

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#7 $ SAP

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]

Compiled Aug 11 2009 00:02:15

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe -e SAPAPPL1_1.cmd -datacodepage 4103 -l SAPAPPL1_1.log -stop_on_error

(DB) INFO: connected to DB

(DB) INFO: Export without hintfile

(GSI) INFO: dbname = "BSSWIN-2CC-S-079 "

(GSI) INFO: vname = "MSSQL "

(GSI) INFO: hostname = "WIN-2CC-S-079 "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "WIN-2CC-S-079"

(GSI) INFO: release = "5.2"

(GSI) INFO: version = "3790 Service Pack 2"

(GSI) INFO: machine = "AMD64 Level 6 (Mod 15 Step 7)"

(GSI) INFO: instno = "INITIAL "

(EXP) ERROR: DbSlPrepare/BegRead failed

rc = 103, table "/BI0/0200000001"

(SQL error 208)

error message returned by DbSl:

Invalid object name '/BI0/0200000001'.

Statement(s) could not be prepared.

(DB) INFO: disconnected from DB

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

E:\usr\sap\BSS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100201144823

BR

Niels R

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hey,

How did you resolve your problem?

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Check SAP Note 846672 - SQL error 208 Invalid object name

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny

we do use sql 2005 and not 2000 as pointed out in the note - the system has got EHP1 a few weeks ago

kernel is 701 patch 55

br

niels

0 Kudos

Hi,

u can drop BI0/02* tables in advance via report SAP_DROP_TMPTABLES.

See SAP Note 449891 for further details.

All temporary table will be generated after fhe import on demand.

cheers, Christoph