cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle Migration to DB2 - Export of BSIS

Former Member
0 Kudos

Hi All,

We are currently in the process of database migration from Oracle to DB2. We are using the SAPInst program to carry out the process and are experiencing performance issues when extracting the BSIS table in comparison with our other tables.

The BSIS export is estimated to create around 22 files, each of 665mb or thereabouts. We had to stop the export of data from our production system as each file was taking between 2 and 3 hours to complete.

When we compared this with the creation of other files from similar sized tables, this time was abnormally long (other files of the same size for similar sized tables were written in approximately 20-30mins).

Can anyone give any pointers as to why this would be the case...or has anyone had similar issues and found a solution?

Thanks in advance!!

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_koehler
Active Contributor
0 Kudos

Hello Michael,

of course the BSIS is one of the biggest in almost of SAP systems.

We have faced performance problems on all big tables and have done the export with the distribution monitor, but in your case the migration monitor should solve the problem (if you are facing no cpu problem while running other export packages).

At first we have to clarify some things to help you:

1) How big is your table BSIS (count of rows and mb size)

2) Are you exporting sorted or unsorted?

3) Did you already use the package sap_r3load to define the access pathes for the table? (if not have you already checked the execution plan of the select statement?)

Thanks and Regards

Stefan

andreas_herzog
Active Contributor
0 Kudos

yup - i remember having the same issue concerning table BSIS...it took hours to complete even when it was the last r3load process...

try to split the table using <b>tablesplitting</b> within sapinst and executable <b>r3ta</b> in order to distribute the load to different r3load processes and thus run in parallel...in order to achieve this use <b>migration monitor</b> as the export option...the export will halt after having run r3ldctl and r3szchk, then you will be able to <b>split the table</b> BSIS <b>using r3ta</b> and afterwards you can <b>start the export using migration monitor</b>

GreetZ, AH

Former Member
0 Kudos

Thanks Andreas,

I will give this a try and let you know the result...this could well cut the processing time significantly.

Thanks