cancel
Showing results for 
Search instead for 
Did you mean: 

Import error

Former Member
0 Kudos

Hello all

I have exported my existing sap system data successfully

i a using oracle 10.2.0.5

export was successful but in import phase i got error messege in import ABAP phase

ERROR 2012-02-15 14:24:51

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

Log details for : import_monitor.java.log

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 27, completed 11, failed 0, total 39.

Import Monitor jobs: running 2, waiting 26, completed 11, failed 0, total 39.

Import Monitor jobs: running 3, waiting 25, completed 11, failed 0, total 39.

Loading of 'SAPSSEXC_2' import package: ERROR

Import Monitor jobs: running 2, waiting 25, completed 11, failed 1, total 39.

Import Monitor jobs: running 3, waiting 24, completed 11, failed 1, total 39.

Loading of 'SAPSSEXC_1' import package: ERROR

Import Monitor jobs: running 2, waiting 24, completed 11, failed 2, total 39.

Loading of 'REPOSRC' import package: ERROR

Import Monitor jobs: running 1, waiting 24, completed 11, failed 3, total 39.

Loading of 'DYNPSOURCE' import package: ERROR

Import Monitor jobs: running 0, waiting 24, completed 11, failed 4, total 39.

Import Monitor jobs: running 1, waiting 23, completed 11, failed 4, total 39.

Import Monitor jobs: running 2, waiting 22, completed 11, failed 4, total 39.

Import Monitor jobs: running 3, waiting 21, completed 11, failed 4, total 39.

Log Details for import_monitor.log.

TRACE: 2012-02-15 13:32:19 com.sap.inst.migmon.LoadTask processPackage

Loading of 'DYNPSOURCE' import package into database:

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

INFO: 2012-02-15 13:34:17 com.sap.inst.migmon.LoadTask run

Loading of 'DOKCLU' import package is successfully completed.

TRACE: 2012-02-15 13:34:18 com.sap.inst.migmon.LoadTask run

Loading of 'SAPNTAB' import package is started.

TRACE: 2012-02-15 13:34:18 com.sap.inst.migmon.LoadTask processPackage

Task file generation for 'SAPNTAB' import package:

E:\usr\sap\SHP\SYS\exe\uc\NTI386\R3load.exe -ctf I D:\DB_EXPORt_NEW\ABAP\DATA\SAPNTAB.STR "C:\Program Files\sapinst_instdir\NW04S\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP\DDLORA.TPL" SAPNTAB.TSK ORA -l SAPNTAB.log

TRACE: 2012-02-15 13:34:18 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPNTAB' import package into database:

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

ERROR: 2012-02-15 13:41:42 com.sap.inst.migmon.LoadTask run

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

Process 'E:\usr\sap\SHP\SYS\exe\uc\NTI386\R3load.exe -i DYNPSOURCE.cmd -dbcodepage 4103 -l DYNPSOURCE.log -stop_on_error' exited with return code 2.

For mode details see 'DYNPSOURCE.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

i don't know why this error is occurring

please help me to get out of here

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Seems like tables are not created in the target system.

Carefully analyze the import logs and check for errors..

Did you create the oracle tablespaces manually?

Did you run SMIGR_CREATE_DDL in the source system before export?

Can you please provide the details with ERROR from 'DYNPSOURCE.log' file.

Regards,

Venkata S Pagolu

Former Member
0 Kudos

Hello Venkata S Pagolu,

I did not create table space manually, & also i didnt run SMIGR_CREATE_DDL before taking export

i had stoped the sap instance & kept database connected & took the export, & tried to import in target system its showing above

error

Please check Log file :DYNPSOURCE.log

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

Compiled Apr 2 2006 23:26:45

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

(GSI) INFO: dbname = "DEV20120215080229 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "MCSTEST "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "MCSTEST"

(GSI) INFO: release = "5.2"

(GSI) INFO: version = "3790 Service Pack 2"

(GSI) INFO: machine = "2x Intel 80686 (Mod 23 Step 10)"

(DB) INFO: DYNPSOURCE created #20120216075839

DbSl Trace: OCI-call 'OCILobWrite' failed: rc = 1691

DbSl Trace: ORA-1691 occurred when writing to a LOB

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "DYNPSOURCE"

(SQL error 1691)

error message returned by DbSl:

ORA-01691: unable to extend lob segment SAPSR3.SYS_LOB0000009939C00005$$ by 1024 in tablespace PSAPSR3700

(DB) INFO: disconnected from DB

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

E:\usr\sap\SHP\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20120216081139

E:\usr\sap\SHP\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20120216090928

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

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

Compiled Apr 2 2006 23:26:45

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

(GSI) INFO: dbname = "DEV20120215080229 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "MCSTEST "

(GSI) INFO: sysname = "Windows NT"

(GSI) INFO: nodename = "MCSTEST"

(GSI) INFO: release = "5.2"

(GSI) INFO: version = "3790 Service Pack 2"

(GSI) INFO: machine = "2x Intel 80686 (Mod 23 Step 10)"

(DB) INFO: DYNPSOURCE deleted/truncated #20120216090939

DbSl Trace: OCI-call 'OCILobWrite' failed: rc = 1691

DbSl Trace: ORA-1691 occurred when writing to a LOB

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "DYNPSOURCE"

(SQL error 1691)

error message returned by DbSl:

ORA-01691: unable to extend lob segment SAPSR3.SYS_LOB0000009939C00004$$ by 8192 in tablespace PSAPSR3700

Former Member
0 Kudos

Hi,

Do the tablespace PSAPSR3700 have enough freespace?

Have this tablespace extended.

Also, update DBSL libraries.

Br,

Venky

Former Member
0 Kudos

Hi,

Please find below errors from log

DbSl Trace: ORA-1691 occurred when writing to a LOB

ORA-01691: unable to extend lob segment SAPSR3.SYS_LOB0000009939C00004$$ by 8192 in tablespace PSAPSR3700

extend the tablespace and give a try. it should proceed now.

Regards,

Venkata S Pagolu

former_member182034
Active Contributor
0 Kudos

hi amol,

would you past the log of following files

SAPSSEXC_2

SAPSSEXC_1

REPOSRC

DYNPSOURCE

Regards,

Former Member
0 Kudos

Hi Majami,

Sorry i cant provide you cause i have formatted the system and i have again executed same procedure

but mean time can you please provide me any system copy document or link cause i am lil confused between both process

export & import, i export it is showing only database export while in import it is asking for central instance

JPReyes
Active Contributor
0 Kudos

Sorry i cant provide you cause i have formatted the system and i have again executed same procedure

Making this thread obsolete.

but mean time can you please provide me any system copy document or link cause i am lil confused between both process

System copy guides are available and the procedure is well descibed on it

export & import, i export it is showing only database export while in import it is asking for central instance

Certainly... you are exporting the contents of the Database. To be able to import them into a new system you need to build the CI and DI otherwise you won't have a system to import the data into, right?

Please read the documentation

Regards

Juan