DB2LOG Question - DB2UDB 8.1 FixPak 5 for LUW on AIX 5.2 using TSM

Mark Baskerville

DB2LOG Question - DB2UDB 8.1 FixPak 5 for LUW on AIX 5.2 using TSM
List;

We are running DB2 UDB 8.1 FP5 on AIX 5.2 using the userexit to archive
logs to TSM.
We have been working with IBM on correcting a communication problem with
our TSM server that has prohibited us from archiving logs and taking
backups for about a week (this is not a production system).

Management is opposed to reverting to circular logging in the interim
and as a result, the DB2LOG file system for the catalog partition has
grown to 99%. I moved an old log to a separate file system to provide us
with some breathing room.

We anticipate a solution from TSM support this afternoon, but my concern
is that when I want to move this file back to the "/db2log" directory,
there will not be enough space to "squeeze" it back in.
What is a "worst case" scenario if the file system has increased in size
between now and this afternoon to the point where the old log file won't
fit back into it's original log file system?

We plan to take a full backup when we re-establish communication with
TSM, but I am concerned because the log file I moved was never archived.

Mark Baskerville
PBG - Database Engineering
Data Services
Email: [login to unmask email] <mailto:[login to unmask email]>
(V)914.767.7819 (F)914.767.1342
(P)888.858.7243 pin 133514



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

tim malamphy

Re: DB2LOG Question - DB2UDB 8.1 FixPak 5 for LUW on AIX 5.2 using TSM
(in response to Mark Baskerville)
Mark-

It should only be an issue if you actually need to
recover/restore something before you get a backup. If
you don't have really long UOWs and can get a full
backup (sending the backup somewhere other than TSM),
you won't need the old log files anyway. If the
filesystem does fill, and you need the log back, the
unix sysadm is going to have to make it a larger
filesystem. I tried playing around with NEWLOGPATH to
do this type of thing, but that won't let you move
logs from where DB2 knows where they were originally
created. A better solution, if it happens again,
might be to change NEWLOGPATH (and bounce db2) to some
place that has more space so that if you do need ALL
the logs for a recovery scenario, DB2 will keep track
of where they are for you.

The SQLOGDIR file is where all the pointers are kept,
but I've not personally tried tweaking it to do what
you want, since there are some weird values here and
there that I've not seen documented anywhere. IBM
might be able to walk you through it, though, if
expanding the file system is not an option.

timm

--- "Baskerville, Mark {PBG}"
<[login to unmask email]> wrote:

> List;
>
> We are running DB2 UDB 8.1 FP5 on AIX 5.2 using the
> userexit to archive
> logs to TSM.
> We have been working with IBM on correcting a
> communication problem with
> our TSM server that has prohibited us from archiving
> logs and taking
> backups for about a week (this is not a production
> system).
>
> Management is opposed to reverting to circular
> logging in the interim
> and as a result, the DB2LOG file system for the
> catalog partition has
> grown to 99%. I moved an old log to a separate file
> system to provide us
> with some breathing room.
>
> We anticipate a solution from TSM support this
> afternoon, but my concern
> is that when I want to move this file back to the
> "/db2log" directory,
> there will not be enough space to "squeeze" it back
> in.
> What is a "worst case" scenario if the file system
> has increased in size
> between now and this afternoon to the point where
> the old log file won't
> fit back into it's original log file system?
>
> We plan to take a full backup when we re-establish
> communication with
> TSM, but I am concerned because the log file I moved
> was never archived.
>
> Mark Baskerville
> PBG - Database Engineering
> Data Services
> Email: [login to unmask email]
> <mailto:[login to unmask email]>
> (V)914.767.7819 (F)914.767.1342
> (P)888.858.7243 pin 133514
>
>
>
>
---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go
> to the archives and home page at
> http://www.idugdb2-l.org/archives/db2-l.html. From
> that page select "Join or Leave the list". The IDUG
> DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG
> List Admins can be reached at
> [login to unmask email] Find out the latest
> on IDUG conferences at
> http://conferences.idug.org/index.cfm
>




__________________________________________
Yahoo! DSL – Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm