BDLS taking a long time to run?

Details

Category: Basis

Published on Wednesday, 19 March 2008 11:40

Written by Anon.

Hits: 17059

Read the following tips...

With regard to excluding certain tables from the BDLS run I would
suggest that you make sure that you absolutely do not need these tables
when using ALE communication between systems in the future as this will
cause inconsistencies.

It is possible to exclude tables from BDLS. To do this, you can
either do it maually by making the required entries in the table
'BDLSEXZ' as specified in note 932032.

OR

You can select the tables to be converted by entering the
objects (the tables you actually do want converted) in the
Tables for Conversion selection screen in Set Parameters in Tx
BDLS and leave out the tables you don't want converted.

There are 3 stages when running BDLS ->
1) Determining tables which have to beconverted
2) Generating conversion programs
3) Running the conversion program to do the conversion

For many tables the runtime will be long.
We recommend you start BDLS always in the test mode first - then you
can check which tables are to be converted.
Please review the following very important information with regard to
this utility and how to optimise it's performance and usage:

The conversion can take very long (a few days etc.) if the relevant
tables do have many entries (e.g. COEP is always a problem). The
bottleneck of the conversion process is always the database access, not
the report!

One thing I would strongly recommend is that you run this report in
parallel. What this in effect means is to start the report several timeswith
distinct tables - for example one report only for table GLPCA, one
for table COEP and maybe one run for the rest.

With release 620, tx BDLS was changed by using a new design and
technique. With the new BDLS in 620 parallel processing was
for same pairs of names was removed.

But the old BDLS and so the function of parallel processing is still
in your system and you can use it. There are no disadvantage to use it
because the change from one to another is the same way. But the old
version you can't run by using tx BDLS.

Please run the report RBDLS2LS direct. It is the old BDLS that you
already know. During the first start
a report RBDLSxxx (xxx-client) is created. That you can use direct
for the conversion and also for parallel runnings.

With regard to remaining references to the old logical system names
after the execution of BDLS note the following:
What transaction BDLS does is it looks for all references to fields of
data type "LOGSYS" and "EDI_PARNUM" and changes these values to the new
logical system name (from the old one). Hence even though the above
referenced tables may refer to the old logical system name these
names will only be converted if their data type is either "LOGSYS" or
"EDI_PARNUM". All other field references to the old logical system name
have to be changed manually and will not be included in the BDLS
conversion.

I have attached the following note on the BDLS utility:

What I would suggest is to read this note and the online documentation
BDLS. Also run BDLS in test mode first as this basically writes a
catalogue of the changes to be made and subsequently should improve
the live runtime of the utility.
You can exclude tables do not contain the Logical System
names from the BDLS run. However it is your responsibility to ensure
that you properly identify tables which can be excluded (to avoid any
data inconsistencies).

• < Prev
• Next >