| Author |
Message
|
| murdeep |
 Posted: Wed May 14, 2008 7:27 am Post subject: Co-existance of V6 broker and V6.1 broker in same database |
 |
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Hello, I am in the process of planning my migration from V6.0 to V6.1. I've read that V6.0 and V6.1 components may co-exist. But I haven't read anywhere a statement that says "V6.0 broker and V6.1 broker may share the same database".
In one of my environments I have many brokers that share a common database. I assume that when I migrate the first one to V6.1 the others will still work. The reason I ask is because the messages when I migrate a broker are as follows:
BIP8670I: Database migration started
BIP8663I: Creating temporary new tables
BIP8664I: Migrating from existing tables to temporary new tables
BIP8665I: Dropping existing tables
BIP8666I: Creating new tables
BIP8667I: Copying all rows from temporary new tables to new tables
BIP8668I: Dropping temporary new tables
BIP8669I: Database migration successful
Also, can a v6.0 broker be created in a V6.1 broker database? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 14, 2008 7:32 am Post subject: Re: Co-existance of V6 broker and V6.1 broker in same databa |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| murdeep wrote: |
| Also, can a v6.0 broker be created in a V6.1 broker database? |
There's no such thing as a v6.n database - there's a DB2 database, or Oracle, or something (if v6.n supports somethings).
AFAIK all the tables for any v6.n broker are prefixed with the broker name, allowing coexistance. I agree that the table formats differ (requiring the conversion you correctly mention) but the database software doesn't mind that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| murdeep |
| Posted: Wed May 14, 2008 8:52 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
None of the tables in my database that support my V6.1 broker have the broker as part of the name. You may want to check where you got that info from.
Another thing I have noticed. After issuing the mqsimigratecomponents for my broker on W2K the broker component services ImagePath registry entry was still set to the V6.0 path. This had the effect of returning a BrokerVersion of 6007 in a message flow that I use to dump certain broker values even though the broker was V6.1.
I had to stop the broker and use regedit to update the registry settings for ImagePath for all of my migrated components. Then when I executed the flow it returned the BrokerVersion of 6100.
Has anyone run into this? Looks like mqsimigratecomponents doesn't update the broker service definitions in the W2K registry. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed May 14, 2008 8:14 pm Post subject: Re: Co-existance of V6 broker and V6.1 broker in same databa |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| Vitor wrote: |
AFAIK all the tables for any v6.n broker are prefixed with the broker name, allowing coexistance. |
co-existance is achieved by saving broker information with UUID... table names still stay the same... the entries in those tables are wrt UUID- corresponding to each broker...
_________________
Cheers |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 14, 2008 11:14 pm Post subject: Re: Co-existance of V6 broker and V6.1 broker in same databa |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| AkankshA wrote: |
| Vitor wrote: |
AFAIK all the tables for any v6.n broker are prefixed with the broker name, allowing coexistance. |
co-existance is achieved by saving broker information with UUID... table names still stay the same... the entries in those tables are wrt UUID- corresponding to each broker... |
So AFAIK wasn't far enough. I knew they were prefxed with something broker specific.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
