 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / DB2 Topics / June 2005Cleaning up after a crash
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? > 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  SignatureSerge Rielau DB2 SQL Compiler Development IBM Toronto Lab I am in a windows enviroinment. Im not sure what rm -rf means... 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. > I am in a windows enviroinment. Im not sure what rm -rf means... 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? In the dbm cfg, look for DIAGPATH HTH, Pierre SignaturePierre Saint-Jacques SES Consultants Inc. 514-737-4515 > 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? > 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... SignatureSerge Rielau DB2 SQL Compiler Development IBM Toronto Lab But you told me to do it.... > But you told me to do it.... Who believes what's on the internet....? Sorry. Wasn't aware of this Windows special. SignatureSerge Rielau DB2 SQL Compiler Development IBM Toronto Lab But you work for the IBM TORONTO LAB!!! Its your job to know. > 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 SignatureSerge Rielau DB2 SQL Compiler Development IBM Toronto Lab > 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) 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? > 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 |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.