cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BDLS runtime/performance

Former Member
0 Likes
2,442

hello - has anyone came up w/ some ways to improve BDLS runtime/performance? we have an 4.7 system on Oracle that is about 8TB allocated. BDLS is taking a long time....over 1 day and still running

any idea on how much changing the #entries/commit will help? default is 1 million records/commit....wondering how high i can go, and how much , if any, that would help

thanks

View Entire Topic
anindya_bose
Active Contributor
0 Likes

I do two thing to make BDLS conversion faster in our system.

1. Switch of the Archive log mode of database. During BDLS lots of archive logs get generated, to switching to noarchive mode always make it faster.

2. Create index on some large table where I think it could take much time.

It is possible to exclude some tables if you are sure that you do not need those tables in the test system,

Check https://service.sap.com/sap/support/notes/932032

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!

Former Member
0 Likes

There is already good advice here so far. Two more things:

It may be helpful to create specific indexes to speed up large tables. But to do this database knowledge is needed for example on oracle create index with parallel nologging (maybe compressed).

There is also a possibilty in doing parallel BDLS, check this blog: [Execute conversion of logical system names (BDLS) in short time and in parallel - Intermediate|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4796] [original link is broken] [original link is broken] [original link is broken];

I have used the both ways so far, careful testing is needed. Good luck.

Regards, Michael

anindya_bose
Active Contributor
0 Likes

>It may be helpful to create specific indexes to speed up large tables. But to do this database knowledge is needed for example >on oracle create index with parallel nologging (maybe compressed).

Sorry, I should have explained the index creation procedure for a particular table. Here is the procedure.

Say the table is RSSELDONE, we generally create index for field LOGSYS because RBDLSMAP search for this field.

Go to SE11-Enter the database table name->Click on "Display"-->Click on "Indexes"--->Click on "Create" buttong

Enter any name (say ZSS) >maintain in logon language->Enter "LOGSYS" in the fieldname>Enter some description>Click ok. then Save and Activate.

Hope this will help.