cancel
Showing results for 
Search instead for 
Did you mean: 

Problem during AS-ABAP export, export preparation!

Former Member
0 Kudos

Dear All,

While going on with Export Preparation for ECC6.0 system SYSTEM COPY, encountered the following :

WARNING: Table QCM/OBIZ/ZVAT_C not in DB

WARNING: Table QCMZBILL_NUM_RA not in DB

WARNING: Table QCMZMTAXCOND not in DB

ERROR: ExeModify for write_ddloadd failed in row 43078

(rc = 26)

objectname = /1CN/CPASAP00001

objecttype = TABLE APPL0 X

tabart = APPL0 X

rowcount = 0

error message returned by DbSl:

DbSlExeModifyDB6( SQLExecute 😞 [IBM][CLI Driver][DB2/AIX64] SQL0803N One or more values in the INSERT statement, UPDATE stateme

nt, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index i

dentified by "1" constrains table "SAPHED.DDLOADD" from having duplicate values for the index key. SQLSTATE=23505 row=1

root@10.1.1.217(/tmp/sapinst_instdir/ERP/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/PREEXP)# date

Mon Jun 13 17:44:51 IST 2011

Please suggest what needs to be done...

Thanks in advance!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Post log files.

Have you downloaded latest SAPINST?

Former Member
0 Kudos

I've got the latest of R3trans,R3ta,R3szchk,R3ldctl,tp,sapinst, R3load etc. , the system copy procedure gets through the R3szchk phase, where it was previously aborting. It prompts for SAP instance shutdown and later on the export monitor

Completed 97, failed 61, total 158

INFO 2011-06-17 18:12:05.900

Output of /usr/java14/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m -Xj9 com.sap.inst.migmon.exp.ExportMonitor -sapinst is written to the logfile export_monitor.java.log.

WARNING 2011-06-17 18:17:37.353

Execution of the command "/usr/java14/jre/bin/java -classpath migmon.jar -showversion -Xmx1024m -Xj9 com.sap.inst.migmon.exp.ExportMonitor -sapinst" finished with return code 103. Output:

java version "1.4.2"

Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)

IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 AIX ppc-32 j9ap32142-20080510 (JIT enabled)

J9VM - 20080508_19305_bHdSMr

JIT - 20080424_1845_r8

GC - 200804_28)

ERROR 2011-06-17 18:17:37.358

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

ERROR 2011-06-17 18:17:37.811

FCO-00011 The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|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) export_monitor.java.log, export_monitor.log.).

Below are the logs :

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

ERROR: 2011-06-16 17:47:58 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPAPPL1_57' export package is interrupted with R3load error.

Process '/usr/sap/HEP/SYS/exe/run/R3load -e SAPAPPL1_57.cmd -datacodepage 4103 -l SAPAPPL1_57.log -stop_on_error' exited with return code 2.

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

ERROR: 2011-06-16 17:47:58 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPAPPL1_60' export package is interrupted with R3load error.

Process '/usr/sap/HEP/SYS/exe/run/R3load -e SAPAPPL1_60.cmd -datacodepage 4103 -l SAPAPPL1_60.log -stop_on_error' exited with return code 2.

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

Edited by: basis-novice on Jun 17, 2011 3:05 PM

Edited by: basis-novice on Jun 17, 2011 3:07 PM

former_member185031
Active Contributor
0 Kudos

For mode details see 'SAPAPPL1_6.log' file.

For mode details see 'SAPAPPL1_57.log' file.

Check these log files.

Regards,

Subhash

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Please try with latest version of R3trans, R3ta, TP, R3szchk, R3load and R3ldctl.

Thanks

Sunny

Former Member
0 Kudos

Dear Sunny,

Thanks alot for your reply!

Went ahead with your suggestion, downloaded the latest of all you mentioned.and restarted. The Export hangs during running R3szchk in the Phase 2(Prepare to export ABAP)....

former_member185031
Active Contributor
0 Kudos

If Sapinst is running then definately you would be able to see some temporary file on the installation directory which contains logs. That can only tell you what is going on.

Regards,

Subhash