ADSM-L

Re: Problem with audit DB

2003-03-26 14:15:12
Subject: Re: Problem with audit DB
From: Jurjen Oskam <jurjen AT QUADPRO.STUPENDOUS DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 26 Mar 2003 20:12:32 +0100
On Wed, Mar 26, 2003 at 04:13:14PM +0100, GUILLAUMONT Etienne wrote:
>
> I had a problem with my TSM db, it couldn't make a reclamation with an
> error on the db (some raws could not be deleted as I remember)
> So I am trying to do an auditdb but the problem is that I get the
> followings messages :
>
> ANR4306I AUDITDB: Processed 324433 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324433 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324433 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324433 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324433 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324433 database entries (cumulative).
> ANR9999D imaudit.c(5630): ThreadId<11> Inventory object 0.3081816 deleted.
> ANR4306I AUDITDB: Processed 324434 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324434 database entries (cumulative).
> ANR4306I AUDITDB: Processed 324434 database entries (cumulative).

You forgot to mention a *lot* of information, for example:

 - What level of TSM are you on?
 - How large is your database (GB)?
 - On what type of hardware does the TSM server run?
 - What kind of clients do you have?


For what it's worth, I encountered this problem too, once. It was on
a level of TSM that was mishandling Windows 2000 System Objects. Before
resolving the problem, an auditdb took hours and hours (2G), after
resolving the problem an auditdb took 25 minutes.

Search the archives for the "CLEANUP BACKUPGROUP" command. *If* the System
Objects are causing this problem, CLEANUP BACKUPGROUP can help. Note
that CLEANUP BACKUPGROUP is only available at later TSM levels!

--
Jurjen Oskam

PGP Key available at http://www.stupendous.org/

<Prev in Thread] Current Thread [Next in Thread>