One recommendation would be to try to avoid having expiration running while
client sessions are accessing the server.  They both hit the some of the
same parts of the database, so the locks do start to conflict.  You can run
expiration in multiple windows through the day (with the duration
parameter) to avoid other processing that it could conflict with (client
backups and TSM database backups).

Nick Cassimatis

----- Forwarded by Nicholas Cassimatis/Raleigh/IBM on 02/13/2006 07:37 AM
-----

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/13/2006
05:03:47 AM:

> Hi
>
> I have been having database performance issues possibly related to
> unexpired objects in the database. The problem manifests itself with all
> the client sessions during the backup window grinding to a halt. There
> are 7 pages of locks on the database and nothing is moving. After
> running expiration, which expired 60% of the objects that is analysed,
> the problems goes away.
>
> Can anyone tell me how to work out the actual number of objects in the
> database? Also, once the expiration process complete- I ran it again,
> immediately and it found another few hundred thousand objects to expire-
> why?
>
> Has anyone else seen this type of problem? If so is there a statement
> that can be written to analyse the number of unexpired objects that
> currently reside in the database? As light weight as possible, as a
> heavy weight global lock enforced by a big statement probably wont
> complete when the system is under this massive load!
>
> Thanks
>
> Ian
>
> _____________________________
> Ian Smith
> SAN/TSM Specialist
>
>
>
>
> _____________________________________________________________
>
> This email (including any attachments to it) is confidential,
> legally privileged, subject to copyright and is sent for the
> personal attention of the intended recipient only. If you have
> received this email in error, please advise us immediately and
> delete it. You are notified that disclosing, copying, distributing
> or taking any action in reliance on the contents of this information
> is strictly prohibited. Although we have taken reasonable
> precautions to ensure no viruses are present in this email, we
> cannot accept responsibility for any loss or damage arising from the
> viruses in this email or attachments. We exclude any liability for
> the content of this email, or for the consequences of any actions
> taken on the basis of the information provided in this email or its
> attachments, unless that information is subsequently confirmed in
> writing. If this email contains an offer, that should be considered
> as an invitation to treat.
> _____________________________________________________________