We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-basis] Error while installing ECC6.0 sr2(R3load failed)

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by rao_raj
on Mar 12 at 11:18 AM
Mark this reply as helpfulMark as helpful
Hi David,

I already tried to restart installation & used option drop database & create new but still getting same error mentioned on sapinst.log file above.`

please advice.

Regards,

---------------Original Message---------------
From: sriharshalv
Sent: Tuesday, January 12, 2010 9:40 AM
Subject: Error while installing ECC6.0 sr2(R3load failed)

> hi guys,
> we are installing ECC6.0 IDES stand alone system on win2003 and oracle10.2.0.2
> i am getting error at step " import ABAP "
> i am sending u log file
> import_monitor.log
> CONFIG: 2010-01-12 05:35:52
> List of packages with views: 'SAPVIEW'.
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.imp.ImportStandardTask preCreate
> Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDL ORA.TPL' template file is started.
> INFO: 2010-01-12 05:35:52 com.sap.inst.migmon.imp.ImportStandardTask preCreate
> Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDL ORA.TPL' template file is successfully completed.
> Primary key creation: after load.
> Index creation: after load.
> INFO: 2010-01-12 05:35:52
> Data codepage 4103 is determined using TOC file 'Z:\SAPECC6\Export1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPAPPL1' import package is started.
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPSSEXC' import package is started.
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPAPPL0' import package is started.
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask processPackage
> Loading of 'SAPAPPL1' import package into database:
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask processPackage
> Loading of 'SAPSSEXC' import package into database:
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
> TRACE: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask processPackage
> Loading of 'SAPAPPL0' import package into database:
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -stop_on_error
> ERROR: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPAPPL0' import package is interrupted with R3load error.
> Process 'E:\usr\sap\JPD\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
> ERROR: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPSSEXC' import package is interrupted with R3load error.
> Process 'E:\usr\sap\JPD\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
> ERROR: 2010-01-12 05:35:52 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPAPPL1' import package is interrupted with R3load error.
> Process 'E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error' 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
> TRACE: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPAPPL2' import package is started.
> TRACE: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPSDIC' import package is started.
> TRACE: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPCLUST' import package is started.
> TRACE: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask processPackage
> Loading of 'SAPAPPL2' import package into database:
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error
> TRACE: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask processPackage
> Loading of 'SAPSDIC' import package into database:
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
> TRACE: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask processPackage
> Loading of 'SAPCLUST' import package into database:
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
> ERROR: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPAPPL2' import package is interrupted with R3load error.
> Process 'E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error' exited with return code 2.
> For mode details see 'SAPAPPL2.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: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPCLUST' import package is interrupted with R3load error.
> Process 'E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error' exited with return code 2.
> For mode details see 'SAPCLUST.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: 2010-01-12 05:36:22 com.sap.inst.migmon.LoadTask run
> Loading of 'SAPSDIC' import package is interrupted with R3load error.
> Process 'E:\usr\sap\JPD\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
> WARNING: 2010-01-12 05:36:52
> Cannot start import of packages with views because not all import packages with tables are loaded successfully.
> WARNING: 2010-01-12 05:36:52
> 6 error(s) during processing of packages.
> INFO: 2010-01-12 05:36:52
> Import Monitor is stopped.
> import_monitor.java.log
> java version "1.4.2_13"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
> Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
> Import Monitor jobs: running 1, waiting 6, completed 12, failed 0, total 19.
> Import Monitor jobs: running 2, waiting 5, completed 12, failed 0, total 19.
> Import Monitor jobs: running 3, waiting 4, completed 12, failed 0, total 19.
> Loading of 'SAPAPPL0' import package: ERROR
> Import Monitor jobs: running 2, waiting 4, completed 12, failed 1, total 19.
> Loading of 'SAPSSEXC' import package: ERROR
> Import Monitor jobs: running 0, waiting 4, completed 12, failed 3, total 19.
> Loading of 'SAPAPPL1' import package: ERROR
> Import Monitor jobs: running 0, waiting 4, completed 12, failed 3, total 19.
> Import Monitor jobs: running 1, waiting 3, completed 12, failed 3, total 19.
> Import Monitor jobs: running 2, waiting 2, completed 12, failed 3, total 19.
> Import Monitor jobs: running 3, waiting 1, completed 12, failed 3, total 19.
> Loading of 'SAPAPPL2' import package: ERROR
> Import Monitor jobs: running 2, waiting 1, completed 12, failed 4, total 19.
> Loading of 'SAPCLUST' import package: ERROR
> Import Monitor jobs: running 1, waiting 1, completed 12, failed 5, total 19.
> Loading of 'SAPSDIC' import package: ERROR
> Import Monitor jobs: running 0, waiting 1, completed 12, failed 6, total 19.
> SAPAPPL0.log
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20100112053552
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
> Compiled Sep 1 2006 00:38:35
> E:\usr\sap\JPD\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
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100112053552
> SAPAPPL1.log
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20100112053552
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
> Compiled Sep 1 2006 00:38:35
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.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
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100112053552
> SAPAPPL2.log
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20100112053622
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
> Compiled Sep 1 2006 00:38:35
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.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
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
> E:\usr\sap\JPD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100112053622
__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251

0 comments:

Post a Comment

T r a n s l a t e to your language