deletion of RSBERRORLOG tables takes long time

[chanda]

Dear SAP Guru's,

We have some issues in long running DTP's. It was observed that this is due to the huge RSBERRORLOG table.All the DTP's are taking long time reading this errorlog table.

I asked our basis team to re organize the Table, but they said it is not possible as they have to do it offline .

Firstly may i know how long it takes to reorganize offline , secondly can it be done online ?

As an alternative option our basis team wanted to delete the requests based on 15days requests starting from January 2013. It was observed that even after 24hrs there are no changes . ofcouse did not hit any dump.

Also during this period we observed our daily loads have impacted , i mean the daily running process chains were taking long time . We are not sure if the program RSBM_ERRORLOG_DELETE has an impact on other BW processes, like loading and reporting?

Kindly provide us a solution.

we are currrently running on BI7.0 support pack 19.

Thank you and regards,

Chanda.

[AtulKumarJain · Accepted solution]

Hi ,

You can perform online reorg for this.

6.  How does an online reorganization with BRSPACE work?

    You start an online reorganization of tables or entire tablespaces
    using the BRSPACE function TBREORG as described in Note 646681.
    During reorganzation, BRSPACE carries out the following steps:

    o  BRSPACE uses DBMS_REDEFINITION.CAN_REDEF_TABLES to check whether
       the selected tables can be reorganized online.

    o  It increases the DB_FILE_MULTIBLOCK_READ_COUNT parameter to 128,
       to ensure an optimal Full Table Scan performance (see Note
       806554).

    o  It determines the CREATE TABLE statement and the CREATE INDEX
       statement for creating target segments with
       DBMS_METADATA.GET_DDL.

    o  It determines dependent objects such as grants, constraints,
       triggers and comments using DBMS_METADATA.GET_DEPENDENT_DDL.

    o  It creates the target table with the naming convention
       <source_table>#$.
                                                                
    o  It exports statistics of the source table using
       DMBS_STATS.EXPORT_TABLE_STATS.

    o  It calls DBMS_REDEFINITION.START_REDEF_TABLE (the central
       function of the DBMS_REDEFINITION-package).

       -  It waits until all open changes are closed on the table to be
          reorganized.

       -  It copies the source table data into the target table.

       -  It logs all changes to the source table until the later
          DBMS_REDEFINITION.FINISH_REDEF_TABLE in a Materialized View
          Log (MLOG$_<source_table>), which is created in the
          default-tablespace of the user.

   o  It creates indexes on the target table in accordance with the
      naming convention <source_index>#$.

   o  It imports the previously exported statistics for the target
      table using DBMS_STATS.IMPORT_TABLE_STATS. (with BRSPACE 6.40
      (below 49), 7.00 (below 34) and 7.10 (below 10), this step was
      performed at the end after renaming the indexes.)

   o  It finishes the online reorganization using
      DBMS_REDEFINITION.FINISH_REDEF_TABLE:

      -  It copies the changes to the source table that occurred during
         the online-reorganization.

      -  It swaps the names of the source table and the target table.

   o  It drops the source table.

   o  It changes index names from <index_name>#$ to <index_name>.

Please check sap note for more information SAP Note No. 541538

BR

Atul

[chanda · Accepted solution]

Dear Atul Jain,

Thank you for the detail explaination.

I understand from the above that online reorg can be done.

May i know if this has any impact on other BW operations like loading and reporting time?.

When our team tried to do it yesterday i noticed the loading time was more than normal for some process chains. I suspected its because of errorlog deletion process , But also we run for 24hrs and no change/ log . As if it was struck  there. Hence we had to kill the job.

RSBERRORLOG table size is 355GB and we are just thinkig on how to delete it in the best possible manner.

Thank you ,

Chanda.

[Former Member · Accepted solution]

Hello,

you have been facing in consistancy in table RSBERRORLOG.

I just opened it via SE16, marked all records and used the

"delete all" function from the menu.

The table RSCOMPTLOGO contained an inconsistent entry:

APPLNM              PARENTNAME          CHILDNAME NEXTNAME

HYBR                NODESNOTCONNECTED

NODESNOTCONNECTED                       HYBR      NODESNOTCONNECTED <<<

Warm Regards,

Prabaharan B

[chanda · Accepted solution]

Dear Prabhakaran,

You mean inconsistency causes it to lun very long? If so how should i be overcoming this problem.

kindly advise.

Thanks & regards,

Chanda.

[Former Member · Accepted solution]

Hello,

Goto se16-->enter table name-->sele table content--->delete table content

WR,

PHB

[chanda · Accepted solution]

Hi Atul,

Re organisation worked.

Probably its was because we were on a lower suport pack and the table being huge , it was unable to re org for days.

We have upgraded to latest support pack - BI7.0 Support Pack 31 and deleted all the entries from the error log table and re org was successful and the DTP performance improved considerably.

Hope this should be a continuous monitoring process.

Hi Prabhakaran,

Even after deleting the table , no change was observed in DTP loading .

Thanks for the input and time.

rgds,

chanda.