cancel
Showing results for 
Search instead for 
Did you mean: 

I am getting installation error in ides system please help some one.

Former Member
0 Kudos

Dear all,

i am getting installation error in ides system. please help me.

IMPORT MONITORING LOGS:

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

Process 'D:\usr\sap\EID\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

ERROR: 2009-05-19 13:43:11 com.sap.inst.migmon.LoadTask run

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

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

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

ERROR: 2009-05-19 13:43:11 com.sap.inst.migmon.LoadTask run

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

Process 'D:\usr\sap\EID\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.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

WARNING: 2009-05-19 13:43:40

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

WARNING: 2009-05-19 13:43:40

3 error(s) during processing of packages.

INFO: 2009-05-19 13:43:40

Import Monitor is stopped.

IMPORT_MONITORING.JAVA.LOGS:

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 3, completed 15, failed 0, total 19.

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

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

Loading of 'SAPSSRC' import package: ERROR

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

Loading of 'SAPSDIC' import package: ERROR

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

Loading of 'SAPSSEXC' import package: ERROR

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

SAPSSRC:

(DB) ERROR: DbSlErrorMsg rc = 99

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

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090519104927

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090519134311

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

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

Compiled Jul 17 2007 01:28:45

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.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

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

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090519134311

SAPSSEXC:

(DB) ERROR: DbSlErrorMsg rc = 99

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

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090519104927

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090519134311

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

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

Compiled Jul 17 2007 01:28:45

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.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

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

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090519134311

SAPSDIC:

(DB) ERROR: DbSlErrorMsg rc = 99

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

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090519104927

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090519134311

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

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

Compiled Jul 17 2007 01:28:45

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.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

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

D:\usr\sap\EID\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090519134311

Regards:

ramu

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Raman,

Please check your host and services file and ensure that you have maintained the proper entry there.

Please also check the output of R3trans -d. In case of error, please provide the trans.log output.

With Regards,

Saurabh

Former Member
0 Kudos
CONNECT failed with sql error '1034' (DB) ERROR:

Is your database oracle? Check the connectivity.

Former Member
0 Kudos

your installation is stuck in the Abap import phase.

this error mainly occur whe the cd are corrupt or you dont have enough ram.

JPReyes
Active Contributor
0 Kudos

Read,

SAP Note 491174 - Composite SAP note for ORA-01034

Regards

Juan