Installation Error: ImportABAP Phase

[Former Member]

Hello,

I am installing Nerweaver 2004s SR2 in my Desktop, I got following error in middle.

OS:windows 2003 server

DB: Oracle 10g

SAP: Netweaver 2004s SR2

When Installation is going on ( Phase No: 19, ImportABAP) unexpected power got shutdown my system . Again i started the installation " Old Intsallation" i got the following error:

Error in SAPInst:

ERROR 2009-08-12 17:03: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-08-12 17:03: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 .

Error in 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 14, failed 0, total 19.

Import Monitor jobs: running 2, waiting 3, completed 14, failed 0, total 19.

Import Monitor jobs: running 3, waiting 2, completed 14, failed 0, total 19.

Import Monitor jobs: running 4, waiting 1, completed 14, failed 0, total 19.

Loading of 'SAPAPPL1' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 14, failed 2, total 19.

Loading of 'SAPSSEXC' import package: ERROR

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 14, failed 3, total 19.

Import Monitor jobs: running 1, waiting 1, completed 14, failed 3, total 19.

Loading of 'SAPAPPL2' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 14, failed 4, total 19.

Error in import_monitor.log

ERROR: 2009-08-12 16:12:37 com.sap.inst.migmon.LoadTask run

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

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

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

Please give me the Solution for this.

Regards,

Sanjeeva

*<subjectmodified>*_

Edited by: Juan Reyes on Aug 12, 2009 1:22 PM

[Former Member · Accepted solution]

Hi Sanjeeva,

Has your problem solved?

Thanks

[Former Member · Accepted solution]

Hello,

What does SAPAPPL0.log say.

Regards.

Ruchit Khushu

[Former Member · Accepted solution]

Hi,

My installation stopped over there.

SAPAPPL0.log History:

:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -stop_on_error

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

DbSl Trace: CONNECT failed with sql error '1034'

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

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

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

DbSl Trace: CONNECT failed with sql error '1034'

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

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

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

D:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090826054453

D:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090826061014

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

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

Compiled Sep 1 2006 00:38:35

D:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -stop_on_error

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

DbSl Trace: CONNECT failed with sql error '1034'

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

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

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

DbSl Trace: CONNECT failed with sql error '1034'

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

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

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

D:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090826061016

Can you fix my issue?

Thanks in advance

Regards,

sanjeeva

[Former Member · Accepted solution]

Hi,

This is log in Import_java.log.

I have gone through some threads in sdn.They are saying problem with MIGMON.

ERROR: 2009-08-26 05:44:53 com.sap.inst.migmon.LoadTask run

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

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

For mode details see 'SAPSSEXC.log' file.

Standard error output:

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

Solving my problem will be appreciated .

Regards,

sanjeeva

[Former Member · Accepted solution]

1034 means oracle is not available.

Check you database is up and SGA allocation is adequate.

Proably you might need to increase the sessions and process parameter in the database.

[Former Member · Accepted solution]

Hi Vijay,

Can you tell me steps to do that process.

I'm using 2003 server. At first i allocated 3500-4500 to DB drive after that i have changed.

Regards,

sanjeeva

[Former Member · Accepted solution]

Hello Sanjeeva,

After shutdown occurred did you restart the listener and subsequently the database in mount state and opened it ? If not please do it.

Regards.

Ruchit.

[former_member185031 · Accepted solution]

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

Check this file also.

Regards,

Subhash

[Former Member · Accepted solution]

Please check your export DVD ,then are corupt

Thanks

Rishi Abrol

[Former Member · Accepted solution]

hi sanjeeva,

in netwaever installation if systems shuts down abnormally or by mistake if u close it that corresponding job gets cancelled it will not allow you to proceed further there is only one solution unisntall and start the installation from the begining ,this is the only way if any job gets cancelled forcefully ,you have to be very care full in import abap phase .

Regards

Zia

[Former Member]

What I understood.... while import ABAP stage power shutdown took place and now you are resuming installation by choosing old installation option.. RIGHT?

Basically SAPINST now can not connect to your database because once system got bounced your listerner is also stopped. So start Listener, Try to open database with followings

1. lsnrctl start

2. sqlplus "/as sysdba"

startup

See if database gets started then nothing like that and you can resume your installation. And if Database does not get started, means You have to rectifiy errors. Please post error msgs you are getting during opening of database.

[praveenvanam]

Please also do check whether the database is connected to your system.

Regards,

-- Vanam

[praveenvanam]

Hi Sanjeeva,

According to the problem,

It clearly states that there is a problem with Open Catalog Interface (OCI), which is a log that ensures the free communication between SAPR/3 system and external catalog.

( For more details , See : http://help.sap.com/saphelp_nw04/helpdata/en/5d/0eba5fa0084247acbb0c04cede18e8/content.htm. ) and database connection failure, which could be due to absence of

ora_dba member.

So , Try out the below steps ,accordingly:

1) Go to My Computer - Manage- Local User and Groups- Users- RIght Click on SAP Service <SID>-Properties-Memberof-Add-Advanced-Findnow-Double click on ora_dba.

Do the Same steps as above for <SIID>adm too.

Regards,

--Vanam

[Former Member]

Hi,

Problem is with abnormal shutdown during installation.

Regards,

Muralidhar

[Former Member]

Hi Sanjeev,

This problem caused by an abnormal shutdown. The installation process records action in some log files and step by step performs next activity.

Process creates BCK files and final status is updated in files. It seems that system could not update the last status because of power failure.

I would advise to install the Database Instance from scratch.

Thanks

[JPReyes]

This is a discussion forum, you can't demand immediate answers or people to "give" you solutions.

Read the "Rules of Engagement"

What have you done so far to troobleshoot?... have you read the logs?

Juan