We are at the same level of fixpack as you and not running into a problems. What you are describing sounds like something we ran into a long time ago when we first started using UDB. Is there any kind of backup processing going on when these errors occur? If DB2 can't get to a file because some other process had hold of it, DB2 would say something is wrong and mark the database as bad. It took us a while to learn to make sure that the server backups were not touching anything that DB2 wanted. I doubt if this is it if the problem just started happening...
Thanks. [EMAIL PROTECTED]@Lugwash.org on 02/25/2003 01:26:15 PM Please respond to [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: 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 ******************* PLEASE NOTE ******************* This E-Mail/telefax message and any documents accompanying this transmission may contain privileged and/or confidential information and is intended solely for the addressee(s) named above. If you are not the intended addressee/recipient, you are hereby notified that any use of, disclosure, copying, distribution, or reliance on the contents of this E-Mail/telefax information is strictly prohibited and may result in legal action against you. Please reply to the sender advising of the error in transmission and immediately delete/destroy the message and any accompanying documents. Thank you. - ::: 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
