ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Evaluating exceptionlist database failure reason

Post new topic  Reply to topic
 Evaluating exceptionlist database failure reason « View previous topic :: View next topic » 
Author Message
sclarke
PostPosted: Fri Jul 25, 2014 10:24 am    Post subject: Evaluating exceptionlist database failure reason Reply with quote

Apprentice

Joined: 05 Jan 2002
Posts: 39

I would like to differentiate between database insert errors in ESQL and identify if the insert failed due to a recoverable error or non-recoverable ie. something wrong with the data being inserted. Recoverable means insert to db may have failed due to logon failures, network error, table out of space etc. I would like to do this so I can set up process to be able to retry the messages which failed due to 'recoverable ' errors.

Looking at odbc sqlstate codes - there is quite a mix and I believe I would have to grab the sqlstate out of the last child and list the ones I thought were recoverable and the ones that are not.

There is also a line in the last DatabaseException which states ImbOdbcStatement for the data error (bad data on insert) and the other for the connection failure due to bad password has ImbOdbcConnection.

I would like to codify this in a simple manner - has anyone else solved this issue?

Thanks
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Jul 25, 2014 11:08 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

I tried this once. I gave up after some 'Fixes' to the DB changed all the error codes.
The DB supplier said 'tough, all the error codes we return are documented'.
That was true but suddenly the error codes for a error that we had a test case for changed. Time to pull hair out of head, go to the Pub and forget about doing for specific errors. Never felt like trying again.
_________________
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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Evaluating exceptionlist database failure reason
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.