Import ABAP Problem

[Former Member]

Hi All,

Using

VERSION :: ECC6

DB WITH VERSION :: ORACLE 10.2.0.2.0

OS :: WIN 2003 R2.

I'm trying to install ECC 6 IDES Netweaver SR2.It ran smoothly up to Import ABAP Phase.Then all Imports failed and the installation stopped showing an Error code 103. I tried to install this 3 times and stuck with the same error.. Looking forward for a solution to this.

Any Help would be appreciated.

Thanks & regards,

Ravi S

Edited by: Ravi chandra on Aug 5, 2008 4:28 PM

Edited by: Ravi chandra on Aug 5, 2008 4:32 PM

[Former Member · Accepted solution]

Hi Markus,

Thanks for ur wonderful support. It's Just like the problem above even after restarting oracle listener.

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

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

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806234158

This is log of sapclust because i waited to stop till 2 processes are processed.

Thanks & regards,

Ravi S

[markus_doehr2 · Accepted solution]

> DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

>

> DbSl Trace: CONNECT failed with sql error '1034'

>

ORA-01034 means "Oracle not available"

It seems that your database was not started correctly for whatever reason.

Are you sure that the database was completely started and opened?

To verify:

(as user <sid>adm in a cmd.exe):

sqlplus / as sysdba
shutdown abort
startup

Please post what you see there.

Markus

[Former Member · Accepted solution]

Hi,

When entered command sqlplus/as sysdba

connected to Oracle Database 10g EE 10.2.0.2.0 .

When Shutdown abort.

oracle instance shutdown.

>startup

oracle instance started

total system global area 515899392 bytes

Fixed size 1290360

variable size 268439432

database buffers 243269632

Redo Buffers 28999638

Database mounted

database opened

Regards,

Ravi S

[markus_doehr2 · Accepted solution]

This is all really strange... (to me)

One thing we can try is

(as <sid>adm in a cmd.exe):

R3load -testconnect

The problem seems to be, that the R3load processes can't connect to the database. You can also check in the Windows Services that your listener is up and running.

Markus

[Former Member · Accepted solution]

Hi,

This is what i got when entered command r3load -testconnect

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

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

r3load: START OF LOG: 20110807002852

r3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP

r3load: version R7.00/V1.4 [UNICODE]

Compiled Jul 17 2007 01:28:45

r3load -testconnect

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(DB) INFO: disconnected from DB

r3load: job completed

r3load: END OF LOG: 20110807002853

Regards,

Ravi S

[markus_doehr2 · Accepted solution]

This looks really good!

Now try again to repeat the process of importing. If the "-testconnect" works, then the normal connect should work too.

Markus

[Former Member · Accepted solution]

Hi Markus,

Yes It is.Thank u so much for ur patience with me.This really worked out.Thanks again.

By the way 4 Jobs have been completed & still 14 more to go.With 3GB of Ram & 1 Parallel processes How much more time does it take to complete?

Regards,

Ravi S.

Edited by: Ravi chandra on Aug 7, 2008 12:46 AM

[markus_doehr2 · Accepted solution]

> Yes It is.Thank u so much for ur patience with me.This really worked out.Thanks again.

Great to hear it's working now!

> By the way 4 Jobs have been completed & still 14 more to go.With 3GB of Ram & 1 Parallel processes How much more time does it take to complete?

Good question... it depends how fast your harddisks are. Let it run, ERP 6.0 is a rather huge package, it can take some hours. You can check in the task manager in the process overview by sorting for CPU usage the activity. With only one loader process it can take up to 10 - 12 hours (or even longer).

It's possible to change the number of load processes but you would need to repeat all that "-merge_only" stuff again and edit keydb.xml. I would let it run, it will finally come to an end

Markus

[Former Member]

Hi,

When resumed installation I got the following error.

ERROR: 2011-08-06 23:13:44 com.sap.inst.migmon.LoadTask run

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

Process 'G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error' exited with return code 2.

For mode details see 'SAP0000.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: 2011-08-06 23:14:14

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

WARNING: 2011-08-06 23:14:14

14 error(s) during processing of packages.

INFO: 2011-08-06 23:14:14

Import Monitor is stopped.

This is my last attempt & I'm gonna reinstall it again.

Regards,

Ravi S

[markus_doehr2]

> For mode details see 'SAP0000.log' file.

Check that logfile - you're almost there

Markus

[Former Member]

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110806193949

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -ctf I G:\INST6\Exports\EXP5\EXP5\DATA\SAPSSRC.STR C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL SAPSSRC.TSK ORA -l SAPSSRC.log

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: job completed

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806193949

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110806193949

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

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

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806193954

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110806203220

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

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

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806203225

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110806212520

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

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

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806212524

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110806213020

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

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

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806213025

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110806213343

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

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

Compiled Jul 17 2007 01:28:45

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

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

G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110806213348

[markus_doehr2]

Your listener is not running.

Execute (as <sid>adm)

lsnrctl start

in a cmd.exe and retry.

Markus

[Former Member]

Hi Markus,

Thanks for ur help.Do i need to resume installation from sidadm account or from Administrator Account.Because it's being failed again.

Thanks & Regards,

Ravi S

[markus_doehr2]

What "is failed"? Please post the last lines of the log...

Markus

[Former Member]

This is what it shows in Import_monitor file

ERROR: 2011-08-06 21:33:48 com.sap.inst.migmon.LoadTask run

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

Process 'G:\usr\sap\SR1\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error' exited with return code 2.

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

[markus_doehr2]

> For mode details see 'SAPSSRC.log' file.

It says to look in that logfile - what do you see there?

Markus

[Former Member]

Hi All,

I ran the installation again with the suggestions above by putting auto extend on & it ran smoothly.After completing 4,system got shut down due to power supply.After logging in again I went to the import_state_properties & changed - to 0.Is there any thing else should i do.Please let me know the steps to resume installation without starting it all over again.

Thanks & Regards,

Ravi S.

[markus_doehr2]

We need to check first if your database is coming up again.

login as <sid>adm, open a cmd.exe - then try

sqlplus / as sysdba
startup

Is the database correctly mounted and opened?

Markus

[Former Member]

Yes . It is mounted .I got the message oraccle Instance started & buffer sizes.

[markus_doehr2]

Good.

Now we have to step in cmd.exe to your installation directory (c:\program files\sapinst_instdir...) where the .TSK and .TSK.bck files reside.

For each of the packages a .TSK.bck file exists you need to execute (in that directory):

R3load -merge_only <packagename>.TSK

This will merge the content of the .bck file back to the .TSK file.

If this is done you can start sapinst again and select "continue old installation".

Markus

[Former Member]

Hi All,

Thanks for ur replies.I'm in office now & look at these as soon as i reach home.Will Let u know.

Thanks,

Ravi S

[Former Member]

Hai,

Try to extend the TEMP tablespace and if required add the datafiles and make the autoextend 'ON' and check.

Now repeat the Installation once again and check....

Thanks and Regards,

[Former Member]

Dear Ravi,

First stop the sapinst and Please check the import_state_properties file and change all packages from - to 0.

Then check all the packages which are ' - '( as you said all are not done) are having bck files. If there is any .bck files please merge those packages as below:

->open command promt

->move to sapmnt/SID/exe

-> give command R3load - merge_only <packagename>.TSK ( only the packages which is having .bck files)

and restart the SAPINST. Hope it will work,otherwise paste the log file for atleast one package.

Thanks

Kishore

[Former Member]

->open command promt

->move to sapmnt/SID/exe

-> give command R3load - merge_only <packagename>.TSK ( only the packages which is having .bck files)

Hi,

Could u Elaborate this.Where can i find sapmnt?I mean Path..

[markus_doehr2]

"sapmnt" is a share pointing to \usr\sap

I suggest you read the documentation, the filesystem layout is described there.

Markus

[Former Member]

Hi,

Thanks to the replies .I'm Installing it on my home desktop & Installing

from Harddisk & not from DVDs.

This is the error Log.

ERROR 2008-08-05 14:48:37

CJS-30022 Program 'Migration Monitor' exits with error code 103. For

details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2008-08-05 14:48:37

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 .

Import_monitor.java.log:

java version "1.4.2_12"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)

Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)

Import Monitor jobs: running 1, waiting 4, completed 31, failed 0, total 36.

Import Monitor jobs: running 2, waiting 3, completed 31, failed 0, total 36.

Import Monitor jobs: running 3, waiting 2, completed 31, failed 0, total 36.

Loading of 'SAPSSEXC_3' import package: ERROR

Import Monitor jobs: running 2, waiting 2, completed 31, failed 1, total 36.

Import Monitor jobs: running 3, waiting 1, completed 31, failed 1, total 36.

Loading of 'SAPCLUST' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 31, failed 2, total 36.

Loading of 'SAPPOOL' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 31, failed 3, total 36.

Loading of 'SAPSSEXC_4' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 31, failed 4, total 36.

Import_monitor.log:

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

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

E:\usr\sap\EC4\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080106214611

Regards,

Ravi S.

[markus_doehr2]

it seems that your database crashed.

Check you oracle alert log in ...\oracle\saptrace\background\alert<SID>.log

Markus

[Former Member]

Hi,

Try to connect to oracle using SQLPLUS.

Check the services oracleserviceSID.exe, listener is running in services.msc

Thanks,

Shambo

[Former Member]

Hi,

Can u post the exact error message & log files.

Thanks,

Shambo

Edited by: Shambo on Aug 5, 2008 1:14 PM

[Former Member]

Are you running the installation for CD Drive or from a dump on HDD? If running from CD Drive, suggest you dump all the CD's/DVD's on your system and execute the installation from there.

Are you installing as Administrator user ?