Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / December 2007

Tip: Looking for answers? Try searching our database.

UDB with MQ v6 as XA coordinator

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
TheAndroid - 03 Dec 2007 17:50 GMT
Hi all,
  I am getting a message from UDB:
FATAL SQL ERROR
SQL0998N  Error occurred during
transaction or heuristic processing.
Reason Code = "9". Subcode = "".
SQLSTATE=58005
SQLSTATE 58005: A system error (that
prevents the successful execution of
subsequent SQL statements) occurred.

I was wondering if anyone had seen this before. I am using MQ v6 as a
transaction coordinator for a 32bit COBOL program. When I was running
V5.3, this worked fine. Now, I'm getting these errors. I rebuilt the
switch files as directed and made sure it was in the correct
directory.
  I know MQ is trying to use the 32 bit version as I can rename the
one in /var/mqm/exits and it will complain when I do MQBEGIN. However,
the documentation at boulder says it should be using the 64 bit one.
If I delete the 32 bit db2swit file, I get 2212 errors
(RESOURCE_MANAGER_NOT_FOUND) errors so it is demanding the 32
version.
  I'm at a loss on this as when I do db2 ? sql0998 the response shows
two subcodes. Neither of which I'm getting. db2diag on the server
doesn't show anything either.

Help!
TheAndroid - 12 Dec 2007 15:07 GMT
Just a ping to ask for help on this again!

Thanks
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.