sapides installation error

[Former Member]

I am new in SAP . I am installing SAPIDES on win 2003 with oracle.

During Import Abap I am facing probbb.

NFO 2011-04-08 03:19:17

Switched to user: ideadm.

INFO 2011-04-08 03:19:17

Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.

INFO 2011-04-08 03:19:17

Output of C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs E:\sapdump\Export\export1\EXP1;E:\sapdump\Export\export2\EXP2;E:\sapdump\Export\export3\EXP3;E:\sapdump\Export\export4\EXP4;E:\sapdump\Export\export5\EXP5;E:\sapdump\Export\export6\EXP6;E:\sapdump\Export\export6\EXP7;E:\sapdump\Export\export6\EXP8;E:\sapdump\Export\export6\EXP9;E:\sapdump\Export\export6\EXP10;E:\sapdump\Export\export6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.

WARNING 2011-04-08 03:23:18

Execution of the command "C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs E:\sapdump\Export\export1\EXP1;E:\sapdump\Export\export2\EXP2;E:\sapdump\Export\export3\EXP3;E:\sapdump\Export\export4\EXP4;E:\sapdump\Export\export5\EXP5;E:\sapdump\Export\export6\EXP6;E:\sapdump\Export\export6\EXP7;E:\sapdump\Export\export6\EXP8;E:\sapdump\Export\export6\EXP9;E:\sapdump\Export\export6\EXP10;E:\sapdump\Export\export6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:

java version "1.4.2_11"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06)

Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)

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

Loading of 'SAPAPPL2' import package: ERROR

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

ERROR 2011-04-08 03:23:18

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

ERROR 2011-04-08 03:23:18

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 .

INFO 2011-04-08 03:32:16

An error occured and the user decided to retry the current step: "|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".

INFO 2011-04-08 03:32:18

Switched to user: ideadm.

INFO 2011-04-08 03:32:19

Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.

INFO 2011-04-08 03:32:19

Switched to user: ideadm.

INFO 2011-04-08 03:32:19

Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.

INFO 2011-04-08 03:32:19

Output of C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs E:\sapdump\Export\export1\EXP1;E:\sapdump\Export\export2\EXP2;E:\sapdump\Export\export3\EXP3;E:\sapdump\Export\export4\EXP4;E:\sapdump\Export\export5\EXP5;E:\sapdump\Export\export6\EXP6;E:\sapdump\Export\export6\EXP7;E:\sapdump\Export\export6\EXP8;E:\sapdump\Export\export6\EXP9;E:\sapdump\Export\export6\EXP10;E:\sapdump\Export\export6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.

WARNING 2011-04-08 03:36:51

Execution of the command "C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs E:\sapdump\Export\export1\EXP1;E:\sapdump\Export\export2\EXP2;E:\sapdump\Export\export3\EXP3;E:\sapdump\Export\export4\EXP4;E:\sapdump\Export\export5\EXP5;E:\sapdump\Export\export6\EXP6;E:\sapdump\Export\export6\EXP7;E:\sapdump\Export\export6\EXP8;E:\sapdump\Export\export6\EXP9;E:\sapdump\Export\export6\EXP10;E:\sapdump\Export\export6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:

java version "1.4.2_11"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06)

Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)

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

Loading of 'SAPAPPL2' import package: ERROR

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

ERROR 2011-04-08 03:36:51

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

ERROR 2011-04-08 03:36:51

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 .

INFO 2011-04-08 04:30:37

An error occured and the user decided to retry the current step: "|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".

INFO 2011-04-08 04:30:45

Switched to user: ideadm.

INFO 2011-04-08 04:30:47

Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.

INFO 2011-04-08 04:30:47

Switched to user: ideadm.

INFO 2011-04-08 04:30:47

Working directory changed to C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.

INFO 2011-04-08 04:30:47

Output of C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs E:\sapdump\Export\export1\EXP1;E:\sapdump\Export\export2\EXP2;E:\sapdump\Export\export3\EXP3;E:\sapdump\Export\export4\EXP4;E:\sapdump\Export\export5\EXP5;E:\sapdump\Export\export6\EXP6;E:\sapdump\Export\export6\EXP7;E:\sapdump\Export\export6\EXP8;E:\sapdump\Export\export6\EXP9;E:\sapdump\Export\export6\EXP10;E:\sapdump\Export\export6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.

WARNING 2011-04-08 04:34:48

Execution of the command "C:\j2sdk1.4.2_11\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs E:\sapdump\Export\export1\EXP1;E:\sapdump\Export\export2\EXP2;E:\sapdump\Export\export3\EXP3;E:\sapdump\Export\export4\EXP4;E:\sapdump\Export\export5\EXP5;E:\sapdump\Export\export6\EXP6;E:\sapdump\Export\export6\EXP7;E:\sapdump\Export\export6\EXP8;E:\sapdump\Export\export6\EXP9;E:\sapdump\Export\export6\EXP10;E:\sapdump\Export\export6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:

java version "1.4.2_11"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06)

Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode)

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

Loading of 'SAPAPPL2' import package: ERROR

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

ERROR 2011-04-08 04:34:48

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

thanks

moni

[Former Member]

Hi,

You need to change oracle memory parameters. Mostly SHARED_POOL_SIZE

Refer 830576 Parameter recommendations for Oracle 10g

Also check below SAP notes for details.

Note 869006 - Composite SAP note: ORA-04031

Note 133351 - Short dumps due to Oracle error ORA 4031

Note 789011 - FAQ: Oracle memory areas

Hope this helps

Thanks

Sushil

[Former Member]

as per marks . I install again Oracle via sapserver.cmd .then start installation of sap.

at same it stop . then I check that database is connected. but its giving here error.

Enter user-name: /as sysdba

ERROR:

ORA-12560: TNS:protocol adapter error

I check the oracle services. all is started . i again reboot my server. but problem is same .

ORA-12560: TNS:protocol adapter error

Moni

[Former Member]

dear Monika

your listner is not ok

just do one thing check and set your environment variable same as you will find when you login as <SID>adm

and then try it will work

SQL>startup nomount

and restart your installation

ok

[Former Member]

ORA-12560: TNS:protocol adapter error

its comes only and only when your listner is not ok

whenever you check your listner service just mannually start it...

or else through

command

lsnrctl

after that

start

it will start...

but be sure that you environment variable through which you are login should be ok

so my suggesion to you

login as <sid>adm user that is creted at the time of installation .

and the try sqlplus

and SQL>startup nomount

and then restart installation from instdir

ok

you will get the solution

Cheers

Anuj

[Former Member]

thanks all of you. I set environment veriable . then start oracle from SQL command. and continue Installation. Now i have completed my installation.

Thanks all of you again.

Moni

[Former Member]

Your welcome moni

Regards

Anuj

[Former Member]

Hi

Some times due to in sufficient shared pool size you may get this type of errors check the shared pool size.

sqlplus "/as sysdba"

show parameter shared_pool_size;

btw paste the job log of the job which got failed

Regards

Uday

[Former Member]

Hi,

Did you checked SAPAPPL2 log file from the sapinst install directory? That´s what the message is asking to do.

By the way you should use a newer Java VM version for installations.

[Former Member]

Thanks for your response . I Check SAPAPPL2.log.

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110407191842

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

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

Compiled Sep 1 2006 00:38:35

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\sapdump\Export\export4\EXP4\DATA\SAPAPPL2.STR C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL SAPAPPL2.TSK ORA -l SAPAPPL2.log

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: job completed

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110407191857

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110407191858

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

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

Compiled Sep 1 2006 00:38:35

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(DB) INFO: /AIN/ACTTYPE created #20110407193301

(IMP) INFO: import of /AIN/ACTTYPE completed (84 rows) #20110407193301

(DB) INFO: /AIN/ACTTYPE~0 created #20110407193301

DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=33)

(DB) ERROR: DDL statement failed

(CREATE UNIQUE INDEX "TJV52~0" ON "TJV52" ( "MANDT", "SPRAS", "VSPART" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )

DbSlExecute: rc = 99

(SQL error 604)

error message returned by DbSl:

ORA-00604: error occurred at recursive SQL level 2

ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select o.owner#,o.name,o.nam...","Typecheck","kgghtInit")

(DB) INFO: disconnected from DB

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

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110408043425

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110408060006

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

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

Compiled Sep 1 2006 00:38:35

F:\usr\sap\IDE\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

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

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110408060007

thanks in Advanced

Moni

[former_member227600]

Hi ,

edit ora<SID>.sap file & increass the value of shared pool.restart your machine or database & try again.

karan

[Former Member]

Monika,

It looks like you need more memory for shared_pool_size. You can edit this parameter in init<sid>.ora file and then restart the oracle.

Hope this helps.

Manoj

[Former Member]

Dear ,

Thanks for your response . I change value in initIDE.ora

F:\oracle\product\10.2.0\db_1\database\

Earlier shared_pool_size was 160274841

1. unit of shared_pool_size: bytes

2. unit of db_block_buffers: number of cached blocks

3. unit of log_buffer: bytes

shared_pool_size = 420274841

1. 10% of shared_pool_size

shared_pool_reserved_size = 16027484

log_buffer = 1048576

Then restart my server and again start installation with Continue with OLD.

But same problem .

SAPPRDL2.log

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

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

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110410013555

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20110410015436

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

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

Compiled Sep 1 2006 00:38:35

F:\usr\sap\IDE\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

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

F:\usr\sap\IDE\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20110410015437

what should i do for this one

Moni

[Former Member]

Dear Monika,

Do one thing login as <SID>adm

ok

and try @sqlplus level

and run startup nomount

ok then contt the installation....

it will work....

if not able to go through with SQLPLUS then....

check listner status....

and also environment variable.

ok

do that and you will get the solution...

Cheers

Anuj

[markus_doehr2]

> F:\oracle\product\10.2.0\db_1\database\

It seems to me, that you installed the database software by having doubleclicked on "setup.exe" on the Oracle DVD. This is not correct.

The usual ORACLE_HOME looks like "c:\oracle<SID>\102".

If you've done that, then you may run into other problems later.

I suggest:

- uninstall the SAP system

- uninstall the database software

- boot the machine

- install Oracle correctly by using "sapserver.cmd" on the DVD

- install the latest patchset (10.2.0.4)

- install the latest interim patch for 10.2.0.4

- restart sapinst to load the content into the database

Markus

[Former Member]

Thanks for your response .

I check my listener status . It start sucessfully. then I start and stop my listener .its working file.

I have check shared_pool_size via SQL prompt

it show as below

SQL> show parameter shared_pool_size;

NAME TYPE VALUE

-

---

-

---

-

---

shared_pool_size big integer 0

SQL> startup nomount

ORA-01081: cannot start already-running ORACLE - shut it down first

why its showing value 0.

But i have changed in initIDE.ora.

thanks

moni

[Former Member]

Dear Monika,

Markus saying very correct thing that you didnot install orcale properly ....

ok

but for increaseing shared pool size...

what you have to follow...

first of all check listner status

then

1. Start the database:

2. SQL> STARTUP NOMOUNT

3. SQL> SHOW PARAMETER PFILE;

4. SQL> SHOW PARAMETER SHARED_POOL_SIZE

SET parameter upto 512 for 2-4 gb RAM

6. SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='512M' SCOPE=spfile;

7. SQL>shutdown immediate

resatrt server

and then try...

ok

Edited by: anuj sharma on Apr 10, 2009 8:35 AM