on 03-28-2014 3:23 PM
Hi ,
Our environment BI server PSAPSR3 TABLE SPACE size growth high. Please find below figure and help me.
Date | Tablespace name | Size [MB] | Chg.size [MB] | Free [MB] |
01.03.2014 | PSAPSR3 | 7,097,066.00 | 0 | 443,048.13 |
01.02.2014 | PSAPSR3 | 7,097,066.00 | 0 | 586,538.13 |
01.01.2014 | PSAPSR3 | 7,097,066.00 | 0 | 739,218.44 |
01.12.2013 | PSAPSR3 | 7,097,066.00 | 0 | 938,937.50 |
01.11.2013 | PSAPSR3 | 7,097,066.00 | 0 | 1,228,713.88 |
01.10.2013 | PSAPSR3 | 7,097,066.00 | 0 | 1,342,750.63 |
18.09.2013 | PSAPSR3 | 7,097,066.00 | 0 | 1,399,346.31 |
Find top table & index size.
Name | Type | Tablespace | Size [MB] |
/BIC/AZRT_GL_200 | TABLE | PSAPSR3 | 336,900.00 |
/BIC/AZPOSDLA00 | TABLE | PSAPSR3 | 206,616.00 |
/BIC/AZRT_O0500 | TABLE | PSAPSR3 | 172,798.00 |
/BIC/AZOPRSCL200 | TABLE | PSAPSR3 | 161,988.00 |
/BIC/AZRT_GL_200~0 | INDEX | PSAPSR3 | 157,462.00 |
/BIC/EZRTIC_03 | TABLE | PSAPSR3 | 149,978.00 |
/BIC/EZRTIC_03~P | INDEX | PSAPSR3 | 112,752.00 |
/BIC/AZPOSDLA00~0 | INDEX | PSAPSR3 | 107,385.00 |
/BIC/AZRT_GL_200ZG | INDEX | PSAPSR3 | 96,038.00 |
/BIC/AZRT_GL_200Z1 | INDEX | PSAPSR3 | 93,742.00 |
/BIC/EZPOS_LDAF | TABLE | PSAPSR3 | 78,317.00 |
/BIC/EZRT_SCEF~P | INDEX | PSAPSR3 | 72,714.31 |
/BIC/PZRT_LT~0 | INDEX | PSAPSR3 | 69,716.38 |
/BIC/AZPOS_DSG00 | TABLE | PSAPSR3 | 68,550.00 |
Thn.
MS
I don't consider this as a problem. SAP and the Oracle database is working as designed.
If you are worried about the size of the database objects then the only solution is to contact the BW team or a BW Consultant and ask for clarification. If the data is required then all you can do is extend the PSAPSR3 tablespace. If there was a heavy data load lately then it must be the reason. The only recommendation is to consult with the BI team.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manas,
As it is BI system, firstly look for housekeeping from the application front.
For eg: deletion of unwanted cubes, compression of data into cubes, creating aggregates wherever possible etc.
Secondly you may look into clearing of PSA tables which also occupy enough space in the database.
Thirdly as a last option you may look into archiving as a solution.
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.