Skip to Content
0

SAPSR3DB LOBSEGMENT MG_STG space is drastically increasing in XI/PI Production

Oct 05, 2017 at 06:12 AM

134

avatar image

Hi All,

As we noticed In SAP PI System PSAPSR3DB Table space is drastically increasing and irrespective of adding 250 GB space additionally still table growth is occupied 86% as shown below.

Please help us the way to reduce the PSAPSR3DB LOBSEGMENT Space.

Regards,

Kesava.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

James Zhang
Oct 06, 2017 at 08:40 AM
0

Hi Kesava,

This could be oracle bug 26729494, for the details please refer to SAP note 2538588.
If the workaround does not work, please contact SAP support by mentioning this note.

Best regards,
James

Share
10 |10000 characters needed characters left characters exceeded
KESAVA SUGALI Oct 07, 2017 at 06:39 AM
0

Dear James,

Thanks q So much for your suggestion. I will suggest my DB team to implement the same.

Kindly suggest on my below query. As we are not able to solve this from past one month. Due to this we are not able to perform any production activity in smooth way.

Issues we are facing

In SAP PI System PSAPSR3DB Table space is drastically increasing and irrespective of adding 700 GB space additionally still table growth is occupied 90%.

I asked DB team to perform the RE-ORG activity in table (PSAPSR3DB- BC_MSG)for getting the extra used space in the segment level. While performing this activity DB team is facing the below error. There are un able to resolve this this and table space is keep increasing. Please suggest us the way to come out from this issue.

""

ORA-00955: name is already used by an existing object

BR0280I BRSPACE time stamp: 2017-10-06 00:11:24
BR1106E Reorganization of table SAPSR3DB.BC_MSG failed

""

Regards,

Kesava

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Kesava,

You are welcome.

Note 2538588 workaround is to set a parameter, but to reduce the table size, you are correct, you need to perform reorg.

Regarding the reorg error, which command you used? referring to note 646681?

Best regards,
James

0