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 » Coexistence Problem (MB5 and MB6)

Post new topic  Reply to topic
 Coexistence Problem (MB5 and MB6) « View previous topic :: View next topic » 
Author Message
ayanc
PostPosted: Tue Nov 14, 2006 11:05 pm    Post subject: Coexistence Problem (MB5 and MB6) Reply with quote

Voyager

Joined: 15 Nov 2004
Posts: 88

Hi All,

We have planned to upgrade to MB6 from MB5. We have installed MB6 in the same m/c (with MB5 running perfectly).

MB5 has been affected rather strangely.

1. The Problems view show that Broker is not Running, Execution Group is not running. However the deploy is working ... ()

2. I am getting the following 3 errors in the event viewer

1st Error
==============================================
( WBRK_BROKER.default ) Message broker internal error: diagnostic information 'DynamicSubscriptionEngine'.

An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: 'DynamicSubscriptionEngine'.

Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
==============================================

2nd Error
===============================================
( WBRK_BROKER.default ) Database error: ODBC return code '-1'.

The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.

Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
===============================================

3rd Error
===============================================
( WBRK_BROKER.default ) Database error: SQL State '38553'; Native Error Code '-443'; Error Text '[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553 '.

The error has the following diagnostic information: SQL State '38553' SQL Native Error Code '-443' SQL Error Text '[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553 '

This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
==============================================

3. My Subscriptions are not working. In MB5 I am not able to register any subscriptions.

Another error that is very new to me is as follows:
==============================================
ConfigMgr ) Error casting character string 'ConfigMgr' to a TIMESTAMP

The character string must have a TIMESTAMP format, for it to be castable to a timestamp.

Ensure that the string being cast is formatted correctly. Examples of correct formats include 'yyyy-mm-dd hh:mm:ss[.f+]' and 'yyyy-mm-dd hh:mm:ss[.uuu]'.
==============================================

I could go on with the list of errors ... but anyway if you want me to I will definitely post them. I had to uninstall the entire set up and reinstall a number of times ... facing new problems every time. However currently I am facing this problem.

I think installing both versions in the same m/c is creating all this trouble. Can anyone give me an idea as to a suitable course of action. Sadly I need to have both of em in a single m/c.

Now for the system details:

Win XP SP2
WMQ 5.3 CSD 10
WBIMB 5.0 CSD 5
DB2 8.1 Fixpack 13
WBIMB 6.0 ( CMVC Level: S000-L50920.2 DH000-L50920)

I have a separate queue manager for v5 with both ConfigMgr and Broker sharing the same qmgr.

I have a separate queue manager for v6 with both ConfigMgr and Broker sharing the same qmgr.

Could you please let me know if you need any further info?

Thanks.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 15, 2006 3:31 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I think you're trying to create the v6 broker tables in the same database and same schema as the v5 broker tables?

I think that doesn't work.

Drop your v6 configuration - don't uninstall.

Resolve any open issues with v5, without uninstalling software.

Then try recreating your v6 environment and make note of when it fails.

Also, you don't say if you're trying to MIGRATE the broker or COEXIST it.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
ayanc
PostPosted: Wed Nov 15, 2006 5:36 am    Post subject: Reply with quote

Voyager

Joined: 15 Nov 2004
Posts: 88

Hi Jeff,

Thanks for your reply. Sorry I forgot to mention about the database. I am using separate databases for v5 and v6 ... although in the same schema.

For example:
WBRKCMDB - ConfigMgr DB v5
WBRKBKDB - Broker DB v5
MB6BKDB - Broker DB v6

We intend to migrate ... but in a different way () . We are currently testing our interfaces in v5 and v6. We are then comparing the output messages, resolving probs and getting our interfaces ready for v6.

So, although our objective is migration ... we need both to co-exist for the entire testing duration.

Please feel free to ask for any info u need.

Thanks.
Back to top
View user's profile Send private message
Ward
PostPosted: Sat Nov 18, 2006 4:11 am    Post subject: Reply with quote

Voyager

Joined: 27 Jun 2001
Posts: 98
Location: Europe

have a look at this: http://www-1.ibm.com/support/docview.wss?uid=swg21215626
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ayanc
PostPosted: Tue Nov 21, 2006 3:57 am    Post subject: Reply with quote

Voyager

Joined: 15 Nov 2004
Posts: 88

Hi Ward,

Sorry for the delayed response. Thanx for that link. It really worked for me. I am able to register my subscriptions, and the error messages are gone.

Thanx.
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 » Coexistence Problem (MB5 and MB6)
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.