Clemens,
If you're server can't startup again, because the log is 100% full, you've
got the biggest problem I know.
This is the only way i know to get it up and i'm sure you don't like it:
- Restore the database.
Now you can start the server. If it works, halt TSM
- Audit database
Start TSM
- Audit ALL volumes.
Like i said, you don't like it, but it works.....
If anybody knows a better way, i like to hear it...
Succes,
Maurice
The Netherlands
----- Original Message -----
From: "Block, Clemens" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 20, 2001 2:48 PM
Subject: Server crashed with full dblog volume
> Hi Folk!
>
> I have an out of service Problem with our TSM 3.7 Server runnig on
> a NT Server.
>
> Depending on special circumstances the Server was unable to
> perform a db backup. He tried to dot it for several hours but at the
> end the server crashed.
>
> Unfortunately I'm unable to restart the server to perform a db backup
> by hand. When I start the server service it crashes after a few minutes
> with an Dr. Wartson reporting an application error in dsmsvc.dbg.
>
> What can I do to solve the problem?
> I'm not sure, but I think, that the logvolume is 100% full now and so
> the server can't start.
>
> In my opinion I can solve the problem, if it is possible to start a db
> backup without a running server or exctend the dblog without a run-
> ning server. Any idea how to do this?
>
> Is there any other solution to fix my problem?
>
> As I mentioned bellow, the server is out of service at the moment.
> Therefore it is really urgent for me to solve the problem.
> I'm appreciativelly for any hint.
>
> Thanks in advance
> Clemens
>
