cancel
Showing results for 
Search instead for 
Did you mean: 

Error code 103 Import Database - Copia Homogenea Solman

Former Member
0 Kudos

Hi experts,

I have an error in the import of the database, copy the Homogeneous Solman.

The error is:

 

An error occurred while processing option SAP
Solution Manager 7.1 Support Release 1 > Software Life-Cycle Options >
System Copy > Oracle > Target System Installation > Distributed System
> Based on AS ABAP and AS Java > Database Instance( 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 Log Files to get more information about the
error.

Stop the option and continue with it later.

The error is consistently presented, I move with Retry, but the process stops with this error again.


I need help to solve

thank you very much

Juan Carlos Salazar R.

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member185239
Active Contributor
0 Kudos

Hi Juan,

Can you please paste the logs

-import_monitor.java.log

-import_monitor.log


With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh Chaturvedi

The files are large.

This is the last record Import_monitor.log

ERROR: 2014-05-23 12:29:45 com.sap.inst.migmon.LoadTask run

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

Process '/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load -i SAPSSEXC_9.cmd -dbcodepage 4103 -l SAPSSEXC_9.log -stop_on_error' exited with return code 2.


For mode details see 'SAPSSEXC_9.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: 2014-05-23 12:29:50

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

This is the last record Import_monitor.java.log

Loading of 'SAPSSRC_1' import package: ERROR

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

Loading of 'SAPSSEXC_9' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 34, failed 51, total 86.

With Regards

Juan Carlos Salazar

0 Kudos

Hi Juan Carlos.

Did you executed the report SMIGR_CREATE_DDL before export phase?

Solution Manager have BW structures which need the execution of this reports.

If you proceed the system copy without this, you may encounter some errors in import phase with creation views and etc related.


However send the SAPSSRC_1 and SAPSSRC_9 log file contents or last lines.

Regards,

Mauricio Montoya

Former Member
0 Kudos

Hi Mauricio Montoya

Yes, I already run the SMIGR_CREATE_DDL report, before starting the export on the source server.

SAPSSRC_1 and SAPSSRC_9 log

I do not find these files; please indicate me where they are?

With Regards

Juan Carlos Salazar

0 Kudos

Hi Juan.

Check in sapinst_dir directory.

Former Member
0 Kudos

Hi Mauricio Montoya

Sorry, I had not seen before

SAPSSRC_1

(DB) ERROR: DDL statement failed

(CREATE TABLE "CCCINFO" ( "CCPHASE" VARCHAR2(6) DEFAULT ' ' NOT NULL , "REPFBNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "UNAME" VARCHAR2(36) DEFAULT ' ' NOT NULL , "DATUM" VARCHAR2(24) DEFAULT '00000000' NOT NULL , "APPLK_DOPR" VARCHAR2(6) DEFAULT ' ' NOT NULL , "TEXT50" VARCHAR2(150) DEFAULT ' ' NOT NULL  ) TABLESPACE PSAPSR3  STORAGE (INITIAL 0000000016K NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )

DbSlExecute: rc = 102


  (SQL error 955)

  error message returned by DbSl:

ORA-00955: name is already used by an existing object

(DB) INFO: disconnected from DB


/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)


/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140527095247

SAPSSRC_9

DB) ERROR: DDL statement failed


(CREATE TABLE "WDY_LIBRARY_USE" ( "COMPONENT_NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "LIBRARY_NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "VERSION" VARCHAR2(3) DEFAULT ' ' NOT NULL  ) TABLESPACE PSAPSR3702  STORAGE (INITIAL 0000000016K NEXT 0000000160K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )

DbSlExecute: rc = 102

(SQL error 955)

error message returned by DbSl:


ORA-00955: name is already used by an existing object

(DB) INFO: disconnected from DB


/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)

/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140527101604

With Regards

Juan Carlos Salazar

0 Kudos

Hi Juan.

One question. Did you started the import in a existing database? The import phase should be executed like a fresh installation with only database software installed.

Can you post the import.properties file content?

Former Member
0 Kudos

HI Mauricio Montoya

I am using a database already installed solman contained but had no data.

import:

dbType=ORA

importDirs=/instaladores2/KERNEL_IMPORT/Krnl_7.20_LNX_x86_64_PPC_64bit_SP04_/DATA_UNITS

installDir=/tmp/sapinst_instdir/SOLMAN71/LM/COPY/ORA/SYSTEM/DISTRIBUTED/AS/DB

orderBy=

ddlMap=ddl_mapping.txt

r3loadExe=/usr/sap/SOP/SYS/exe/uc/linuxx86_64/R3load

tskFiles=yes

extFiles=no

dbCodepage=4103

jobNum=3

monitorTimeout=30

loadArgs=-stop_on_error

trace=all

Thank you very much for your help.

Juan Carlos salazar

0 Kudos

These are the first jobs with errors? How many are completed?

If possible, run sapinst to uninstall the scraps of sap instance and remove de oracle instance completely (datafiles and etc).

An workaround is do drop these tables in database and restart de import, but if you have a old database created with tables and other structures created you will have a lot of this errors.

sqlplus> drop table <Schema>.<table>;

Again, the import phase should be executed like a fresh installation with only database software installed.

regards y suerte!

Mauricio Montoya

VJain
Active Contributor
0 Kudos

Hi Juan,

Please check if they helps:

1716201 - Obsolete - Update control.xml files for installation: Sybase ASE
609332 - Composite note: ORA-12541/ORA-12224

Please read and follow the sapnotes
#551344 - Unicode Conversion
#552464 - What is Big Endian / Little Endian? What Endian do i have?
#548016 - Conversion to Unicode
if want to copy system from non-unicode to unicode.

usefull link: http://service.sap.com/unicode@sap


Thanks

Vikram