Re: Page Shadow File not valid

Yes, that did it. Server is running again. The exact commands I had to do
were:

>dsmfmt -log tempreclog 1000
>dsmserv extend log tempreclog 1000

Thanks for the help,

Alex
---                                                               ---
   Alex Lazarevich | Systems Administrator | Imaging Technology Group
            Beckman Institute - University of Illinois
       alazarev AT itg.uiuc DOT edu | (217)244-1565 | www.itg.uiuc.edu
---                                                               ---

On Tue, 29 Jul 2003, Bob Booth - UIUC wrote:

> You need to go to the back of the Reference Guide and look at how to add log
> space to the server.  There is a procedure for recovering the server due to
> overcommited log space.
>
> I don't know the answer for the shadow device, but it really isn't the problem
> here I believe.
>
> Once the log is extended and you figure out what pinned the log and fix the
> problem, you can get rid of the extra space you created.  More than likely
> the clients pinned the log and a database backup was not able to clear enough
> space.  You might need more recovery log space in the future.
>
> bob
>
> On Tue, Jul 29, 2003 at 02:31:12PM -0500, Alexander Lazarevich wrote:
> > We just got TSM 5.1.6.5 running on Windows 2K server. Server configured
> > and started a couple of weeks ago and it has been running great. I've been
> > backing up clients, getting all the data on the server, so far so good,
> > until an hour ago.
> >
> > I was backing up 3-4 clients at a time, when all of a sudden the client
> > displayed a message: "Not enough space in the recovery log". I went to the
> > server and it was hung. I tried to restart the server and I get the
> > following errors:
> >
> > ANR0990I Server restart-recovery in progress.
> > ANR0200I Recovery log assigned capacity is 8000 megabytes.
> > ANR0201I Database assigned capacity is 4000 megabytes.
> > ANR0306I Recovery log volume mount in progress.
> > ANR0287W Contents of the page shadow file dbpgshdw.bdt are not valid.
> > ANR0285I Database page shadowing started using file dbpgshdw.bdt.
> > ANR0353I Recovery log analysis pass in progress.
> > ANR0354I Recovery log redo pass in progress.
> > ANR0355I Recovery log undo pass in progress.
> > ANR0352I Transaction recovery complete.
> > ANR9999D adminit.c(1269): ThreadId<0> Insufficient log space to update
> > table Administrative.Attributes.
> >
> > So it seems the server can't read the dbpgshdw.bdt, yet it starts using it
> > anyway, and then the server crashes due to insufficient log space.
>