MIGMON starts only after several hours

[Former Member]

Hello guys,

i have a strange Problem.

I did the ABAP import via migmon (import monitor) several times without any problems. But now i have a strange behavour.

We have an Oracle ExaData with OEL 6.6 and i need to import a dump, where the exchange directory has no files in it.

So i configured our migmon like this:

importDirs=/sapmnt/Export_WB1_Neu/NB1/export/ABAP

installDir=/app/bin/sap/tmp/EB1_Import_20160517/sapinst_instdir/NW740SR2/ORA/COPY/SYSTEM/DISTRIBUTED/AS-ABAP/DB

orderBy=size

ddlFile=

ddlMap=

monitorTimeout=30

r3loadExe=

tskFiles=yes

extFiles=no

dbCodepage=4103

migrationKey=**********

omit=

taskArgs=

loadArgs=-nolog -c 10000000 -loadprocedure fast

jobNum=20

exchangeDir=

localhost=

port=

trace=all

mailServer=

mailFrom=

mailTo=

After i started the migmon he logged following output in the import_monitor.log:

INFO: 2016-05-17 15:27:06

Import Monitor is started.

CONFIG: 2016-05-17 15:27:06

Application options:

dbCodepage=4103

dbType=ORA

ddlFile=

ddlMap=

exchangeDir=

extFiles=no

importDirs=/sapmnt/Export_WB1_Neu/NB1/export/ABAP

installDir=/app/bin/sap/tmp/EB1_Import_20160517/sapinst_instdir/NW740SR2/ORA/COPY/SYSTEM/DISTRIBUTED/AS-ABAP/DB

jobNum=20

loadArgs=-nolog -c 10000000 -loadprocedure fast

localhost=

mailFrom=

mailServer=

mailTo=

migrationKey=1WUge5M50D401eqteaM01aa1

monitorTimeout=30

omit=

orderBy=size

port=

r3loadExe=

taskArgs=

trace=all

tskFiles=yes

CONFIG: 2016-05-17 15:27:06

List of packages with table structure: 'SAP0000'.

CONFIG: 2016-05-17 15:27:06

List of packages with views: 'SAPVIEW'.

TRACE: 2016-05-17 15:27:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of '/app/bin/sap/tmp/EB1_Import_20160517/sapinst_instdir/NW740SR2/ORA/COPY/SYSTEM/DISTRIBUTED/AS-ABAP/DB/DDLORA.TPL' template file is started.

INFO: 2016-05-17 15:27:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of '/app/bin/sap/tmp/EB1_Import_20160517/sapinst_instdir/NW740SR2/ORA/COPY/SYSTEM/DISTRIBUTED/AS-ABAP/DB/DDLORA.TPL' template file is successfully completed.

Primary key creation: after load.

Index creation: after load.

INFO: 2016-05-17 19:39:18

Data codepage 4103 is determined using TOC file '/sapmnt/Export_WB1_Neu/NB1/export/ABAP/DATA/WBCROSSGT-9.TOC' for package 'WBCROSSGT-9'.

INFO: 2016-05-17 19:39:18 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report

Monitor jobs: running 1, waiting 736, completed 0, failed 0, total 737  Package Group  max threads: 20 current running threads : 0 processing package: REPOSRC

And you see that between step com.sap.inst.migmon.imp.ImportStandardTask preCreate and the really starting import, he has a delay of nearly 4 hours where nothing happend for my point of view.

We had this behavior with 2 hours, 4 hours and also 5 hours delay.

Another export, which has also the exchange files, started immediate.

So what is the failure here?

Regards

Sascha

[Former Member · Accepted solution]

Hi Stefan,

thanks for your reply. I found out that the parameter "orderBy=size" was the time eating parameter. If set it to orderBy=name or leave it blank. He starts directly with the import.

Another option would be "orderBy=size" and "ignorePackageSizeCalculation=true".

Regards

Sascha

[stefan_koehler]

Hi Sascha,

i am a little bit confused as you wrote: "We have an Oracle ExaData with OEL 6.6 and i need to import a dump, where the exchange directory has no files in it. Another export, which has also the exchange files, started immediate."

Once you are talking about import (with no files in exchange directory) and then you are talking about an export with exchange files for comparison.

However is there any activity on database level between step com.sap.inst.migmon.imp.ImportStandardTask preCreate and starting the import? If not what is strace or Java Flame Graphs telling you on application level? Time can only be spent on database level or application level.

Regards

Stefan