Scott,
As I had mentioned in my previous email, Appendix A, DB2 Internal Return
Codes, of the DB2 Troubleshooting Guide, provides information on how to
interpret DB2 internal codes (FFFF**** or ****FFFF formats).
For the codes with FFFF**** format, simply look for the four character
hexadecimal value in the Appendix. For example, the code FFFFE60A can be
interpreted by looking up the entry for E60A in the Appendix and finding
out that it means the File does not exist.
For ****FFFF codes:
1. Byte-reverse them
Switch the first four characters with the last four characters, and
then the fifth and sixth characters with the seventh and eighth
character. For example, the error code 0AE6FFFF is translated to
FFFFE60A
2. Convert it to decimal format, using a hexadecimal conversion too
If it is in the Message Reference, then it is a SQL code
Else it is an internal code � check the Troubleshooting Guide
Hope this helps ...
Iqbal Goralwalla,
Triton Consulting
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Scott Saunders
Sent: 26 February 2003 13:14
To: Fortier, Christi (GTS); [EMAIL PROTECTED]; John Lantz
Cc: [EMAIL PROTECTED]
Subject: RE: [DB2EUG] Database Marked Bad?????
Does anyone know how to convert John's error code, ZRC=0xFFFFE60A, into
anything useful? I thought that I had seen a method for this at one
time but cannot find it right now.
Thanks,
Scott
-----Original Message-----
From: Fortier, Christi (GTS) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 4:56 PM
To: '[EMAIL PROTECTED]'; John Lantz
Cc: [EMAIL PROTECTED]
Subject: RE: [DB2EUG] Database Marked Bad?????
First, check with your people to see if anyone deleted a file as that is
what the diaglogs are saying. Looks like a log file. If this is the
case
& a restore & rollforward to most current log time is not an option; IBM
labs may help you resolve this.
Otherwise,
Are your logs or tablespaces on a SAN? If the SAN is not configured
correctly the Win locking mechanism could have allowed something else to
access the LUN your volume is on. You can go into explorer or command
line & just look at a directory on the volume, if it is marked as not
accessable/corrupt; then DB2 won't be able to access. The SAN LUNs are
sometimes rebuildable or fixable when this occurs (ie: if you have a hot
spare).
Sometimes DB2 heals itself when it sees its resource is available
again(look for crash recovery or node recovery in the diag log).
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 3:32 PM
To: John Lantz
Cc: [EMAIL PROTECTED]
Subject: Re: [DB2EUG] Database Marked Bad?????
This server was just activated last week, so I was able to go back and
review the entire DB2DIAG.LOG and I ran into no other occurrences of
this sequence of errors. We do have db2 backups that run nightly, but
these errors have occurred outside of the time that the backups were
running and these backups go to a d:\db2\backups directory. We have
this same setup on several other servers and are not encountering any
problems.
Thanks,
Tim
"John Lantz"
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
hna.com> cc:
[EMAIL PROTECTED]
Sent by: Subject: Re: [DB2EUG]
Database Marked Bad?????
[EMAIL PROTECTED]
ash.org
02/25/2003 01:51
PM
Please respond to
"John Lantz"
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
-
::: 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
-
::: 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
