on 01-11-2012 6:56 PM
Hi Experts,
I have a <Removed by moderator> requirement in my project to release database space from PI server.
I have done the following things to accomplish this:
1. Set the retention period in SXMB_ADM
2. Activated "Switch delete procedure" in SXMB_ADM.
3. Scheduled the Deletion job and History Deletion jobs in PI. This job is running successfully and the joblog states that the entries are being deleted.
The messages are getting deleted from SXMB_MONI,but the DB space is not getting freed.
Also the entries in SXMS* tables is not getting deleted.
Please suggest a solution as almost 92% space of our current production system is already occupied.
Thanks,
Nitin Nigam
Edited by: Prateek Raj Srivastava on Jan 12, 2012 1:08 AM
Hi,
Have you set the Deletion job recently or was it there since beginning?
If the deletion job is defined recently, then it will not delete the previous messages.
Please refer to SAP Note 789352 for this.
-Supriya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Which database is it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Prateek,
In our landscape we have file to RFC scenario with huge data "nearly 250 MB".
Due to which the DB space has been occupied very frequently.
Can you please suggest a way to delete the payload manually from Database.
Also the reorg status is as follows:
messages in DB : 148655
messages in client : 148655
Number of messages in client still to be reorganized: 6991
Asynchr. msgs in retention period (cannot be deleted): 6986
The major problem is messages are getting deleted by executing the Delete Jobs but the DB space is not getting freed.
Regards,
Nitin Nigam
Dear nitin_ngm,
this information on database platform in use is essential!
In that db2 version, there is no native "truncate table" statement (this statement is executed at the very end of a table switch), and the DBSL implemented the abap truncate statment using the following DB2 native commands:
"IMPORT FROM /dev/null of DEL REPLACE INTO <table name>"
In SAP enviornment, the default behavior of the above command does not release the physical storage associated with an object because of the following database registry setting:
<i> DB2_TRUNCATE_REUSESTORAGE=IMPORT [DB2_WORKLOAD]
Hence, an offlince table reorg is necessary after the truncate.
For a detailed description of this registry variable DB2_TRUNCATE_REUSESTORAGE, please refer to the following IBM online doc:
[DB2_TRUNCATE_REUSESTORAGE|http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.regvars.doc/doc/r0005669.html|DB2_TRUNCATE_REUSESTORAGE]
You should be able to free the space via ALTER TABLESPACE ... REDUCE MAX
See related information under the following link.
[ALTER TABLESPACE ... REDUCE MAX|http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.sql.ref.doc/doc/r0000890.html|ALTER TABLESPACE ... REDUCE MAX]
Best regards,
Harald Keimer
PI Development Support
SAP AG, Walldorf
Hello,
You have to perform a "table reorganization". For other DBs this is called "database shrink".
Check the official documentation in order to choose the best strategy for your scenario:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/t0024848.htm
Cheers,
Diego.
If you can reduce the retention period of messages, then you may follow SAP Note 807615 untill you get the actual solution.
Regards,
Prateek Raj Srivastava
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 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.