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 » DB exception 'HY001'

Post new topic  Reply to topic
 DB exception 'HY001' « View previous topic :: View next topic » 
Author Message
sanjoo
PostPosted: Thu Nov 01, 2012 9:12 pm    Post subject: DB exception 'HY001' Reply with quote

Acolyte

Joined: 26 Oct 2005
Posts: 65

Hi,
We are facing weird database exception. Here is the scenario -

MQInput (with transaction mode 'Yes') --> Compute node doing DB inserts and updates (with transaction mode 'Automatic' and throw exception on DB error checked)
Upon DB failure we handle it in catch path.

Works fine for happy scenarios. But if tested with genuine DB failure scenario, it fails as expected. However, any other valid message which normally succeeds is played within 1 minute interval of previously DB failure scenario, fails with 'HY001' exception. The same message if played after waiting for a minute succeeds.

'HY001' seems to be memory allocation exception. Am I missing some configuration at flow level or is it the lack of resources on the machine or some DSN configuration issue?

Any hint will be really really helpful.
Thanks in advance.
_________________
Sanjoo

Keep smiling
Back to top
View user's profile Send private message
sanjoo
PostPosted: Thu Nov 01, 2012 10:40 pm    Post subject: Reply with quote

Acolyte

Joined: 26 Oct 2005
Posts: 65

We are on Oracle 10g, WMB 6.1.0.4 and AIX 5.3
_________________
Sanjoo

Keep smiling
Back to top
View user's profile Send private message
sanjoo
PostPosted: Fri Nov 02, 2012 12:58 am    Post subject: Reply with quote

Acolyte

Joined: 26 Oct 2005
Posts: 65

My bad.. we are receiving 'HY000' (and not HY001)
_________________
Sanjoo

Keep smiling
Back to top
View user's profile Send private message
rekarm01
PostPosted: Fri Nov 02, 2012 1:08 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

What is the complete exception? (A usertrace may help here.)
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Nov 02, 2012 4:42 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Are you using the ODBC drivers supplied with WMB?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sanjoo
PostPosted: Wed Nov 07, 2012 12:21 am    Post subject: Reply with quote

Acolyte

Joined: 26 Oct 2005
Posts: 65

Yes. We are using odbc drivers provided with WMB.
And let me reword the issue with more details:

===================================
MQ 7.0
WMB 6.1.0.8
AIX 5.3
Oracle 11g

Scenario:
MQInput (with transaction mode 'Yes') --> Compute node doing DB inserts and updates (with transaction mode 'Automatic' and throw exception on DB error checked)
Upon DB failure we handle it in catch path.

DB table looks like -
COL1 (varchar)
COL2 (varchar)
COL3 (Number) [ESQL CAST to DECIMAL]
COL4 (varchar)
COL5 (Date) [ ESQL CAST to DATE ]

If record already exists, then flow updates it.
If record doesn't exists, then flow inserts a record.


This works okay for happy scenarios.
However if we produce a genuine DB exception by tweaking input message,say "Numeric value out of range" then it throws a DB exception and the failure is handled by the exception handler.
If another valid message, which works okay otherwise is played immediately after above DB exception, subsequent INSERT/UPDATE into the same table fails.
For INSERT -> HY000 "Value to large for column
For UPDATE -> HY000 "Inconsistent datatype:Expected number but got Date"
We have made sure we are passing values to querry in correct order. So my doubt is are column values getting swapped in this particular scenario.
I got this theory from below link-
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IC74779

However, if I wait for couple of minutes and again play the same message it passes through successfully. But the mystery is what happens in couple of minutes that makes it work again?

=============================
Note:
If I alter my table like -
COL1 (varchar)
COL2 (varchar)
COL3 (varchar) [ESQL CAST to CHAR]
COL4 (varchar)
COL5 (varchar) [ESQL CAST to CHAR]

Then it works okay as expected.
=============================


This is certainly not a code issue because it works okay on windows.

Thanks
_________________
Sanjoo

Keep smiling
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 » DB exception 'HY001'
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.