ADSM-L

DB Audit failes with log full...

2002-02-11 10:29:06
Subject: DB Audit failes with log full...
From: Daniel Sparrman <daniel.sparrman AT EXIST DOT SE>
Date: Mon, 11 Feb 2002 16:05:37 +0100

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

<Prev in Thread] Current Thread [Next in Thread>
  • DB Audit failes with log full..., Daniel Sparrman <=