Error in Migration Monitor with error code 103

[Former Member]

Dear All, i exported system copy of Dev server and impot the System copy with new installation, on 18th step Abap Import it gives me an error:

ERROR 2009-06-22 12:48:05

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

ERROR 2009-06-22 12:48:05

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 .

Lines from impot_monitor.java.log file

java version "1.4.2_09"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)

Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)

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

Loading of 'SAPAPPL1' import package: ERROR

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

[Former Member · Accepted solution]

Hi

Can you check which job has failed ( completed 17, failed 1, total 19) and send us the log of that,you can find the same at import_monitor.java.log or import_monitor.log

Btw what is shared_pool_size you have.

start>cmd>run-->sqlplus "/as sysdba"

sql>show parameter shared_pool_size;

Regards

Uday

[Former Member · Accepted solution]

Few lines from import_monitor.log file

CONFIG: 2009-06-22 15:44:35

List of packages with table structure: 'SAP0000'.

CONFIG: 2009-06-22 15:44:35

List of packages with views: 'SAPVIEW'.

TRACE: 2009-06-22 15:44:35 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP\DDLORA.TPL' template file is started.

INFO: 2009-06-22 15:44:35 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP\DDLORA.TPL' template file is successfully completed.

Primary key creation: after load.

Index creation: after load.

INFO: 2009-06-22 15:44:35

Data codepage 4103 is determined using TOC file 'G:\Export_DB\ABAP\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.

TRACE: 2009-06-22 15:44:35 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is started.

TRACE: 2009-06-22 15:44:35 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL1' import package into database:

E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -k 17mgd5M50Dp01eqtdQQt11m2 -l SAPAPPL1.log -stop_on_error

ERROR: 2009-06-22 15:44:58 com.sap.inst.migmon.LoadTask run

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

Process 'E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -k 17mgd5M50Dp01eqtdQQt11m2 -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

WARNING: 2009-06-22 15:45:05

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

WARNING: 2009-06-22 15:45:05

1 error(s) during processing of packages.

INFO: 2009-06-22 15:45:05

Import Monitor is stopped.

INFO: 2009-06-22 15:54:22

Import Monitor is started.

CONFIG: 2009-06-22 15:54:22

Application options:

dbCodepage=4103

dbType=ORA

extFiles=yes

importDirs=G:\Export_DB\ABAP

installDir=C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP

jobNum=2

loadArgs= -stop_on_error

migrationKey=17mgd5M50Dp01eqtdQQt11m2

monitorTimeout=30

orderBy=

r3loadExe=E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2009-06-22 15:54:22

List of packages with table structure: 'SAP0000'.

CONFIG: 2009-06-22 15:54:22

List of packages with views: 'SAPVIEW'.

TRACE: 2009-06-22 15:54:22 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP\DDLORA.TPL' template file is started.

INFO: 2009-06-22 15:54:22 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP\DDLORA.TPL' template file is successfully completed.

Primary key creation: after load.

Index creation: after load.

INFO: 2009-06-22 15:54:22

Data codepage 4103 is determined using TOC file 'G:\Export_DB\ABAP\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.

TRACE: 2009-06-22 15:54:22 com.sap.inst.migmon.LoadTask run

Loading of 'SAPAPPL1' import package is started.

TRACE: 2009-06-22 15:54:22 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPAPPL1' import package into database:

E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -k 17mgd5M50Dp01eqtdQQt11m2 -l SAPAPPL1.log -stop_on_error

ERROR: 2009-06-22 15:54:44 com.sap.inst.migmon.LoadTask run

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

Process 'E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -k 17mgd5M50Dp01eqtdQQt11m2 -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

WARNING: 2009-06-22 15:54:52

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

WARNING: 2009-06-22 15:54:52

1 error(s) during processing of packages.

INFO: 2009-06-22 15:54:52

Import Monitor is stopped.

[Former Member · Accepted solution]

result of show parameter shared_pool_size

shared_pool_size big integer 232M

[markus_doehr2 · Accepted solution]

> ERROR: 2009-06-22 15:44:58 com.sap.inst.migmon.LoadTask run

> Loading of 'SAPAPPL1' import package is interrupted with R3load error.

> Process 'E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -k 17mgd5M50Dp01eqtdQQt11m2 -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

Check SAPAPPL1.log

Markus

[Former Member · Accepted solution]

Some Lines from End of SAPAPPL1 file:

(DB) INFO: ONRHP created #20090622231408

(IMP) INFO: import of ONRHP completed (0 rows) #20090622231408

(DB) INFO: ONRHP~0 created #20090622231408

(DB) INFO: ONRKL created #20090622231409

(IMP) INFO: import of ONRKL completed (8466 rows) #20090622231409

DbSl Trace: Error 1452 in exec_immediate() from oci_execute_stmt(), orpc=0

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

(DB) ERROR: DDL statement failed

(CREATE UNIQUE INDEX "ONRKL~0" ON "ONRKL" ( "MANDT", "OBJNR" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 71680 NEXT 0000000080K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )

DbSlExecute: rc = 99

(SQL error 1452)

error message returned by DbSl:

ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

(DB) INFO: disconnected from DB

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

E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090622231409

E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20090623091018

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

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

Compiled Jul 17 2007 01:28:45

E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -k 17mgd5M50Dp01eqtdQQt11m2 -l SAPAPPL1.log -stop_on_error

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

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

E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20090623091024

[markus_doehr2 · Accepted solution]

> (DB) ERROR: DDL statement failed

> (CREATE UNIQUE INDEX "ONRKL~0" ON "ONRKL" ( "MANDT", "OBJNR" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 71680 NEXT 0000000080K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )

> DbSlExecute: rc = 99

> (SQL error 1452)

> error message returned by DbSl:

> ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

Is that index existing on the source system?

> E:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]

> Compiled Jul 17 2007 01:28:45

Your copy tools are very old (almost two years).

If you use R3load for system copies always use the latest tools on source and target system. This will prevent you getting a number of known errors/problems.

Markus

[Former Member · Accepted solution]

Hi markus thanx for ur helpfull reply, but how can i update both systems regarding r3load can u tell me where i get some note about it.

[markus_doehr2 · Accepted solution]

Those are part of the database dependent part of the kernel, you will get them at the same place where you get the kernel patches.

However, a new R3load will not solve your current problem, there are values in in the index that are not unqiue on the SOURCE system.

Markus

[former_member712749 · Accepted solution]

Dear Usman

This problem is due to duplicate records in your table 'ONRKL' so that it is not generating unique key.In this table you have composite key on columns (mandt & objnr). First of all u find out the duplicate records in this table.

first of all login with

sqlplus "/as sysdba"

after this write down this query to view duplicate records

+sql> Select mandt,objnr from sapsr3.onrkl having count() > 1 group by mandt,objnr;+*

it will show u some records which are duplicate in this table. Now u have to delete these records from this table by using this query

+sql> delete from sapsr3.onrkl where mandt in (select mandt from sapsr3.onrkl having count() > 1 group by mandt);+*

after it

sql>commit;

then continue your old installation hope this will work.

Thanks

Muhammad Ali Sethi

[Former Member]

Hi

Try this

SQL>startup mount

SQL>Alter database open:

Regards

Uday

[Former Member]

Hi

Make it to 300M and restart the installation hope that should work out.

Regards

Uday

[Former Member]

No dear i have done it before but no success same error

[Former Member]

Hi

sqlplus "/as sysdba"

show parameter shared_pool_size;

increase value to 400M

alter system set shared_pool_size=400M;

Is your database open?

sql>select status from v$instance;

Regards

Uday

[Former Member]

SQL> select status from v$instance;

STATUS

-

---

OPEN

SQL> alter system set shared_pool_size=400M;

alter system set shared_pool_size=400M

*

ERROR at line 1:

ORA-02097: parameter cannot be modified because specified value is invalid

ORA-04033: Insufficient memory to grow pool

Please give the solution