| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP8146E when trying to migrate broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| sjensen |
 Posted: Thu Feb 02, 2006 9:50 am Post subject: BIP8146E when trying to migrate broker |
 |
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
When I do
| Code: |
| mqsimigratecomponents TSTBRK |
I get this:
BIP8146E: Unable to retrieve the SQL primitives supported by the Database. The command attempted to retrieve the SQL primitives that the Database supports, however the primitives retrieved
indicate that the Database could not be contacted successfully. Refer to the Administration Guide for information about
Database setup, ensure that the Database libraries are available in the library path and that the ODBC ini file is correct.
I've checked that LD_LIBRARY_PATH, NLSPATH, LANG and LC_ALL are set.
I've modified the .odbc.ini file as per the documentation. The entry is:
| Code: |
Driver=/new/opt/IBM/mqsi/6.0/merant/lib/UKor820.so
Description=DataDirect 5.0 Oracle
EnableDescribeParam=1
OptimizePrepare=1
ServerName=MQSU02.NY.JPMORGAN.COM
WorkArounds=536870912
ProcedureRetResults=1
|
I do have 2 brokers on this machine and I know they have to be migrated at the same time but I can find no way to specify both brokers in the mqsimigratecomponents call so I presume you do them one after the other.
Environment: Solaris 8, WMQ 5.3 with CSD8, WMB 6, and WMQI 2.1 with CSD6
I get an error when I do the migratrion check:
| Code: |
mqsimigratecomponents -c TSTBRK
BIP8849I: Broker 'TSTBRK' (Version 2.1) with Queue Manager 'TSTBRK' and Data Source 'MQSU02' specified for migration.
BIP8678W: Component 'TSTBRK' is sharing a database schema with component 'NYCSBRK'. These components must be migrated together.
BIP8791I: Duplicate rows check started.
BIP8794I: Table BRMINFO has no duplicated rows.
BIP8794I: Table BRMRTDDEPINFO has no duplicated rows.
BIP8794I: Table BROKERRESOURCES has no duplicated rows.
BIP8794I: Table BRMRTDINFO has no duplicated rows.
BIP8794I: Table BRMWFDINFO has no duplicated rows.
BIP8792I: Duplicate rows check passed.
BIP8681W: Pre-migration check failed.
BIP8071I: Successful command completion.
|
but as there are no duplicated rows I assume it is because I have 2 brokers.
Many thanks
Stefan |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Fri Feb 03, 2006 3:02 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Stefan,
Please raise a PMR. To speed things up, please could you include service trace:
| Code: |
| mqsireadlog TSTBRK -t -b mqsimigratecomponents -f -o trace.xml |
Cheers
-Matt |
|
| Back to top |
|
|
| sjensen |
| Posted: Sun Feb 05, 2006 6:19 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi Matt,
Thanks again. PMR is 26424,7TD.
One thing I forgot to mention the old brokers uses NEON but the codebase I have for WMB 6 does not include the rulse and formmater extension. Could this be the problem?
Thanks
Stefan |
|
| Back to top |
|
|
| sjensen |
| Posted: Tue Feb 07, 2006 9:15 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi Again,
I removed obsolete sybase etc. entries from the odbc.ini file as suggested by IBM. I also move the WMB6 entries to the front of env. vars. like NLSPATH, PATH etc. Cleaned up some VCS DB problems on the NEON DB and now the test broker migrated fine 
Then I charged on trying to convert the next broker.
| Code: |
| mqsimigratecomponents -c <broker> |
gave no errors but the actual migration failed with:
| Code: |
BIP8070E: Exception accessing database table executing SQL statement 'SELECT BrokerUUID , SubscriptionId , ClientId , Expiration , Creation , Options , ApplIdentity , SubPoint , Topic , Filter FROM MQSIFIRE.BSUBSCRIPTIONS': SQL state '904'; exception 'ImbException'.
An SQL command has failed.
|
AFAIK 904 is an exceeded resource but I do not know which resource.
Also the select statement has ApplIdentity which is not in the table :
| Code: |
describe MQSIFIRE.BSUBSCRIPTIONS;
Name Null? Type
----------------------------------------- -------- ----------------------------
BROKERUUID NOT NULL RAW(16)
CLIENTID NOT NULL RAW(254)
SUBSCRIPTIONID NOT NULL RAW(60)
TOPIC BLOB
SUBPOINT RAW(128)
FILTER BLOB
EXPIRATION RAW(38)
CREATION RAW(38)
OPTIONS NUMBER
SUBINFO BLOB
|
Ah well I guess one broker in a day is enough 
Thanks
Stefan[/code] |
|
| Back to top |
|
|
| sjensen |
| Posted: Wed Feb 08, 2006 7:57 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
I now know what the problem is. It seems when you convert the first broker it alters the BSUBSCRIPTIONS table.
WMQI 2.1:
| Code: |
describe MQSIFIRE.BSUBSCRIPTIONS;
Name Null? Type
----------------------------------------- -------- ----------------------------
BROKERUUID NOT NULL RAW(16)
CLIENTID NOT NULL NUMBER
SUBSCRIPTIONID NOT NULL RAW(60)
TOPIC BLOB
SUBPOINT RAW(128)
FILTER BLOB
EXPIRATION RAW(38)
CREATION RAW(38)
OPTIONS NUMBER
APPLIDENTITY RAW(64)
|
After migrating first broker to WMB 6:
| Code: |
describe MQSIFIRE.BSUBSCRIPTIONS;
Name Null? Type
----------------------------------------- -------- ----------------------------
BROKERUUID NOT NULL RAW(16)
CLIENTID NOT NULL RAW(254)
SUBSCRIPTIONID NOT NULL RAW(60)
TOPIC BLOB
SUBPOINT RAW(128)
FILTER BLOB
EXPIRATION RAW(38)
CREATION RAW(38)
OPTIONS NUMBER
SUBINFO BLOB
|
So APPLIDENTITY RAW(64) is now SUBINFO(BLOB). Hence the 'The brokers must be migrated at the same time' problem was there I found now way of doing that.
Now when trying to migrate the 2nd broker the select statement reasonably enough throws an error:
| Code: |
Caught exception and rethrowing' , 'SELECT BrokerUUID , SubscriptionId , ClientId , Expiration , Creation , Options , ApplIdentity , SubPoint , Topic , Filter FROM MQSIFIRE.BSUBSCRIPTIONS'
2006-02-07 09:52:43.161364 1 DatabaseException BIP2322E: Database error: SQL State ''42S22''; Native Error Code '904';
Error Text ''[DataDirect][ODBC Oracle driver][Oracle]
ORA-00904: "APPLIDENTITY": invalid identifier ''.
|
So looks a bit stuck apart frrom converting the SUBINFO(BLOB) back to AppIdentity which sounds rather risky.
Thanks
Stefan |
|
| Back to top |
|
|
| sjensen |
| Posted: Wed Feb 08, 2006 9:45 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
although I guess doing
| Code: |
mqsimigratecomponents -c -3 TSTBRK
mqsimigratecomponents SecondBroker
|
Might work as the first command will undo the database work and the second will redo it.
Hardly likely to be blessed though and a database backup first might be a good idea 
Cheers
Stefan |
|
| Back to top |
|
|
| sjensen |
| Posted: Thu Feb 09, 2006 2:32 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
Actually there is a blessed and simples way. For the second broker you only need to do a partial migration. So migrate the first broker then just do:
| Code: |
| migratecomponents -1 SecondBroker |
Using mqsimigratecomponents -2 and -3 afterwards both gave:
'The source and target are compatible, no migration needed'
Sadly though it appears the '-2' flag should have added new queues as a test flow through the first broker works but for the second broker I get
| Code: |
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.AGGR.CONTROL' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.AGGR.REPLY' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.AGGR.REQUEST' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.AGGR.TIMEOUT' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.AGGR.UNKNOWN' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.TIMEOUT.QUEUE' is missing
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.INTERBROKER.MODEL.QUEUE' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.WS.ACK' is missing.
BIP8705S: WebSphere MQ queue 'SYSTEM.BROKER.WS.INPUT' is missing.
|
|
|
| Back to top |
|
|
| sjensen |
| Posted: Mon Feb 20, 2006 9:03 am Post subject: BIP8146E when trying to migrate broker - Solved |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
IBM came through. Here are the steps needed:
Reverse the registry migration of the SecondBroker broker, taking the registry/file entries back to the WMQI 2.1 format:
| Code: |
mqsimigratecomponents SecondBroker -s 6.0.0.0 -t 2.1.0.8 -1
|
Now migrate both the WMQI 2.1 registry/file entries and the WebSphere MQ resources to 6.0.0.0.
| Code: |
mqsimigratecomponents SecondBroker -1 -2
|
This worked and both brokers are running and functional |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
