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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED]FMC34534E: DB2INSTANCE is incorrect or not set.

Post new topic  Reply to topic
 [SOLVED]FMC34534E: DB2INSTANCE is incorrect or not set. « View previous topic :: View next topic » 
Author Message
lboni
PostPosted: Fri Jul 25, 2003 2:04 pm    Post subject: [SOLVED]FMC34534E: DB2INSTANCE is incorrect or not set. Reply with quote

Novice

Joined: 12 Jun 2003
Posts: 12
Location: San Francisco
I just migrated from MQ5.2 to MQ5.3 on my Workflow cluster (AIX). I am now getting the following message: FMC34534E: DB2INSTANCE is incorrect or not set.

I did the same thing yesterday in development without a problem. The only difference between the two environments is that today's have a remote database, yesterday's upgrade had a local database.

I have updated my db2swit file according to IBM's instructions and have check my fmcrc config file to make sure the configuration for my DB2 instance is correct. I have also checked qm.ini to make sure MQSeries is calling the correct XA transation/database. My database is remote. I have a call open to IBM support but have not heard back from them yet and this is urgent. Does anyone have any ideas?
Back to top
View user's profile Send private message
lboni
PostPosted: Wed Aug 13, 2003 3:07 pm    Post subject: Reply with quote

Novice

Joined: 12 Jun 2003
Posts: 12
Location: San Francisco
Thought I'd post a resolution:

The problem wasn't with my remote database. Turns out that if you have a remote database, the error message above is 'normal'. It doesn't really make sense to me but there it is.

The issue turned out to be with a fix that is required for MQSeries 5.3 CSD03. The fix is IY43610.

MQ V5.3 - C++ INTERFACE INCORRECT WHEN FIX PACK CSD03 (SERVICE LEVEL 5.3.0.3) HAS BEEN APPLIED. This problem can cause variety of symptoms including segmentation violation in MQ and abnormal termination of applications. Diagnostics (FDCs etc) may not be produced and trace can look very strange. The size of the xihThread structure has changed in MQ 5.3 and so IBM should ship the libraries that contain the information about this structure. These were omitted from CSD03 and therefore it was possible for any program using a xihThread structure to fail intermittently and in strange ways. It seems information is being written to the wrong place in the changed xihThread structure and this eventually causes an MQ failure.
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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED]FMC34534E: DB2INSTANCE is incorrect or not set.
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.