Tim, I am running out the door to catch a plane, so this isn't long, read Roger Sanders article in the current db2magazine on interpreting diaglog entries and it should point you in the right direction. Also, go to www.software.ibm.com/data/db2/udb
select library, technical manulls, then search the support web site for a quick hit. Phil ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 25, 2003 1:26 PM Subject: [DB2EUG] Database Marked Bad????? > Hello Again List, > > We have been getting errors in the db2diag.log this morning that seem to be > related to 2 different databases. Below is a sequence of these errors. > This sequence has been repeated 2 time each for both of the databases. The > sequences of errors are not happening at the same time. We haven't heard > of anything being wrong from the user end and I can connect to and query > against the tables in the databases. We are at UDB version 7.2 fixpack 6 > on Windows 2000. I am wondering if anyone has seen something similar to > this or has any ideas where I might need to start to look to resolve this. > The last line stating "Marking the database as bad" is very concerning to > me as you may know. I am wondering what exactly that would mean. > > Any guidance is appreciated. > > Thanks, > Tim > > ================================================================== > > > 2003-02-25-10.53.40.475000 Instance:DB2 Node:000 > PID:1520(db2syscs.exe) TID:984 Appid:none > data_protection sqlpgifl Probe:90 > DIA3711C A file "" could not be found. > > ZRC=0xFFFFE60A > > 2003-02-25-10.53.40.491000 Instance:DB2 Node:000 > PID:1520(db2syscs.exe) TID:2192 Appid:none > data_protection sqlpgilt Probe:640 > DIA3856C No message was found in the message queue. > > ZRC=0xFFFFF640 > > 2003-02-25-10.53.40.491001 Instance:DB2 Node:000 > PID:1520(db2syscs.exe) TID:2192 Appid:none > data_protection sqlpgasn Probe:400 > > Logging can not continue due to an error. 0000 0000 > .... > > > 2003-02-25-10.53.40.506000 Instance:DB2 Node:000 > PID:1520(db2syscs.exe) TID:888 Appid:0A1B013E.DE12.030127225532 > data_protection sqlpgint Probe:270 Database:WASPRD3C > DIA3856C No message was found in the message queue. > > ZRC=0xFFFFF640 > > 2003-02-25-10.53.40.506001 Instance:DB2 Node:000 > PID:1520(db2syscs.exe) TID:888 Appid:0A1B013E.DE12.030127225532 > base_sys_utilities sqledint Probe:9 Database:WASPRD3C > > DiagData > 40f6 ffff @��� > > > 2003-02-25-10.53.40.506002 Instance:DB2 Node:000 > PID:1520(db2syscs.exe) TID:888 Appid:0A1B013E.DE12.030127225532 > base_sys_utilities sqledint Probe:9 Database:WASPRD3C > > RIDS/sqledint MS/UNKNOWN_ERR PRCS/940f6 ffff > @��� > > > String Title:sqleMarkDBad: PID:1520 Node:000 > Marking the database bad. > > > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > *** For more information, check http://www.db2eug.uni.cc > - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
