Auditdb poor performance

Manual data shredding is enabled on server and data has not been shredded yet

The below steps may be used to determine if there is data to be shred.

1. Verify if shredding is enabled on one or more storage pools.
   select stgpool_name,shred_count from stgpools
   A shred_count of 1 or higher indicates shredding is enabled for the storage pool.
2. Verify if there is data to be shred
   query shredstatus f=d
   The output from the query command will show "Objects Awaiting Shred" and "Data Left To Shred (MB)"
3. Verify the shredding server option
   q option shredding
4. In this instance, shredding was enabled for the storage pool, shredding was set to manual and there was data left to be shredded because the "shred data" command was not run. This slowed down the auditdb process.

Follow the steps below to resolve the performance issue with the auditdb when data shredding is enabled in a disk storage pool.

1. Start the Tivoli Storage Manager server
2. Shred the data with the following administrator command :
   shred data
3. Monitor how much data is left to be shredded with the following administrative command :
   query shredstatus f=d
4. Once data is shredded, stop the Tivoli Storage Manager server.
5. Re-run the offline auditdb process.
6. Restart the Tivoli Storage Manager server.
   

Note : When running with the "shredding manual" server option, consider running the "shred data" admin command at regular interval so that data is shred regularly.