Skip to Content
avatar image
Former Member

PSAPSR3 is increasing too much - Solution Manager 7.1 sp08

Hi,

In our new Solution Manager 7.1 SP08 (Windows-Oracle)

Configurations in Solman: System preparation, basis configuration and managed system (3 ERP, 3 BI, 3 BIJAVA, 3 PORTAL, 2 SUP, 1 AFARIA, 2 BOBJ, 3 SANDBOX, 1 WPB).

We realized that PSAPSR3 tablespace increase too much every week.

The system went on live on December 2013, and this tablespace have around 170GB of used,

The top grow tables are: (just take a look of objects of PSAPSR3)

SAPSR3 SMD_HASH_TABLE TABLE PSAPSR3USR 24.415,000

SAPSR3 SYS_LOB0000134462C00013$$ LOBSEGMENT PSAPSR3702X 5.060,188

SAPSR3 SYS_LOB0000134462C00014$$ LOBSEGMENT PSAPSR3702X 3.393,188

SAPSR3 D010TAB^0 INDEX PSAPSR3702X 3.014,000

SAPSR3 DSVASRESULTSGEN TABLE PSAPSR3 2.747,000

SAPSR3 SYS_LOB0000124338C00004$$ LOBSEGMENT PSAPSR3702X 2.560,188

SAPSR3 /BI0/PSMD_MEH1~0 INDEX PSAPSR3 2.560,000

SAPSR3 /BI0/SSMD_MEH1~0 INDEX PSAPSR3 2.432,000

SAPSR3 SYS_LOB0000127869C00034$$ LOBSEGMENT PSAPSR3702X 2.176,188

SAPSR3 /BI0/SSMD_MEH1 TABLE PSAPSR3 2.161,000

SAPSR3 /BI0/PSMD_MEH1 TABLE PSAPSR3 1.792,000

SAPSR3 D010TAB TABLE PSAPSR3702X 1.626,000

SAPSR3 SMD_HASH_TABLE~0 INDEX PSAPSR3USR 1.568,000

SAPSR3DB BC_SLD_CHANGELOG TABLE PSAPSR3DB 1.280,000

SAPSR3 BALDAT TABLE PSAPSR3 1.022,000

SAPSR3 /BI0/E0SMD_PEH1 TABLE PSAPSR3 1.020,000

SAPSR3 /BI0/D0SMD_EA2H202 INDEX PSAPSR3 1.008,000

SAPSR3 /BI0/D0SMD_EA2H203 INDEX PSAPSR3 1.008,000

Please your help, how can I control the increase of psapsr3??

I apply this notes, but during this week PSAPSR3 increase in 5GB.

SAP note 1695927 - Cleaning up the change history in the LMDB

SAP note 195157 - Application log: Deletion of logs

SAP note 1874506 - The total size of service session tables is between 10 to 100 Gbytes

Regards

Andy

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 27, 2014 at 02:52 AM

    Hi,

    SAP helped me to resolve this problem.

    The main problem was that two infoobjects 0SMD_MEH1, 0SMD_EA2H, 0SMD_EA2D were increasing anormally, this infoobject recolect java exceptions and around 10000 records were loaded per day, because of this we got TIME_OUT  dumps in the jobs of SM_EWFK user (housekeeping jobs)

    We made many adjustments like deleting data of infocubes, dimensions, etc. and also I followed the recomendations of sap note 1480588 (Section 'Compress Infocube, Delete Requests, Update Statistics) and 1333571.

    Regards

    Andy

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 01, 2014 at 07:36 AM

    Hi

    Have a look to here under note taht will help you to cleanup table SMD_HASH_TABLE.

    Regards

    1958979 - Solution Manager - Tablespace increase

    Open Note 1480588 - Download the file E2E_BI_HK.pdf attached to the note

    Follow the procedure described in pages 7 & 8 the "E2E_BI_HK.pdf" to find out the infocubes that have the largest number of entries in table SMD_HASH_TABLE. After you find the largest infocubes, then you need to create an entry for the largest infocubes in table E2E_BI_DELETE to perform the housekeeping of the old data (page 9) of the "E2E_BI_HK.pdf"

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Yves

      SMD_HASH_TABLE stores in PSAPSR3USR tablespace, I applied sap note 1958979 in order to control the increase of PSAPSR3USR tablespace and works.

      But my proble of volumen data is with PSAPSR3 tablespace, increases around 5GB per week.

      This affects disk space.

      Any idea?

      Regards

      Andy


  • Mar 03, 2014 at 06:14 PM

    Hi

    Sorry I did read you message too quickly.

    The size you provide for these tables is it the total size or the monthly growth ?

    This might be the growth, as these size are not that big...

    For PSAPSR3 the growth is mainly due to 2 tables & index related to solman BI content

    /BI0/PSMD_MEH1

    /BI0/SSMD_MEH1

    Did not find any info about these two, my Solman is down at the moment but i'll check this tomorrow.

    There are some options for DSVASRESULTSGEN

    1874506 - The total size of service session tables is between 10 to 100 Gbytes

    1276584 - Archiving sessions

    BALDAT holds application logs it can be clean using report SBAL_DELETE

    195157 - Application log: Deletion of logs

    Regards

    Add comment
    10|10000 characters needed characters exceeded