Page tree
Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify the understanding of the system logic and requirements in relation to increasing table size of RSOTLOGOHISTORY.

Overview

This Wikipage contains relevant information in regard to increasing table RSOTLOGOHISTORY. First, the structure of the table will be presented, this followed by root cause of the increase. Last but not least, a smaill deletion report will be provided to delete unnecessary entries from the table.

The table RSOTLOGOHISTORY

The SAP BW System Table RSOTLOGOHISTORY contains the metadata of object versions.  

Example:

 

The table contains the Object Name, Object Type, Version Number, Language, Date, Time, Request/Task, Author, TLOGO Version Origin and Content of Serialised Objects.

Why is it increasing?

An unexpected growth of the table RSOTLOGOHISTORY is usually caused because BEFOREACT is filled with an 'X' . At each object activation (InfoObject, Cube, DataStore, etc.) a historical version of the model is generated and stored.

 How is it possible to avoid this?

  Delete 'X' entries from column BEFOREACT. You can do this in transaction SM30. Afterwards the table should look as showed below:

Is it possible to delete unused entries?

 For deleting unnecessary entries from table RSOTLOGOHISTORY use the following report:  

Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'
REPORT ZDELHISTORY.
 PARAMETER: tlogo TYPE rstlogo, dstart TYPE dats.
 DELETE FROM rsotlogohistory WHERE objtype = tlogo AND versdate <= dstart.

Related SAP Notes/KBAs

SAP Note 1943604: Increasing size of table RSOTLOGOHISTORY

  • No labels