OSDB Migration:Import ABAP running from long time

[Former Member]

Dear Experts,

We are Migrating our ECC6EHP4 system from Solaris5.10 with Oracle 11G to RHEL 6.4 with MaxDB 7.8.02 and the DB Size:480 GB, and we are facing issues in Import ABAP Phase as below: Please help us

we have started the Import ABAP phase by importing packages in order by size

The import ABAP job of package BSAS,D010TAB,SAPSSEXC_2 is running from more than a day and it is not writing any logs and some times it is writing logs after several hours  and it is not throwing any error.

we have checked the DB side there is sufficient Data area and log area is available and there is no issue from DB side.

Please help in this case what we can do analysis from the DB side or SAP import side. We have used the source and target systems same kernel with latest R3load, R3ldctl,R2Szchck patches. in this case what we can check the other logs if any thing is available please help us

Regards,

Samba

[JamesZ]

Hi Samba,

I have met such kind of problems many times. Most of cases the bottleneck points to database, but please note it is very hard to prove the bottleneck is really from database. So here we suppose the bottleneck is from database, please log on database server and provide me with all.prt file:

x_cons <dbsid> show all > all.prt

Best regards,

James

[Former Member]

Hi Samba,

Also can you please let us know how many MAX_CPU,CacheMemorySize  MAXUSERTASKS you have defined for the DB.

Also have look on below oss note for performance issues & Parameter recommendations:-

1006491 - MaxDB on Linux (NUMA): Performance problems with MAXCPU > 1

1308217 - SAP MaxDB 7.8 database parameter recommendations

Regards,

Ram

[Former Member]

Dear James,

I have checked the parameter you have suggested and that is not showing any results.

Please check the below:

x_cons RQA show all > all.prt

Please suggest what else we can check and analysis in this case, actually while importing large size of tables like RFBLG,DBATABLOG,ACTIT, those are successfully Imported within less time only, but when it comes to the importing of BSAS,BSIS and D010TAB packages it is still importing from more than a day.

Regards,

Samba.

[Former Member]

Hi Ramkrishna,

Actually we are performing the test migration from Pre Production server data , and the Target server contains 4 CPUS out of that we have assigned 3 for MAXCPUS, where as source Preproduction also contains 6 Cpus .

Please check the below and suggest:

CacheMemorySize   498432

MaxUserTasks       100

MaxCPUs         3

UseableCPUs          3

Regards,

Samba

[JamesZ]

Hi Samba,

Please attach all.prt file.

Best regards,
James

[Former Member]

Dear James,

Actually I have medium knowledge on MaxDb Database, as per your suggestion i have executed the command x_cons RQA show all > all.prt , please see the attahed all.prt file and suggest.

Regards,

Samba

all.txt.txt.zip

[JamesZ]

Hi Samba,

The file shows suspend reason:

IOWait(R)(041) :  398021 (  50.82% ) b13get_node: await read              😞

If the import bottleneck is due to database (which not confirmed yet), then you may need to check io.

If io speed is ok.

Best regards,

James

[Former Member]

Hello Samba,

Please increase following parameters size in target system till migration.

• abap/heap_area_total
• abap/heap_area_dia
• abap/heap_area_non_dia

You can consider increasing dialog work process too.

Regards

Anand

[Former Member]

Hi Anand,

still we are in the process of Import ABAP only, after that only instance specific will be created na, now our concerns is on R3load and the DB side optimization. In R3load side I have done correctly but only still I am suspecting some changes has to be done from DB Parameter side, But I am new to Max DB that's why unable to get the more analysis on DB side. if u know some thing please help us how to resolve the long running packages.

we have given import option as order by loading of packages in size wise and it has taken less time to load into the database of packages contains huge data , but it is hanged  in some medium size packages and it is writing logs after several hours & import is running very very slow

Regards,

Samba

[Former Member]

Hello Samba,

Have you checked updating DB stats before importing.

I believe you can stop current process----> update stats---> and continue.

This will improve your DB performance.

Regards

Anand

[Former Member]

Hello Samba,

where you able to resolve the issue.

Let us know if you have resolved it with solution.

Regards

Anand