SvenM

A customer of mine is implementing policy documents in an environment with about 5000 users. An archiving policy was created and by accident this policy was assigned to a large amount of users. This was not intended and these people were not notified up front. We don’t have a program document that does a load compact -A. Still these users all have an archive now and they are not happy!

Somebody told me that ever since R8 when you do a compact -B the archiving process kicks in. We do have program documents that perform a compact -B.

When I take a look at the help file I find the following:

-b : Uses in-place compacting and recovers unused space without reducing the file size, unless there’s a pending structural change to a database, in which case copy-style compacting occurs. This is the recommended method of compacting.

-B : Uses in-place compacting, recovers unused space and reduces file size, unless there’s a pending structural change in which case copy-style compacting occurs. If you use transaction logging, do full database backups after compacting completes.

I find nothing about archiving! Can anybody tell me if this is true ??