ARSMAINT on system log

[pankaj.puranik]

Hi

I tried to expire the System Log using the following command.

/opt/ibm/ondemand/V9.0/bin/arsmaint -I xxxxxxx -u xxxxx -p xxxxx -n 10 -x 10 -t 2027-12-31 -g "System Log" -d

However after running for some time and completing, when I check the space utilization on the file system, it is unchanged.
Meaning that no expiration happened.
Also the number of rows on the System Log remained unchanged.

Note that I am running the expiration processing using a future date.
Any reason why the space is not clearing.

The retention period on the System Log App Group is 7 years.

Thanks
Pankaj.

[Justin Derrick]

Before I tell you what you've missed, I just want to confirm -- do you realize that the command you're about to run will delete the entire System Log?  Are you absolutely sure you want to do this?

Also, you may be disappointed by the storage savings -- the System Log is usually far under 1% of the size of any cache filesystem, even on small servers.

This should ABSOLUTELY not be run on a production server.

[pankaj.puranik]

I understand JBNC that this will wipe off System Log.
Note that this is a non-production server.

Also I did a query on the database to get the size info and this is what I got.

As you can see that SL3 alone is consuming about 3 GB of space.


Table Name                                  Table Physical size in MB Index Size
SL3                                                 3179
SL2                                                 1708

[pankaj.puranik]

Found this post from Alessandro which probably answers it.
http://www.odusergroup.org/forums/index.php?topic=1871.msg6967#msg6967

The -t option does not work with -d option

[Justin Derrick]

Correct, you would need to remove the -d and add the -c option.

But this still wouldn't remove the System Log metadata, only the data in the cache filesystem.

If you want to shrink the size of a table and indexes, you need to delete rows in order to create free space, and then run a 'reorg table <tablename>' to reclaim the free space in the database pages.

[pankaj.puranik]

See the utilization.
Finding now way to find the biggest contributor.

/dev/mapper/root_vg-db2data1
                       15481840  13935136    760336  95% /apps/IBM/db2/xxxx/data1

[pankaj.puranik]

The reason why the space utilization was not coming down even after expiring eligible records was because we did not run the REORG.
We are using DB2 and it seems that you need to run the REORG to reclaim the space.
The utilization is down to 70 % now.

Cheers
Pankaj.

[Jaydeep Mehta]

HI Pankaj,

If we use Oracle in that case also run  REORG to reclaim the space ..

Regards
Jaydeep