on 09-10-2012 3:55 PM
Hi,
We have a problem with the database on our SAP PI 7.11 server getting larger and larger.
I ran a delete job today that should have deleted all messages and history older than 7 days but it didn't seem to clear down much space. We also ran a re-org on the database.
Can anyone recommend a way to reclaim more space from the database?
Thanks
Gareth
Hi,
go to DB02 and check the DB free size,there are many tables holds all messages, failed messages will not get archived,first you have to cancel then only achive deletion works.
First run Achive jobs to archive old messsages then perform Deletion.once you complete activity for all the messages then run DB Re-org.
and also check BC_MSG java table entries and schedule archive/deletion job .
Regards,
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gareth,
I don't know how many message your system is processing and what the avg. size is, but the sizes that you mention are relatively small compared to systems I used to work on.
Do you still have a huge amount of messages in your system with status error? They are not being deleted by the standard procedure.
You should check for sure the LOGGING option mentioned by Udo. When having this activated, the number of stored payloads in your system will be multiplied with almost a factor 10.
Kind regards,
Mark
Hi Gareth,
the database on our SAP PI 7.11 server getting larger and larger
Where did you get that information from? Can you provide more details?
I ran a delete job today that should have deleted all messages and history older than 7 days but it didn't seem to clear down much space.
This are at least two jobs, please have a look to: Archiving & Deletion of messages in PI - Part 3
Can anyone recommend a way to reclaim more space from the database?
First you need to analyze the reason for database growing. There are a couple of reasons possible, for example java stack, logs, traces, etc. If this is a productive system you should consider if you set SXMB_ADM parameter RUNTIME / LOGGING_SYNC and LOGGING to 0 to avoid success message logging at all (this is of course only ABAP stack).
Regards,
Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
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.