Cleaning up after a crash

[jadionne]

I have a new instalation that I am ironing out the wrinkles in. In the
process I have had a few crashes and now my SQLlib\DB2 Dir is full of
..0 and .000 files. What is the best way to clean up this Dir without
damaging anything permanatly?

[Serge Rielau]

ja******@gmail.com wrote:

I have a new instalation that I am ironing out the wrinkles in. In the
process I have had a few crashes and now my SQLlib\DB2 Dir is full of
.0 and .000 files. What is the best way to clean up this Dir without
damaging anything permanatly?

Assuming youhave no intention to call support..
rm -rf (or the equivalent of Windows) does a great job :-)
You may want to back up the db2diag.log, eventlog etc...
Note that cleaning out the log files every so often is good house
keeping. (just rename them every 24 hours or so and archive away - cron
job).
DB2 will recreate the files when it finds them missing.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[jadionne]

I am in a windows enviroinment. Im not sure what rm -rf means...

[Sean McKeough]

It means "del * /s"...but don't do that...on windows (unlike unix) the
default diagnostic path is shared with the dbm config file, and some
other important directories etc. I'd suggesting changing your diagnostic
paths to point to a different directory. If you want to remove all the
files from the directory, back them up first in case something goes
wrong...I think the only thing you'll need is the config file(db2sys*)
but I'm not 100% sure what's created by default in that path.

ja******@gmail.com wrote:

I am in a windows enviroinment. Im not sure what rm -rf means...

[jadionne]

Ok so back up the Dir and delete the 0 and 000 files
do you remember where the diagnostic path is defined, in the db cfg or
dbm cfg?

[Serge Rielau]

Sean McKeough wrote:

It means "del * /s"...but don't do that...on windows (unlike unix) the
default diagnostic path is shared with the dbm config file, and some
other important directories etc.

Now that is just nasty...

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[jadionne]

But you told me to do it....

[Pierre Saint-Jacques]

In the dbm cfg, look for DIAGPATH
HTH, Pierre

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<ja******@gmail.com> a écrit dans le message de news:
11**********************@g14g2000cwa.googlegroups. com...

Ok so back up the Dir and delete the 0 and 000 files
do you remember where the diagnostic path is defined, in the db cfg or
dbm cfg?

[Serge Rielau]

ja******@gmail.com wrote:

But you told me to do it....

Who believes what's on the internet....?

Sorry. Wasn't aware of this Windows special.

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[jadionne]

But you work for the IBM TORONTO LAB!!! Its your job to know.

[Serge Rielau]

ja******@gmail.com wrote:

But you work for the IBM TORONTO LAB!!! Its your job to know.

I'll start the pilgrimage to Canossa right away, just need to get some
rags from Loosers first.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[Jan M. Nelken]

Serge Rielau wrote:

I'll start the pilgrimage to Canossa right away, just need to get some
rags from Loosers first.

“Nach Canossa gehen wir nicht”

Jan M. Nelken (quoting Bismarck)

[jadionne]

Back to the actual topic at hand, just to be clear i can delete the .0
and .000 files from this directory manualy with out causing issues?
Also if I change my diag path in the future if i run the db2 support
command the command will know where to get its info correct?

[Jan M. Nelken]

ja******@gmail.com wrote:

Back to the actual topic at hand, just to be clear i can delete the .0
and .000 files from this directory manualy with out causing issues?
Also if I change my diag path in the future if i run the db2 support
command the command will know where to get its info correct?

I thought Canossa was actual topic at hand. Back to the previous topic:

1. Yes - removing all *.trp, *.0* files won't cause any problems - assuming you
are not going to report this problem to IBM.

2. You change the diagnostic path by updating database manager configuration -
so db2support can find out where your diagnostic files are...

3. You may consider scheduled task executed daily/weekly (depending on growth
rate of db2diag.log) which renames db2diag.log to db2diag.yyyymmdd (Year Moth Day)
Jan M. Nelken

move