Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

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

Former Member
Former Member replied

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

1 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question