Skip to Content

In order to keep your BI system healthy, it’s necessary to clean-up some statistical tables once in a while. Especially in BI 7.0, I experienced some tables growing rapidly (e.g. RSDDSTATLOGGING, RSBERRORLOG).

Some of BW Statistics tables are listed below.

RSDDSTATLOGGING    –           Logging Table for OLAP Statistics (new)

RSBERRORLOG           –           (Logs for Incorrect Records) – stores error handling logs.

RSDDSTATAGGR          –           Statistics data BW for aggregate selection and accounting

RSDDSTATAGGRDEF   –           Statistics data OLAP: Navigation step / aggregate definition

RSDDSTATCOND          –           BW Statistics: Data on Condensing Run InfoCube

RSDDSTATDELE           –           BW Statistics: Data on Deletion of Data in InfoCube

RSDDSTATDM              –           Data Manager Query Statistic Records

RSDDSTATDTP –           Table for WHM Statistics. Details DTP

RSDDSTATINFO            –           BW Statistics (OLAP), Information by Navigation step

RSDDSTATEVDATA      –           BW Statistics (OLAP), Key Figures for the Events

RSDDSTATHEADER                 BW Statistics (OLAP), Information by Runtime Objec

 

I am going to discuss about one of such table (RSDDSTATLOGGING) and it’s periodic maintenance.

RSDDSTATLOGGING – Logging Table for OLAP Statistics (new)

RSDDSTATLOGGING is one of the BW statistics data tables which potentially grow very fast, causing problems for users to login/access reports.

If we have short dump issues related to inserts on RSDDSTATLOGGING, then, we have to delete the contents of this table (Of course, business approvals are necessary in established environments)

The option to clear the contents is given below in section 1

For regular maintenance, please check Section 2.

1.    Use Program to delete Statistics data

 Step1 : Get electronic approval from Business(as the case maybe)

Step 2 : Delete contents Using program RSDDSTAT_DATA_DELETE

Step 2.1) Go to se38 and enter program name RSDDSTAT_DATA_DELETE and then click on execute and it will take to next screen

image

In the 2nd screen (see below)

Step 2.2) Select (þ) “Statistics Logging Tables under which data is to be deleted?”, tab (see screen shot below)

image

Step 2.3) Select date/duration under “Date up until which data is to be deleted?” tab. (In the screen shot given above, All option was selected to delete all contents. However, if you want to delete contents by date, go to transaction RSDDSTAT first, and find the appropriate Dates for which you want to run this program to delete contents from the RSDDSTATLOGGING table.)

 

Step 2.4) Ask DB team to run re-org on the RSDDSTATLOGGING table

2.    Regular Maintenance:

 

SAP has delivered the note 1476860 in the similar context.

It will allow us to delete data from this table by Date but also internally by X number of records, doing a commit at the end of each packet. If this note is not delivered as part of your SAP, it need to be applied and the parameter BW_STATLOG_DELPKGSIZE needs to be set to 50000 records in RSADMIN table.

Prerequisite(s):

You have to ensure that your regular statistics chains have executed successfully.

You have to ensure that this activity is performed during a quiet time (ideally on weekends or late Fridays, skipping month end periods)

step 1)       Do an initial reduction of the table using the “Older than 30 Days” option as selection.

step 2)       Monthly, execute the program RSDDSTAT_DATA_DELETE with the same “Older than 30 Days” Option.  (Alternatively, we can also create a variant and include a program step in your weekly chains. This will automate the job for you!!! )

 

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member
    I know very little about BI/BW.   BUT we have a team here who does know a lot about it.

    Pictures, examples, I love them.  I’m sure the team here will as well.

    Thank you for the nice blog.  What can I say about it?  It is written well.  Pictures!  I love pictures, and they are so hard to put in these blogs.

    Warning – I am not a stalker – I am now a follower.  That way I can pass information on.  And if you write anything about ABAP programs, well I can comment on those!

    Michelle

    (0) 
  2. Former Member
    Hey,

    This is good blog. I have same problem, this helped me alot to solve problem.

    I want to know how we can avoid this entries in table. I have seen that program RSB_ANALYZE_ERRORLOG helps us to find which DTP’s are creating more entries, but what is a option by which we can avoid any further entries.

    (0) 
  3. Former Member Post author
    Hi Ganesh,

    Apologies for delayed Response.

    In my view, RSB* is a system table fed by the junk arriving in Error DTP’s. The more the error’s, the more the entries in this table.

    For now nothing strikes to me except to limit the Error DTP’s in your system.Use them in unavoidable circumstances.I reckon some of the EWA reports suggesting the same.

    Regards,
    Nawaz.

    (0) 

Leave a Reply