Skip to Content
avatar image
Former Member

BDLS - How to monitor the process?

Dear All,

I am running the BDLS sessions in Background (excluding the known huge tables) now in my Testing System just after the system refresh activities from Production to the Testing.

The BDLS sessions run more than 22 hours (still in progress now ) , may I know where ( which tcode ) I can see the progress of the BDLS?

I've tried to check in Txcode SM50, the BGD process performing a sequential read on a table for more than 8 hours...Is it possible hang in somewhere ? May I know how to determine if the BDLS is 'hang' ?

FYI, the table size that the BDLS running on is around 140GB..

Best Regards,

Ken

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

10 Answers

  • avatar image
    Former Member
    Feb 23, 2010 at 03:36 AM

    You can check the log for progress

    t-code SLG1, object CALE, subobject LOGSYSTEM*.

    -Sekhar

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 07, 2010 at 07:10 PM

    Ken,

    I started a BDLS run that took over 80 hours so I feel your pain. And like you, I couldn't find any adequate logging to tell me what was going on. As I searched, I found the new BDLSS transaction. Even though I started the run with BDLS, I could still see some limited logging in BDLSS [Display Log].

    The next time I ran, I used BDLSS [Display Log] and got a bit more info. I could at least watch it go alphabetically through it's list of tables and when I saw the VBA* tables in the log, I knew it was at least getting to the end of the initial scan.

    My next refresh for BI is in May. I have until then to figure out a better way to run this more efficiently. 😊

    Good Luck,

    Richard

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 23, 2010 at 03:51 AM

    Dear sekhar,

    There is no log in the SLG1.

    Between, I thought the logs will be generated only after the BDLS is done?

    Best Regards,

    Ken

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 23, 2010 at 09:25 AM

    Dear Raja,

    There is not entries in table : BDLSEXZ when I view via SE16.

    Best Regards,

    Ken

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Wen,

      Am extremely sorry the table BDLSEXZ is to exclude the tables while doing BDLS conversion.

      You need to check the log at the transaction BDLSS.

      Pls chk and let me know the status.

      Regards,

      Raja. G

  • avatar image
    Former Member
    Feb 23, 2010 at 11:57 PM

    Dear Raja,

    the log i get from BDLSS shows the table processed until :s

    .

    .

    .

    CATSHR EXTSYSTEM 0

    LOGSYS 0

    CATS_BW_TIME I_RLOGSYS 0

    CATS_GUID_KEY* EXTSYSTEM 0

    CBPR LOGSYSTEM 0

    CC1ERP SRCSYS 0

    CCMCTIADMIN LOGSYS 0

    Dear sekhar,

    Do you meant the job log from SM37 ? :

     
    22.02.2010 09:59:19 Job started                                                                         00
    22.02.2010 09:59:19 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID BASISADM7)      00
    22.02.2010 09:59:19 The new logical system name T00CLNT300 is assigned to the current client 300        B1
    

    Edited by: Wei Jian Kwan on Feb 24, 2010 1:00 AM

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 24, 2010 at 01:13 PM

    Yes,,,sometime BDLS hangs....You can check the table from Sm50.

    To make BDLS faster you can create index on LOGSYS field on that table. You should also run BDLS in no archivemode.

    Regards

    Anindya

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Running the Statistics on Database may help some time, you can run this while your other processes running on system

  • avatar image
    Former Member
    Apr 07, 2010 at 05:15 AM

    Hi there !!!

    You can monitor the BDLS statastic with table BDLSPOS ..

    Hope you will get the ans from this.

    Regards,

    Utpal Patel

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 07, 2010 at 05:24 AM

    Dear Utpal Patel,

    Thanks for your reply.

    However, in this table : BDLSPOS seems like doesnt shows all the table right ?

    For example, i can't see the common table like VBRK, VBAK, ....etc.........

    Best Regards,

    Ken

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 09, 2010 at 04:34 AM

    Hi All,

    Note down the tables which is taking long time or huge in size and buid the index prior to BDLS. You can drop these index after the BDLS. This has helped me well.

    Hope this helps.

    Cheers

    Gopal.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Ken,

      The RBDLS2LS report displays the same screen as BDLS.I am not aware if there is some release constraint for this report.

      I will let you know if i find something on this.

      Thanks,

      Shashank

  • avatar image
    Former Member
    Jun 17, 2010 at 05:00 PM

    Hi,

    1. run the report RBDLSMAP_RESET to clear up old or last stuck BDLS run.

    2. have the temp index created for the tables which are identified as huge and contains the fields (AWSYS, LOGSYS, SNDSYSTEM, RCVSYSTEM, etc.,) - this can be identified if you do a test run or write a code snippet to identify such tables.

    3. After the indexes are created - execute the report RBDLS2LS (through SE38)

    4. Normal BDLS screen appears - here, enter the table range

    5. After executing the RBDLS2LS report for the first time in the system, it creates a new report RBDLS<client.no.>

    6. Now, use the report RBDLS<client No> to schedule the BDLS further (this allows parallel run as well).

    We are trying this out now and it has a significant improvement in saving the BDLS run time. This approach is a must for systems with are in TB size.

    Add comment
    10|10000 characters needed characters exceeded

    • John,

      I like the possibilities of this post and the timing is perfect. I have a 6TB refresh next week and it's our slowest for BDLS conversion. There is a new BDLSS transaction that has two steps to it. The first step scans all of your tables that contain LOGSYS to see if any rows have data in the field. The second step updates only the tables that are relevant (the actual update part is fast). So under this process, I can see how some might say excluding tables is irrelevant because the first scan phase is identifying the only tables that are relevant.

      However, the scan to see which tables needs updating takes forever if you're like us and have millions of rows in some tables. The good news is that I can take the results from the last run and identify many of these monster tables that aren't using their LOGSYS in any way and try to exclude them from the initial scanning step. That has the possibility of saving me lots of time.

      Currently, my BDLS will run for several DAYS if I just let it scan everything. I'm going to try your approach on our ECC 6.0 (Basis 7.0 SP19) system and see just how much I can trim my times down. Last time, it ran for over 3 days just to find 9 tables that need a few thousand rows updated. It was a huge waste of time.

      Thanks,

      Richard

      Georgia-Pacific