Author |
Message
|
wmb_wps_soa |
Posted: Tue Feb 08, 2011 10:47 am Post subject: DB2 SQLNATIVEERROR error codes for network/database down. |
|
|
Acolyte
Joined: 19 Feb 2010 Posts: 65 Location: Detroit,Michigan,USA.
|
Hi Guys,
Could you please provide all the possible DB2 SQLNATIVEERROR that we get when an database exception occurs due to timed out,end of file communication channel,maximum number of sessions/processes exceeded,table not found, schema not found,database not accessible?
I got few SQLNATIVEERROR error codes for DB2 like : -1032 and -201.
I want the SQLNATIVEERROR details for implementing the database retry logic.
The message broker version i use is 7.0.0.1
Thank you
Jeba |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 08, 2011 10:59 am Post subject: Re: DB2 SQLNATIVEERROR error codes for network/database down |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
wmb_wps_soa wrote: |
Could you please provide all the possible DB2 SQLNATIVEERROR that we get when an database exception occurs due to timed out,end of file communication channel,maximum number of sessions/processes exceeded,table not found, schema not found,database not accessible? |
Look in the DB2 documentation; they're called native errors for a reason. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Feb 08, 2011 11:27 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
My guess is that someone has told you to code for ALL possible database errors that Might just possibly appear when some 'idiot' takes the database down or something equally wacky.
The number of possible errors is franky huge.
Even if you found them all, how exactly are you going to prove to whoever asked you to do this that you have covered all the bases. Testing for all these conditions is frankly going to take you several months of Sundays. Some of the errors are so obscure that devising a test to generate them without you good self being a DB2 Guru and possibly privvy to the source code for DB2.
When a Database goes dowin in production it is a Major Incident Full Stop. The fact that a slightly different error code got reported this time should be irrelevant.
All you can do is report/log the actual error code received from DB2 (or any other DB for that matter), roll back the transaction and let the DBA's sort it out.
End of Sermon. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 08, 2011 11:47 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
smdavies99 wrote: |
The number of possible errors is franky huge.
Even if you found them all, how exactly are you going to prove to whoever asked you to do this that you have covered all the bases. Testing for all these conditions is frankly going to take you several months of Sundays. Some of the errors are so obscure that devising a test to generate them without you good self being a DB2 Guru and possibly privvy to the source code for DB2. |
You're determined to take all the fun out of my life.
Mind you, if there was broker code that could individually handle every possible DB2 error it's a potential gold mine. I'd buy a copy.
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Feb 08, 2011 12:13 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Vitor wrote: |
You're determined to take all the fun out of my life.
|
Aw shucks Vitor. I didn't mean to to that.(te-he). _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 08, 2011 12:18 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
smdavies99 wrote: |
Vitor wrote: |
You're determined to take all the fun out of my life.
|
Aw shucks Vitor. I didn't mean to to that.(te-he). |
Why should be the only one....
(Just assume a 5 minute tirade on the sad injustices of the system as they apply to me at this point. While I devise a really good way for one of the project managers to cease being a problem yet making it look like an accident.) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Feb 08, 2011 1:03 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Vitor wrote: |
(Just assume a 5 minute tirade on the sad injustices of the system as they apply to me at this point. While I devise a really good way for one of the project managers to cease being a problem yet making it look like an accident.) |
See last Friday's & Saturday's Dilberts....  _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 08, 2011 1:12 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
smdavies99 wrote: |
See last Friday's & Saturday's Dilberts....  |
Saturday's rang a bell & something like has happened a few times.
The only time I've encountered Friday was being told my rate was going to be cut at renewal and there was nothing I could do about it. I got points back by not seeking renewal and watching the panic flit across the PHB's face.
It's not just about the money. Though it is mostly about the money.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Feb 08, 2011 5:43 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It is an interesting metric, when applying for a position, to count the number of Dilbert strips on display in the cube farm. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Feb 08, 2011 10:30 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
mqjeff wrote: |
It is an interesting metric, when applying for a position, to count the number of Dilbert strips on display in the cube farm. |
good luck with that one where I'm currently working jeff.
- No cubicles
- Not allowed to stick anything on the walls.(Even the glass ones!)
- A Clean Desk policy _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
fatherjack |
Posted: Wed Feb 09, 2011 1:53 am Post subject: Re: DB2 SQLNATIVEERROR error codes for network/database down |
|
|
 Knight
Joined: 14 Apr 2010 Posts: 522 Location: Craggy Island
|
And just getting back to the original subject for a second
Quote: |
Could you please provide all the possible DB2 SQLNATIVEERROR that we get |
Just how many different paths do you want your code to take when it gets a SQLNATIVEERROR ?
Quote: |
I want the SQLNATIVEERROR details for implementing the database retry logic. |
I'm guessing you just want to know the codes that might be temporary problems that could go away by the time you retry? So I'd suggest you come up with a realistic list of conditions where you want to retry and find the SQLNATIVEERROR codes for these, and not worry about the rest of the huge list. _________________ Never let the facts get in the way of a good theory. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Feb 09, 2011 4:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
smdavies99 wrote: |
mqjeff wrote: |
It is an interesting metric, when applying for a position, to count the number of Dilbert strips on display in the cube farm. |
good luck with that one where I'm currently working jeff.
- No cubicles
- Not allowed to stick anything on the walls.(Even the glass ones!)
- A Clean Desk policy |
That says quite a bit as well. |
|
Back to top |
|
 |
|