Symptom
During upgrade using SUM DMO option in SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_MIG_DT_RUN phase ends with below error.
Tables which can be affected and have already been seen in connection with this error are: CDCLS, DOKCLU, RFBLG, KOCLU, EDI40, REGUC, KONV in general all of the SAP cluster tables are candidates.
Directory: <DIR_PUT>/SUM/abap/log
Name: EUMIGRATEDTRUN.log
4EETQ105 Further processes can't be started due to 2 failed ones, so stopping!
1 ETQ000 ==================================================
2 ETQ102 Finished execution of 4 process(es).
2 ETQ108 Analyzing logs for errors.
3 ETQ114 Analyzed 4 log files.
2EETQ109 Found 4 errors in logs and 0 missing logs.
2EETQ106 2 processes failed.
1EETQ399 Export task 'migrate_dt/MIGRATE_DT_00001_EXP.CMD' has errors, exit code 2. Check 'migrate_dt/MIGRATE_DT_00001_EXP.LOG'.
1EETQ399 Import task 'migrate_dt/MIGRATE_DT_00001_IMP.CMD' has errors, exit code 2. Check 'migrate_dt/MIGRATE_DT_00001_IMP.LOG'.
1EETQ399 Export task 'migrate_dt/MIGRATE_DT_00040_EDI40_EXP.CMD' has errors, exit code 2. Check 'migrate_dt/MIGRATE_DT_000XX_EDI40_EXP.LOG'.
1EETQ399 Import task 'migrate_dt/MIGRATE_DT_00040_EDI40_IMP.CMD' has errors, exit code 2. Check 'migrate_dt/MIGRATE_DT_000XX_EDI40_IMP.LOG'.
1EETQ399 Finished execution of buckets with rc = 7.
1 ETQ000 ==================================================
3 ETQ399 Threshold for statistics and duration file: 300 sec import/export time
2 ETQ399 Total import time: 0:19, maximum run time: 0:10.
2 ETQ399 Total export time: 0:24, maximum run time: 0:13.
2 ETQ399 Average exp/imp/total load: 1.8/0.9/2.8 of 40 processes.
2 ETQ399 Summary (export+import): time elapsed 0:13, total size 4619 MB, 355.31 MB/sec (1279.11 GB/hour).
3 ETQ399 Bucket evaluation, sorted for decreasing import speed.
1EETQ399 Last error code set is: Found 7 aborted processes/errors in log files.
Found 2 failed export processes
Found 2 failed import processes
1EETQ203 Upgrade phase "EU_CLONE_MIG_DT_RUN" aborted with errors
=========================================================================
MIGRATE_DT_000XX_RFBLG_IMP.LOG:
(BLD) INFO: kernel release 745 [UNICODE]
(BLD) INFO: data format 1.10
(BLD) INFO: patch number 400
((LOG) INFO: log format: classic
(DB) INFO: Connected to DB
(HDB) INFO: HANA Kernel version 1.00.122.09.1493036600
(HDB) INFO: SQLDBC 1.00.102.04.1453734118
(MIG) INFO: (GSI) vname = 'HDB'
(MIG) INFO: (GSI) release = '1'
(MIG) INFO: (GSI) version = '7'
(MIG) INFO: (GSI) machine = '00CFE2AF4C00'
(HDB) INFO: Loading data in table "RFBLG" with DBSL
(IMP) INFO: Starting import for object "RFBLG" of type
(HDB) INFO: RFBLG deleted/truncated
(HDB) INFO: BSET deleted/truncated
(HDB) INFO: BSES deleted/truncated
(HDB) INFO: BSEG deleted/truncated
(HDB) INFO: BSED deleted/truncated
(HDB) INFO: BSEC deleted/truncated
myCluster (255.11.Imp): 8763: premature end of cluster item encountered.
myCluster (255.11.Imp): 8765: deviation detected in key field 3 of 4.
myCluster (255.11.Imp): 8766: page last read : #0.
myCluster (255.11.Imp): 7955: missing physical pages (pgs rem = 1).
myCluster (255.11.Imp): 6444: decompression of cluster item failed.
myCluster (255.11.Imp): 6454: received return code 2 from G_deca.
myCluster (255.11.Imp): 4427: received return code 2 from decompression routine.
myCluster (255.11.Imp): 3304: failed to unpack cluster item.
myCluster: RFBLG **010****6231****8404022524****2013**
myCluster (255.11.Imp): 572: error during conversion of cluster item.
myCluster (255.11.Imp): 575: affected physical table is RFBLG.
(CNV) ERROR: data conversion failed. rc = 2
(IMP) ERROR:
(IMP) ERROR: Aborting job, because data import task has failed while running over socket/pipe
(IMP) ERROR: (we will not be able to recover from the consequent 'out-of-sync' error)
(IMP) ERROR:
=========================================================================
Read more...
Environment
SAP ERP, SAP NETWEAVER, DMO
Product
Keywords
SUM, DMO, KOCLU, EDI40, REGUC, KONV, CDCLS, DOKCLU upgrade, HANA, conversion, cluster, Oracle, migration. , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview