Daniel,
you may try to set logmode from rollforward to normal during the audit.
Best regards
Gerhard
----
Gerhard Rentschler                   email:
Gerhard Rentschler                   email:
g.rentschler AT rus.uni-stuttgart DOT de
Manager Central Servers & Services
Regional Computing Center   tel: ++49/711/6855806
University of Stuttgart                fax: ++49/711/682357
Allmandring 30a
D 70550 Stuttgart
Germany





Daniel Sparrman <daniel.sparrman AT EXIST DOT SE>
Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11.02.2002 16:05
Bitte antworten an "ADSM: Dist Stor Manager"


        An:     ADSM-L AT VM.MARIST DOT EDU
        Kopie:
        Thema:  DB Audit failes with log full...


Hi
One of our customer has since some time back had a problem with their DB.
It seems they have a disk storagepool volume that cannot be deleted. When
trying to delete the volume, the TSM server halts, and cannot be brought
up again, giving an error code on startup.
Only thing to do when this happens is to restore the DB from the latest
backup.
This weekend, we were trying to run a  offline audit DB with fix=yes.
After about 8 hours, the audit stopped at one entry(which is probably the
entry that has gone bad). Then it just repeated the entry, until it said
the log was full. The log is 8GB large.
Is there any other way to repair the database? It seems we cannot get ride
of the damaged entry, and this means we cannot do a unload/load, or
anything else. As I know, the maximum size of the log is 13GB. This means
that our 8GB log shouldn't be to small. The database is 22GB, with 87.5%
utilized.
Appreciates any help
Best Regards
Daniel Sparrman