Error in sap installation in phase 18 - Import Abap

[joo_migueldimas]

Hi gurus,

Iu00B4m facing with a problem when try to install SAP ERP 2005 SR2 with Oracle 10.2.0.4 in windows 2003 server.

Iu00B4m stuck in phase 18 - 44 - Import Abap with error log (in image):

http://img174.imageshack.us/img174/5479/error.png

I checked other logs:

R3load.exe.log

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

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090716193422

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

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 UNICODE

Compiled Jan 24 2008 01:41:44

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

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

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

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090716193428

Can you help me how can I solve this problem...!?

Best regards,

Jou00E3o Dimas - Portugal

[markus_doehr2 · Accepted solution]

Please start your listener (either using services or by executing "lsnrctl start" as user <sid>adm).

Markus

[joo_migueldimas · Accepted solution]

Hi Markus,

Thanks again, you are very kind person... thanks one more time for help me in toward to the solution!!

I´ll give you the highest punctuation!!

Thanks also to the others users that help me, Sunny Pahuja ; Shambo ; Surendrajain2003.

Best regards,

João Dimas - Portugal

[Former Member]

Hi Experts

I'm getting the same error while installing database instance in distributed environment (ASCS is already installed successfully). Can anyone please help in getting rid of this..

Error in Import ABAP phase -

Logs from R3load.exe.log file -

Logs from sapinst_dev.log file -

Regards

Hardeep

[Former Member]

Hi ,

I have't solve this problem until now. I try all you solutions but it does't works.

I don't know what should I do now.

Regards

Stephenlii

[former_member206552]

Hi Stephen,

please open a question with all the required logs and errors and we will try and assist

best regards

marius

[joo_migueldimas]

Hello Stephen Lii,

Please Stephen as recommended by Marius Burger, please open a new SCN thread with your problem and post there all the required logs because this is a very old thread and maybe your problem isn´t related with this problem that I had some years ago.

Regards,

João Dimas

[Former Member]

Hi marius and João Dimas,

You guys are very nice. Thank you very much. I'll open a new SCN thread later.

Best regards,

Stephenlii

[Former Member]

MARKUS,

I am installing IDES ECC6.0 including EHP4 on 32 bit machine.. I came to know from the following ( Note 1379040 - IDES ERP 6.0 ECC 6.0 incl. EHP4) that i cannot install IDES ECC6.00 on 32 bit,but i can install via system copy method.. I followed the exact method as mentioned in the same note. Installation was going smoothly but when it came to IMPORT ABAP PHASE..there were total of 103 files out of which 102 files was sucessful and 1 got failed.. Error is almost similar to tat what this thread has. I also saw that listerner was not started ,so i started the listener (status is showing listener is up) but still I am facing the same issue. I am pasting the log from SAPVIEW log file.

E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20091021202919

E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe: version R7.01/V1.4 [UNICODE]

Compiled Feb 24 2009 23:04:42

E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.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

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

E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20091021202923

I also tried Note 709389 - Problems during load of SAPVIEW , but I am not very clear on how to go by this note.. I had rechecked the export DVD data's.. all are fine..

Please help me out of this issue.. Waiting for your reply..

Regards

Hari Narayanan.M

[markus_doehr2]

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

ORA-01034 means "Oracle not available" - your database crashed.

A few questions before I can maybe propose a solution:

- What exact Oracle version are you using?

- Did you install Oracle using the "sapserver.cmd" script?

- Did you install patchset 10.2.0.2 (or 10.2.0.4) after you installed the version delivered on the DVD plus the interim patch and before you started sapinst?

Markus

[Former Member]

Hi Markus,

Thanks for your reply..

1) Oracle version is 10G

2) No, I used oui.exe to install oracle.

3) I am using 10.2.0.2

But I am able to connect to database, how can it be possible if its database crash???

I am also pasting the import log for you reference here..:

TRACE: 2009-10-22 16:30:36 com.sap.inst.migmon.LoadTask run

Loading of 'SAPVIEW' import package is started.

TRACE: 2009-10-22 16:30:36 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPVIEW' import package into database:

E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -stop_on_error

ERROR: 2009-10-22 16:30:36 com.sap.inst.migmon.LoadTask run

Loading of 'SAPVIEW' import package is interrupted with exception.

java.io.IOException: CreateProcess: E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -stop_on_error error=216

at java.lang.ProcessImpl.create(Native Method)

at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)

at java.lang.ProcessImpl.start(ProcessImpl.java:30)

at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)

at java.lang.Runtime.exec(Runtime.java:591)

at com.sap.inst.lib.io.ProcessUtils.createProcess(ProcessUtils.java:28)

at com.sap.inst.migmon.LoadTask.loadPackage(LoadTask.java:640)

at com.sap.inst.migmon.LoadTask.processPackage(LoadTask.java:334)

at com.sap.inst.migmon.LoadTask.run(LoadTask.java:195)

at java.lang.Thread.run(Thread.java:595)

at com.sap.inst.lib.util.ThreadDispatcher$ThreadWrapper.run(ThreadDispatcher.java:113)

INFO: 2009-10-22 16:31:05

All import packages are processed.

WARNING: 2009-10-22 16:31:05

1 error(s) during processing of packages.

INFO: 2009-10-22 16:31:05

Import Monitor is stopped.

I am also pasting import_monitor.java.log

java version "1.5.0_06"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)

Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)

Import Monitor jobs: running 1, waiting 0, completed 102, failed 0, total 103.

Loading of 'SAPVIEW' import package: ERROR

Import Monitor jobs: running 0, waiting 0, completed 102, failed 1, total 103.

Please do the needful..

Regards

Hari Narayanan.M

[markus_doehr2]

> But I am able to connect to database, how can it be possible if its database crash???

You did quite a few things wrong.

A SAP system requires the database to have certain features activated. This is done by using "sapserver.cmd" which uses a response file to make sure all environment is set properly and that the init<sid>.ora has the correct parameters. Otherwise you may run into trouble.

You also need to install the proper patches for the database (so including the minipatch installed using Opatch before you load the database). That patch contains important fixes which makes sure the database is stable.

Since you apparently didn't follow the installation guides your database may not be properly installed.

> java version "1.5.0_06"

> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)

> Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)

Java 1.5/5.0 is not supported, you need to use 1.4.2.

I suggest you start sapinst, use the point to "uninstall" your instance and start from scratch following the installation guide step-by-step to make sure the system will be installed properly.

Markus

[Former Member]

I agree to your point Markus.

I will restart the installation again.. But I have few queries before doing it..

1) I have done few installations in the same way,but everything went on well and it was successful,So this makes me to think otherwise..

2) Is it mandatory that oracle patch set 4 is required for this installation? 10.2.0.2 will not help?

Can I have your views before proceeding?

Regards

Hari Narayanan.M

[markus_doehr2]

> 1) I have done few installations in the same way,but everything went on well and it was successful,So this makes me to think otherwise..

The you were "lucky".

Technically you can do with the database whatever you want, the question is, will the system be stable, fast and reliable if you don't use the SAP recommended way to install it. I don't know what's the problem with following the official way. If you know everything to install the database manually (setting environment, permissions, registry keys etc.) it's fine to do it that way, I'm not trying to be offensive.

> 2) Is it mandatory that oracle patch set 4 is required for this installation? 10.2.0.2 will not help?

Not mandatory but 10.2.0.2 without any additional patches contains bugs that can generate bad blocks on the database. You will need to install at least the minipatch for 10.2.0.2 and set all the required parameters to activate those fixes.

I have seen so many posts here on the SDN where people tried to "know better" and didn't follow the tested and verified way to install and run the database and now having problems keeping their systems running.

> ERROR: 2009-10-22 16:30:36 com.sap.inst.migmon.LoadTask run

> Loading of 'SAPVIEW' import package is interrupted with exception.

> java.io.IOException: CreateProcess: E:\usr\sap\ID9\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l > SAPVIEW.log -stop_on_error error=216

> at java.lang.ProcessImpl.create(Native Method)

This problem means, that the Java migration monitor could not create an R3load process, maybe because of too less memory, maybe because of a disk full.

I would no more install a 32bit Unicode instance, it's very cumbersome to keep it running. Since this seems to be a new installation I highly recommend going for 64bit.

Markus

[Former Member]

Thanks for your suggestion MARKUS..

The main reason we are goin gon 32 bit machine is,we are planning for SAP TAO installation which runs only in 32 bit enviornment as TAO requires dotnetframework 2.0 which will work only in 32 bit.

This problem means, that the Java migration monitor could not create an R3load process, maybe because of too less memory, maybe because of a disk full

There were total 103 in abap import phase,102 was completed leaving 1 failed. I suppose for all 103 process it would use r3 load rite?? if so why one failed alone will be due to memory issue... this question is purely out of anxiety,please dont mistake me and correct me if iam wrong. I am having enough disk space too..

Please tell me whether 100 % my issue will be solved if iam redoing it as mentioned by you from scratch .

Regards

Hari Narayanan.

[markus_doehr2]

> The main reason we are goin gon 32 bit machine is,we are planning for SAP TAO installation which runs only in 32 bit enviornment as TAO requires dotnetframework 2.0 which will work only in 32 bit.

According to the installation documentation the TAO client doens't necessarily need to be installed on the ERP server. If that assumption was true only customers running 32bit Windows on their ERP systems could use TAO which is very unlikely. ST-TAO is installed on Solution Manager EHP1 which should also be on 64bit.

> There were total 103 in abap import phase,102 was completed leaving 1 failed. I suppose for all 103 process it would use r3 load rite?? if so why one failed alone will be due to memory issue... this question is purely out of anxiety,please dont mistake me and correct me if iam wrong. I am having enough disk space too..

What do you see in sapinst_dev.log when this error occurs?

Markus

[Former Member]

Markus,

I am getting the following error while trying to install TAO in 64 bit enviornment.

Prerequisite check for system component .NET Framework 2.0 failed with the following error message:

"This version of the .NET Framework 2.0 is not supported on a 64-bit operating system. Contact your application vendor."

I am pasting the sapdev_inst.log below..

WARNING 2009-10-22 16:31:05.537

CJSlibModule::writeWarning_impl()

Execution of the command "C:\Program Files\Java\jdk1.5.0_06\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:

java version "1.5.0_06"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)

Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)

Import Monitor jobs: running 1, waiting 0, completed 102, failed 0, total 103.

Loading of 'SAPVIEW' import package: ERROR

Import Monitor jobs: running 0, waiting 0, completed 102, failed 1, total 103.

TRACE 2009-10-22 16:31:05.537

Function setMessageIdOfExceptionMessage: nw.programError

ERROR 2009-10-22 16:31:05.537

CJSlibModule::writeError_impl()

CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

TRACE 2009-10-22 16:31:05.537 [iaxxejsbas.hpp:483]

EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.

ERROR 2009-10-22 16:31:05.553 [sixxcstepexecute.cpp:950]

FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 ( 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.).

TRACE 2009-10-22 16:31:05.569 [iaxxgenimp.cpp:752]

CGuiEngineImp::showMessageBox

<html> <head> </head> <body> <p> An error occurred while processing option Enhancement Package 4 for SAP ERP 6.0 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > Central System > Based on AS ABAP > 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: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/ERPEhP4/LM/COPY/ORA/SYSTEM/CENTRAL/AS-ABAP/. </p> </body></html>

TRACE 2009-10-22 16:31:05.569 [iaxxgenimp.cpp:1255]

CGuiEngineImp::acceptAnswerForBlockingRequest

Waiting for an answer from GUI

Regards

Hari Narayanan.M

[Former Member]

Markus, I am getting the following error while trying to install TAO in 64 bit enviornment.

Prerequisite check for system component .NET Framework 2.0 failed with the following error message: "This version of the .NET Framework 2.0 is not supported on a 64-bit operating system. Contact your application vendor."

I am pasting the sapdev_inst.log below..

WARNING 2009-10-22 16:31:05.537 CJSlibModule::writeWarning_impl() Execution of the command "C:\Program Files\Java\jdk1.5.0_06\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output: java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode) Import Monitor jobs: running 1, waiting 0, completed 102, failed 0, total 103. Loading of 'SAPVIEW' import package: ERROR Import Monitor jobs: running 0, waiting 0, completed 102, failed 1, total 103. TRACE 2009-10-22 16:31:05.537 Function setMessageIdOfExceptionMessage: nw.programError ERROR 2009-10-22 16:31:05.537 CJSlibModule::writeError_impl() CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log. TRACE 2009-10-22 16:31:05.537 [iaxxejsbas.hpp:483] EJS_Base::dispatchFunctionCall() JS Callback has thrown unknown exception. Rethrowing. ERROR 2009-10-22 16:31:05.553 [sixxcstepexecute.cpp:950] FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 ( 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.). TRACE 2009-10-22 16:31:05.569 [iaxxgenimp.cpp:752] CGuiEngineImp::showMessageBox

An error occurred while processing option Enhancement Package 4 for SAP ERP 6.0 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > Central System > Based on AS ABAP > 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/ERPEhP4/LM/COPY/ORA/SYSTEM/CENTRAL/AS-ABAP/.

Regards

Hari Narayanan.M

[markus_doehr2]

> Prerequisite check for system component .NET Framework 2.0 failed with the following error message:

> "This version of the .NET Framework 2.0 is not supported on a 64-bit operating system. Contact your application vendor."

Yes - but why do you try to install it on the ERP server? You can install it (to my understanding) on ANY 32bit machine and connect it to your ERP system.

> Execution of the command "C:\Program Files\Java\jdk1.5.0_06\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:

> java version "1.5.0_06"

Well - Java 1.5 is not supported - did you try with a Java 1.4.2 version? I'd also use the latest update of 1.5, build 06 is also pretty old.

Markus

[Former Member]

Hi,

I have the exact error at "IMPORT ABAP" stage while installing IDES ECC6 on LINUX.

I didnt solved by starting Listener. Please advise how to get through these erros.

[ email@removed AS]# more R3load.exe.log

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

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

/usr/sap/CHL/SYS/exe/run/R3load: START OF LOG: 20091008085304

/usr/sap/CHL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/

R3ldmain.c#14 $ SAP

/usr/sap/CHL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/CHL/SYS/exe/run/R3load -testconnect

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc 541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc 541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc 541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc 541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

/usr/sap/CHL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/CHL/SYS/exe/run/R3load: END OF LOG: 20091008085304

Thanks,

PAUL

[markus_doehr2]

> I have the exact error at "IMPORT ABAP" stage while installing IDES ECC6 on LINUX.

> I didnt solved by starting Listener. Please advise how to get through these erros.

What's the output of the commands

lsnrctl stat

tnsping CHL

Markus

[joo_migueldimas]

Hi again... sorry... I forgot the other log file.

So this message is a continuation of the previous. As you imagine I donu00B4t get to put here all log because is very long!!

sapinst.log :

....

....

WARNING 2009-07-16 19:34:28

Execution of the command "D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:

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

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090716193422

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

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

Compiled Jan 24 2008 01:41:44

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe -testconnect

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

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

D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090716193428

ERROR 2009-07-16 19:34:28

CJS-30023 Process call 'D:\usr\sap\AIO\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.

ERROR 2009-07-16 19:34:28

FCO-00011 The step testDatabaseConnection 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|testDatabaseConnection was executed with status ERROR .

Best regards,

Jou00E3o Dimas - Portugal

[sunny_pahuja2]

Hi,

Check SAP Note 609332 - Composite note: ORA-12541/ORA-12224

Thanks

Sunny

[Former Member]

Right Click on My Computer>Manage>Services & Applications-->Services

Find the Listernar service & go to the properties Change the Startup Type from Manual to Automatic & Start the Listener Service.

Check your database is up & running then start the SAPinst.

Tnx,

Shambo

[Former Member]

hi,

go to command prompt

lsnrctl start

now check r u able to ping service

tnsping <sid>