Tablespace memory

[Former Member]

Hi all,

We are facing one issue regarding tablespace PSAPXIDDB.

Initially its having 5GB memory, after some data was processed communication channel was giving the following error.

unable to extend lobsegment SAPXIDDB.SYS_LOB0000052285C00020$$ by 128 in tablespace PSAPXIDDB

So we have increased the memory of tablespce PSAPXIDDB by 2GB...........

processing of some data again tablespace memory was full....so every time we are increasing that memory.

But we dont want to increase memory like this, so i have deleted old XML messages through SXMB_ADM deletion program,but we dint get any free space...after that we have re organized that table sapce also but no use..........

Could you please let me know how can we get the free memory of that table space?

Thanks,

Sreedhar Goud.

[SudhirT · Accepted solution]

Hi,

To get the memory free, you need to reorganize the tables. To reorganize the tables Follow these steps

1. Mark message interfaces for archiving.

2. Schedule deletion and archiving jobs periodically

3. Run the report RSXMB_DELETE_ARCHIVED_MESSAGES to delete the archived messages.

4. Goto SXMB_ADMIN and activate the switch table deletion.

5. Set the DROP_MAX_LOAD parameter to a minimum value then persistent layer in SXMB_ADMIN>Integration Engine Configuration->Specific configuration.

6. Run the report RSXMB_TABLE_SWITCH

Let the job finish (will take large time) and then you will get the message as table reorganised.

This way you can prevent the continuous growth of database.

Thanks!

[Former Member · Accepted solution]

Hi Sudhir,

I have done all the mentioned steps.........but we dont want the previous data so that we have scheduled only deletion job....we are not archiving the data(we have not scheduled archiving job).........and reorganized the table space.....But we dint get any free memory.........particular one lob segment only taking this memory.......we have to clear that........

Thanks,

Sreedhar Goud.

[SudhirT · Accepted solution]

Hi,

There are some messages which are cancelled or modified mannually, automaticallly archived. Also archiving ensures that there are no more messages.

Check also the retention period in Integration engine for different kind of messages also reduce this Persistent Duration of messages in Visual Admin>Services>SAP XI Adapter-->Inbound and outbound persist duration from 30 days to 7 days.

After you run the deletion job check in Moni to make sure whether all old messages are deleted.

Thanks!

[former_member334189]

Dear Sreedhar,

from the information provided in your request I can see that this issue is related to segments in the java related schema of your Oracle DB. SYS_LOB* denotes LOB segments storing large objects (>4000Byte) outside the database table.

Depending on the throughput and the average message size the java base persistency layer might easily exceed 5Gb. Please check whether the sizing of your tablespaces matches the quantity structure processed by XI (Java stack).

In order to reorganize (delete) messages in the java related persistency layer please follow OSS note 872388, section 2.

Please note that deleting XML messages means that the database space is no longer allocated. It does not mean that this space is released on file system level immediately. This is done by the DBMS and highly depends on the database platform in use. For Oracle there is the BRSPACE tool which is also able to handle LOB segments. For your reference you might want to have a look at OSS notes 647697, 646681 and 500340.

Best regards,

Harald Keimer

XI Development Support

SAP AG, Walldorf