on 12-12-2013 5:39 AM
Hi Everyone,
I recently found out that some administrative jobs had not been regularly scheduled in our BW system due to which the size of the table '' had grown to a huge 75+ GB. After I found out I scheduled and executed the program RSBM_ERRORLOG_DELETE to delete all logs older than 90 days in the system.
At first the job failed because the size of the logs was too huge. Afterwards I scheduled the job in batches to delete 3 months worth of logs at a time and went on to delete all the logs older than 90 days from the system. However even after deleting all the old logs the table size hasn't reduced at all. It still shows 75+ GB in DB02.
Can someone tell me how I can get the table size to reflect the actual number of records in the table? FYI The deletion job is now scheduled regularly and there are no logs older than 90 days in the system.
Hi
have a look at this .
Regards ,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks for the link, but I've already implemented those steps. As I explained in my post, I've finished clearing all the old logs.
The issue is that even after deleting the logs, the table size isn't going down. I've talked to my basis team and they've also reorganised the table, still no change in the size.
I forgot to put in the name of the table. Its RSBERRORLOG.
Apologies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
11 | |
10 | |
8 | |
8 | |
6 | |
6 | |
6 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.