Skip to Content
avatar image
Former Member

Performance issue BALDAT

Hi Gurus,

Last night, in our CRM system around 100 of users got stuck while accessing BALDAT table.In sm66,there was sequential reads for this table for around an hour or so and thus affecting performance.In sm13,several updates for the table was in initial status,

We manually cleared the updates,restarted work process,cleared application log,ran optimizer stats to clear the processes.

Could you please share what caused the issue and how to avoid it?In some forums its advised to deactivate the logging and could find notes for reorganizing the tables.What is recommended.Please suggest.

Thanks

Sabya

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Dec 25, 2014 at 02:59 PM

    Merry Xmas to all of you.

    Hi Sabya,

    Based on your earlier observations I have provided certain guidelines below. Please follow them to get more information to help identify the root-cause:

    Last night, in our CRM system around 100 of users got stuck while accessing BALDAT table.In sm66,there was sequential reads for this table for around an hour or so and thus affecting performance.

    => 1. Since all the work processes are active in  performing read operations, check DBACOCKPIT/DB command level on what the DB sessions were waiting for? for example, db file read. If the sessions were waiting for a specific SQL access, tune the SQL statement.

    => 2. BALDAT is one of  the Basis administrative tables from which data volume could be reduced to maintain optimal performance, please refer to SAP Note 195157 'Application log: Deletion of logs' (part of 706478)

    Also, after removing significant volume of data, it is suggested to perform table reorganization if you have deleted major chunk of data. Check the storage quality of the indexes and rebuild them periodically to avoid performance issues due to index fragmentation.

    => 3. Check whether all of the users that were stuck were performing same SAP transaction/program, and check on individual transaction performance from ST03/DB historical statistics

    => 4. Make sure that the application log deletion program does not run in period when there is heavy updates on BALDAT occur in the system: reschedule the reorg program to a later time accordingly

    In sm13,several updates for the table was in initial status,

    => 5. Did you check if the Update server was active (SM14 or link from SM13 to Update Administration), if it was not active it would represent a core DB issue stopping all the Update activities in system. Analyze the DB logs (alert log in case of Oracle) for errors.

    => 6. If the Update server did not have any issues, this would mean a blockage of all Update work processes in certain operations -> please check what the processes were doing: if these were reading BALDAT , please work on point 1.

    Regards,
    Karthik

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 24, 2014 at 11:55 AM

    HI Sriram,

    Sorry for late reply.Please find the attached dump,size of BALDAT table is 3 GB

    Thanks

    Sabya

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Sabya

      1. When this issue happened, your system will goes to deadlock status(Lock entries table getting full), because of this you are getting more Time out dumps in ST22.

      2. Is any one accessing the Database level to read/write / modification ?

      BR

      SS

  • Dec 24, 2014 at 05:44 AM

    Hi Sabya

    1.  Is this any dumps? If it is yes pls share the full dump

    2. Could you check the SM21 system log any errors ?

    BR

    SS

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 24, 2014 at 03:05 PM

    Hi Sabya,

    Could you share SM21 logs for analysis.

    Regards,

    Gaurav

    Add comment
    10|10000 characters needed characters exceeded