cancel
Showing results for 
Search instead for 
Did you mean: 

SAP IDES BW Installation - Infamous ABAP Import error

Former Member
0 Kudos

Hi there, i've been fighting with this phase for 4 days now. Fisrt i had like 7 jobs failed - solved it. I Reinstalled the OS, the JSDK and started again - 3 jobs failed!

I logged in as a SIDADM. and started my SAP DB trhough the services.exe and ran the installation again - 1 job failed!

So, now, i have this 1 job failed, 16 are OK and 1 waiting and i'm stuck. So, please look at my ERROR log file and may be you have a clue?!

Thanx

INFO: 2009-01-20 11:55:53

Import Monitor is started.

CONFIG: 2009-01-20 11:55:53

Application options:

dbCodepage=4103

dbType=ADA

extFiles=no

importDirs=E:\51032416_1\EXP1;E:\51032416_2\EXP2;E:\51032416_2\EXP3

installDir=C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS

jobNum=3

loadArgs= -nolog -c 0

monitorTimeout=30

orderBy=

r3loadExe=E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2009-01-20 11:55:53

List of packages with table structure: 'SAP0000'.

CONFIG: 2009-01-20 11:55:53

List of packages with views: 'SAPVIEW'.

TRACE: 2009-01-20 11:55:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is started.

INFO: 2009-01-20 11:55:53 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is successfully completed.

Primary key creation: before load.

Index creation: after load.

INFO: 2009-01-20 11:55:53

Data codepage 4103 is determined using TOC file 'E:\51032416_1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.

TRACE: 2009-01-20 11:55:53 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is started.

TRACE: 2009-01-20 11:55:53 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL1' import package into database:

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 0

ERROR: 2009-01-20 11:55:53 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is interrupted with R3load error.

Process 'E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 0' exited with return code 2.

For mode details see 'SAPAPPL1.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

WARNING: 2009-01-20 11:56:23

Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2009-01-20 11:56:23

1 error(s) during processing of packages.

INFO: 2009-01-20 11:56:23

Import Monitor is stopped.

-


I went to SAPAPPL1.log

And that's what it said:

(DB) INFO: connected to DB

(DB) INFO: The MaxDB logwriter is switched off#20090120115440

(TSK) ERROR: file C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted

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

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090120115441

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090120115553

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jul 17 2007 01:28:45

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 0

(DB) INFO: connected to DB

(DB) INFO: The MaxDB logwriter is switched off#20090120115553

(TSK) ERROR: file C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted

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

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090120115553

-


I looked through the SAPAPPL1.TSK file looking for an "error" status in order to correct it manually to "ok"

As it was suggestet by people in this forum, but there is no single entry with "error" status.

So, could anyone help me?

Thank you.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

May be i should delete SAPAPPL1.TSK.bck file??

what do you think?

markus_doehr2
Active Contributor
0 Kudos

> May be i should delete SAPAPPL1.TSK.bck file??

No!

Do not delete it.

You have to merge the content of it with the original file - you may miss tables if you delete it.

Execute as <sid>adm in the installation directory

R3load -merge_only SAPAPPL1.TSK

Then restart the import.

Markus

Former Member
0 Kudos

I didn't delete it. I just removed it from the SAP installation directory and restarted the installation, but once again no luck

Markus, i did as you told me and restarted the installation and it seems like the process is OK. It's been like an hour already and it gives no error. So, thank you a lot. At least this error is over

Points assigned

markus_doehr2
Active Contributor
0 Kudos

> I didn't delete it. I just removed it from the SAP installation directory and restarted the installation, but once again no luck

This is the same than deleting it.

> Markus, i did as you told me and restarted the installation and it seems like the process is OK. It's been like an hour already and it gives no error. So, thank you a lot. At least this error is over

You can check the activity of the database by logging in as <sid>adm (or execute "runas /user:<sid>adm cmd.exe") and doing

x_cons <SID> sh ac 1

Then you will see if the database is still working.

Markus

Former Member
0 Kudos

Once again the same SAPAPPL1 error

WARNING 2009-01-20 15:08:11

Execution of the command "C:\j2sdk1.4.2_09\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ADA -importDirs E:\51032416_1\EXP1;E:\51032416_2\EXP2;E:\51032416_2\EXP3 -installDir "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_09"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)Import Monitor jobs: running 1, waiting 1, completed 16, failed 0, total 18.Loading of 'SAPAPPL1' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 16, failed 1, total 18.

ERROR 2009-01-20 15:08:11

CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2009-01-20 15:08:11

FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .

I looked through the import_monitor:

Import Monitor is started.

CONFIG: 2009-01-20 15:07:11

Application options:

dbCodepage=4103

dbType=ADA

extFiles=no

importDirs=E:\51032416_1\EXP1;E:\51032416_2\EXP2;E:\51032416_2\EXP3

installDir=C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS

jobNum=3

loadArgs= -nolog -c 0

monitorTimeout=30

orderBy=

r3loadExe=E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2009-01-20 15:07:11

List of packages with table structure: 'SAP0000'.

CONFIG: 2009-01-20 15:07:11

List of packages with views: 'SAPVIEW'.

TRACE: 2009-01-20 15:07:11 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is started.

INFO: 2009-01-20 15:07:11 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is successfully completed.

Primary key creation: before load.

Index creation: after load.

INFO: 2009-01-20 15:07:11

Data codepage 4103 is determined using TOC file 'E:\51032416_1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.

TRACE: 2009-01-20 15:07:11 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is started.

TRACE: 2009-01-20 15:07:11 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL1' import package into database:

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 0

ERROR: 2009-01-20 15:08:08 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is interrupted with R3load error.

Process 'E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 0' exited with return code 2.

For mode details see 'SAPAPPL1.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

WARNING: 2009-01-20 15:08:11

Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2009-01-20 15:08:11

1 error(s) during processing of packages.

INFO: 2009-01-20 15:08:11

Import Monitor is stopped.

-


And that's the SAPAPPL1.log

-


E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090120150711

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jul 17 2007 01:28:45

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 0

(DB) INFO: connected to DB

(DB) INFO: The MaxDB logwriter is switched off#20090120150713

(DB) ERROR: DDL statement failed

(DROP INDEX "/BI0/D0PP_C023~010" ON "/BI0/D0PP_C023")

DbSlExecute: rc = 103

(SQL error -4011)

error message returned by DbSl:

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) INFO: /BI0/D0PP_C02P~010 created#20090120150729

(DB) INFO: /BI0/D0PP_C02U~010 created#20090120150730

(DB) INFO: /BI0/D0PP_C031~010 created#20090120150730

(DB) INFO: /BI0/D0PP_C03P~010 created#20090120150730

(DB) INFO: /BI0/D0PP_C041~010 created#20090120150731

(DB) INFO: /BI0/D0PP_C043~010 created#20090120150731

(DB) INFO: /BI0/D0PP_C04P~010 created#20090120150731

(DB) INFO: /BI0/D0PP_C04U~010 created#20090120150731

(DB) INFO: /BI0/D0PP_C051~010 created#20090120150732

(DB) INFO: /BI0/D0PP_C053~010 created#20090120150732

(DB) INFO: /BI0/D0PP_C054~010 created#20090120150732

(DB) INFO: /BI0/D0PP_C05P~010 created#20090120150732

(DB) INFO: /BI0/D0PP_C05U~010 created#20090120150733

(DB) INFO: /BI0/D0PP_C061~010 created#20090120150733

(DB) INFO: /BI0/D0PP_C063~010 created#20090120150733

(DB) INFO: /BI0/D0PP_C064~010 created#20090120150734

(DB) INFO: /BI0/D0PP_C06P~010 created#20090120150734

(DB) INFO: /BI0/D0PP_C06U~010 created#20090120150734

(DB) INFO: /BI0/D0PP_C071~010 created#20090120150734

(DB) INFO: /BI0/D0PP_C07P~010 created#20090120150735

(DB) INFO: /BI0/D0PP_C07U~010 created#20090120150735

(DB) INFO: /BI0/D0PP_C081~010 created#20090120150735

(DB) INFO: /BI0/D0PP_C082~010 created#20090120150735

(DB) INFO: /BI0/D0PP_C083~010 created#20090120150735

(DB) INFO: /BI0/D0PP_C08P~010 created#20090120150735

(DB) INFO: /BI0/D0PP_C08T~010 created#20090120150736

(DB) INFO: /BI0/D0PP_C08U~010 created#20090120150736

(DB) INFO: /BI0/D0PT_C012~010 created#20090120150738

(DB) INFO: /BI0/D0PT_C013~010 created#20090120150738

(DB) INFO: /BI0/D0PT_C016~010 created#20090120150738

(DB) INFO: /BI0/D0PT_C017~010 created#20090120150738

(DB) INFO: /BI0/D0PT_C018~010 created#20090120150739

(DB) INFO: /BI0/D0PT_C019~010 created#20090120150739

(DB) INFO: /BI0/D0PT_C01A~010 created#20090120150740

(DB) INFO: /BI0/D0PT_C01P~010 created#20090120150740

(DB) INFO: /BI0/D0PT_C01T~010 created#20090120150741

(DB) INFO: /BI0/D0PT_C01U~010 created#20090120150741

(DB) INFO: /BI0/D0PUR_C011~01 created#20090120150741

(DB) INFO: /BI0/D0PUR_C013~01 created#20090120150741

(DB) INFO: /BI0/D0PUR_C015~01 created#20090120150742

(DB) INFO: /BI0/D0PUR_C016~01 created#20090120150742

(DB) INFO: /BI0/D0PUR_C017~01 created#20090120150742

(DB) INFO: /BI0/D0PUR_C018~01 created#20090120150742

(DB) INFO: /BI0/D0PUR_C019~01 created#20090120150743

(DB) INFO: /BI0/D0PUR_C01B~01 created#20090120150743

(DB) INFO: /BI0/D0PUR_C01P~01 created#20090120150744

(DB) INFO: /BI0/D0PUR_C01U~01 created#20090120150744

(DB) INFO: /BI0/D0PUR_C021~01 created#20090120150744

(DB) INFO: /BI0/D0PUR_C022~01 created#20090120150744

(DB) INFO: /BI0/D0PUR_C024~01 created#20090120150746

(DB) INFO: /BI0/D0PUR_C025~01 created#20090120150746

(DB) INFO: /BI0/D0PUR_C026~01 created#20090120150746

(DB) INFO: /BI0/D0PUR_C027~01 created#20090120150747

(DB) INFO: /BI0/D0PUR_C028~01 created#20090120150747

(DB) INFO: /BI0/D0PUR_C02P~01 created#20090120150747

(DB) INFO: /BI0/D0PUR_C02T~01 created#20090120150748

(DB) INFO: /BI0/D0PY_C022~010 created#20090120150748

(DB) INFO: /BI0/D0PY_C023~010 created#20090120150748

(DB) INFO: /BI0/D0PY_C026~010 created#20090120150749

(DB) INFO: /BI0/D0PY_C02P~010 created#20090120150749

(DB) INFO: /BI0/D0PY_C02T~010 created#20090120150749

(DB) INFO: /BI0/D0PY_C02U~010 created#20090120150749

(DB) INFO: /BI0/D0SD_C021~010 created#20090120150750

(DB) INFO: /BI0/D0SD_C022~010 created#20090120150750

(DB) INFO: /BI0/D0SD_C023~010 created#20090120150751

(DB) INFO: /BI0/D0SD_C024~010 created#20090120150751

(DB) INFO: /BI0/D0SD_C025~010 created#20090120150752

(DB) INFO: /BI0/D0SD_C026~010 created#20090120150752

(DB) INFO: /BI0/D0SD_C02P~010 created#20090120150752

(DB) INFO: /BI0/D0SD_C02U~010 created#20090120150752

(DB) INFO: /BI0/D0SD_C032~010 created#20090120150753

(DB) INFO: /BI0/D0SD_C035~010 created#20090120150753

(DB) INFO: /BI0/D0SD_C036~010 created#20090120150754

(DB) INFO: /BI0/D0SD_C037~010 created#20090120150754

(DB) INFO: /BI0/D0SD_C038~010 created#20090120150754

(DB) INFO: /BI0/D0SD_C03P~010 created#20090120150754

(DB) INFO: /BI0/D0SD_C03T~010 created#20090120150755

(DB) INFO: /BI0/D0SD_C03U~010 created#20090120150756

(DB) INFO: /BI0/D0TRCM_C01201 created#20090120150756

(DB) INFO: /BI0/D0TRCM_C01P01 created#20090120150757

(DB) INFO: /BI0/D0TRCM_C01U01 created#20090120150757

(DB) INFO: /BI0/D0WBS_C021~01 created#20090120150758

(DB) INFO: /BI0/D0WBS_C022~01 created#20090120150758

(DB) INFO: /BI0/D0WBS_C023~01 created#20090120150759

(DB) INFO: /BI0/D0WBS_C02P~01 created#20090120150759

(DB) INFO: /BI0/D0WBS_C02T~01 created#20090120150801

(DB) INFO: /BI0/D0WBS_C02U~01 created#20090120150801

(DB) INFO: /BI0/F0WBS_C02~010 created#20090120150802

(DB) INFO: /BI0/F0WBS_C02~020 created#20090120150802

(DB) INFO: /BI0/F0WBS_C02~030 created#20090120150802

(DB) INFO: /BI0/F0WBS_C02~040 created#20090120150802

(DB) INFO: /BI0/F0WBS_C02~050 created#20090120150802

(DB) INFO: /BI0/F0WBS_C02~060 created#20090120150803

(DB) INFO: /BI0/F0WBS_C02~P created#20090120150803

(DB) INFO: /BIC/0CAD000005~Z0 created#20090120150803

(DB) INFO: /BIC/0CAD000006~Z0 created#20090120150803

(DB) INFO: /BIC/0CAD000007~Z0 created#20090120150803

(DB) INFO: /BIC/0CAD000013~Z0 created#20090120150803

(DB) INFO: /BIC/0CAD000014~Z0 created#20090120150804

(DB) INFO: /BIC/0CAD000015~Z0 created#20090120150804

(DB) INFO: /BIC/0CAD000018~Z0 created#20090120150805

(DB) INFO: /BIC/0CAD000019~Z0 created#20090120150805

(DB) INFO: /BIC/0CAD000021~Z0 created#20090120150806

(DB) INFO: /BIC/0CAD000022~Z0 created#20090120150807

(DB) INFO: /BIC/0CAD000023~Z0 created#20090120150807

(DB) INFO: /BIC/0CAD000035~Z0 created#20090120150807

(DB) INFO: /BIC/0CAD000036~Z0 created#20090120150808

ERROR : Execute for create index /BIC/DBZX_PCA7~010 on /BIC/DBZX_PCA7 failed (dbrc=102).

(SQL error -955)

error message returned by DbSl:

SQL-Statement: CREATE INDEX "/BIC/DBZX_PCA7~010" ON "/BIC/DBZX_PCA7" ( "SID_0VERSION" , "SID_0VTYPE" , "SID_0VERSION_RA" )

(DB) INFO: disconnected from DB

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

E:\usr\sap\IAM\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090120150808

-


I'm running this installation on Windows 2003 Server 32b with UNICODE option, could that be the problem?

thanx.

When all the points are assigned, i'll open another thread...

markus_doehr2
Active Contributor
0 Kudos

> ERROR : Execute for create index /BIC/DBZX_PCA7~010 on /BIC/DBZX_PCA7 failed (dbrc=102).

> (SQL error -955)

> error message returned by DbSl:

> SQL-Statement: CREATE INDEX "/BIC/DBZX_PCA7~010" ON "/BIC/DBZX_PCA7" ( "SID_0VERSION" , "SID_0VTYPE" , "SID_0VERSION_RA" )

> (DB) INFO: disconnected from DB

-955 is "duplicate name" - this can be a result of having moved away the original .TSK file and retrying.

> I'm running this installation on Windows 2003 Server 32b with UNICODE option, could that be the problem?

I would not install a Unicode system on 32bit - especially not on new installation. You may not be able to activate all the functions you need with 32bit.

If this is a server purchased in the last two years the CPUs are very likely capable of running Windows 64bit.

Markus

Answers (4)

Answers (4)

Former Member
0 Kudos

..

Former Member
0 Kudos

So, for now forgeting about 32 or 64 bit and unicode. the error you've seen is due to the removed TSK file?

Well, i guess i'll have to start it al over again from the scratch...

thanx

Former Member
0 Kudos

I'm installing it on a 3 years laptop.

Do you think i should restart all the installation from the beginning and do not check the UNICODE option?

markus_doehr2
Active Contributor
0 Kudos

> I'm installing it on a 3 years laptop.

oh...

> Do you think i should restart all the installation from the beginning and do not check the UNICODE option?

Well - it depends what you plan to do with the system.

If you install BI-Java too, then you MUST use Unicode.

Markus

Former Member
0 Kudos

..