ECC 6.0 installation error

[Former Member]

Hi experts,

while installing ecc 6.0 i m facing problem during Import ABAP phase ..

Can any help ..pls..

Error is. :

java version "1.5.0_22"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)

Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode)

Import Monitor jobs: running 1, waiting 2, completed 34, failed 0, total 37.

Import Monitor jobs: running 2, waiting 1, completed 34, failed 0, total 37.

Loading of 'SAPSSEXC_1' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 34, failed 1, total 37.

Loading of 'SAPSSEXC_2' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 34, failed 2, total 37.

thanks ,

vinisha.

[Former Member · Accepted solution]

Hi,

For ECC 6.0, JDK should be 1.4.2_2x, not 1.5.0_22.

Also, you need to check the import logs created during the installation in the SAPInst directory:

If windows: ..\program files\sapinst_instdir\..\..\..\

If unix: /tmp/sapinst_instdir/../../../

In these folders check the last update logs for more info about the error.

Regards,

Srikishan

[Former Member · Accepted solution]

Hello , Thanks srikishan for a quick response ..

the last update log file is.. ::_

INFO: 2011-09-15 16:42:56

Import Monitor is started.

CONFIG: 2011-09-15 16:42:56

Application options:

dbCodepage=4103

dbType=ADA

extFiles=no

importDirs=C:\temp\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP1;C:\temp\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP2;C:\temp\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP3

installDir=C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL

jobNum=3

loadArgs=-nolog -c 50000 -force_repeat -loadprocedure dbsl

monitorTimeout=30

orderBy=

r3loadExe=C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2011-09-15 16:42:56

List of packages with table structure: 'SAP0000'.

CONFIG: 2011-09-15 16:42:56

List of packages with views: 'SAPVIEW'.

TRACE: 2011-09-15 16:42:56 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\DDLADA.TPL' template file is started.

INFO: 2011-09-15 16:42:56 com.sap.inst.migmon.imp.ImportStandardTask preCreate

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

Primary key creation: before load.

Index creation: after load.

INFO: 2011-09-15 16:42:56

Data codepage 4103 is determined using TOC file 'C:\temp\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP1\DATA\ATAB.TOC' for package 'ATAB'.

TRACE: 2011-09-15 16:42:56 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC_1' import package is started.

TRACE: 2011-09-15 16:42:56 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC_2' import package is started.

TRACE: 2011-09-15 16:42:56 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPSSEXC_2' import package into database:

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_2.cmd -dbcodepage 4103 -l SAPSSEXC_2.log -nolog -c 50000 -force_repeat -loadprocedure dbsl

TRACE: 2011-09-15 16:42:56 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPSSEXC_1' import package into database:

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -nolog -c 50000 -force_repeat -loadprocedure dbsl

ERROR: 2011-09-15 16:42:57 com.sap.inst.migmon.LoadTask run

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

Process 'C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_2.cmd -dbcodepage 4103 -l SAPSSEXC_2.log -nolog -c 50000 -force_repeat -loadprocedure dbsl' exited with return code 2.

For mode details see 'SAPSSEXC_2.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: 2011-09-15 16:42:57 com.sap.inst.migmon.LoadTask run

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

Process 'C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -nolog -c 50000 -force_repeat -loadprocedure dbsl' exited with return code 2.

For mode details see 'SAPSSEXC_1.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-09-15 16:43:26

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

WARNING: 2011-09-15 16:43:26

2 error(s) during processing of packages.

INFO: 2011-09-15 16:43:26

Import Monitor is stopped.

can u pls help me in understandig where exactly error is..?

what will be the possible solutions..?

regards,

vinisha

[Former Member · Accepted solution]

Hi,

Also, please post the contents of log files 'SAPSSEXC_1.log' and 'SAPSSEXC_2.log'.

Regards,

Srikishan

[Former Member]

Hello Sundaresh ,

Thank you very much for helping me..

One thing i like to ask u is there any need to install DB externally i mean Oracle ets..?

actually i read the start.htm file and nthg is mentioned regarding DB so i didn't install any .

Infact i thought it will work with the MaxDB ,

Thanks once again ,

Regards,

Vinisha.

[Former Member]

Hi,

If you are installing ECC 6.0 on MaxDB, a seperate installation would not be required. The SAPInst asks for the MaxDB Database components DVDs during the Input Parameters phase and installs the database. It might be that the DB is installed but was not up and running.

Regards,

Srikishan

[Former Member]

Hi Vinisha,

Please check the below links. It has trouble shooting tips for maxdb

http://maxdb.sap.com/72938EE2-A6E5-4AB2-BA91-5750E78CAD9E/FinalDownload/DownloadId-2FCDEEFEBF916A7A7...

http://www.open-maxdb-group.org/72938EE2-A6E5-4AB2-BA91-5750E78CAD9E/FinalDownload/DownloadId-7E034D...

Regards

Sundaresh

[Former Member]

*SAPSSEXC1.log File ..._.*

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110916164600

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Nov 12 2010 03:08:47

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -nolog -c 50000 -force_repeat -loadprocedure dbsl

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running))

(DB) ERROR: db_connect rc = 256

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running))

(DB) ERROR: DbSlErrorMsg rc = 99

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

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110916164600

[Former Member]

Hi Vinisha,

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:[5] database not running))

DB is not up. Pls. start the DB. Which DB is this Oralce ? If it is oracle check the listner also. and continue the installation.

Thanks

Sundaresh

[Former Member]

Hi guys,

i'm again sending u the details of log files ... pls have a look

An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 2 > SAP Application Server ABAP > MaxDB > Central System > Central System( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:

Choose Retry to repeat the current step.

Choose View Log to get more information about the error.

Stop the option and continue with it later.

Log files are written to C:\Program Files/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL/.

*After this i open the importmonitor.log......*_

java version "1.5.0_22"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)

Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode)

Import Monitor jobs: running 1, waiting 1, completed 35, failed 0, total 37.

Loading of 'SAPSSEXC_1' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 35, failed 1, total 37.

*then SAPSSEXC1 .log.....*_

[Former Member]

Hello Sundaresh ,

Thanks for your suggestion..

After doing the setup as u said ..do i need to uninstall or continue with the same ?

thanks,

Regards,

vinisha.

[Former Member]

Hello srikishan,

I uninstall first and then install it again today , now again i stuck at the same point .. its really tiring pls help me ..

*as u requested log file SAPSSEXC1 i_s.. 😘

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110916142652

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: version R7.20/V1.4 [UNICODE]

Compiled Nov 12 2010 03:08:47

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -nolog -c 50000 -force_repeat -loadprocedure dbsl

(DB) INFO: connected to DB

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

(DB) INFO: Maxdb Kernel version 7.8.01.018

SQLDBC 7.8.1.018

(GSI) INFO: dbname = "NSP "

(GSI) INFO: vname = "ADABAS D "

(GSI) INFO: hostname = "vniks "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "VNIKS"

(GSI) INFO: release = "5.1"

(GSI) INFO: version = "2600 Service Pack 3"

(GSI) INFO: machine = "2x Intel 80686 (Mod 15 Step 13)"

(TSK) ERROR: file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\SAPSSEXC_1.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL\SAPSSEXC_1.TSK possibly corrupted

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

C:\usr\sap\NSP\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110916142655

Thanks,

Regards,

Vinisha

[Former Member]

Hi Vinisha,

1. Check the path of JAVA_HOME in the environmental varible

2. If Possible clear the logs from C:\Program Files\sapinst_instdir\.....

3. or create a folder ex: c:\sapinst_log

4. Call the sapinst from this folder like c:\sapinst_log\d:\<DVD Dump>\master\sapinst

5. While entering the values for the parameters in the sapinst screen, try to avoid going back to the previous screens. means.. before clicking <next> verify properly..

6. Follow installation manual clearly.. it will work

Regards

Sundaresh

[Former Member]

try setting SAPSYSTEMNAME at command line and rerun the set up