| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| migrating from V2.1 to V6.0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| harishre |
 Posted: Wed Jun 11, 2008 5:25 am Post subject: migrating from V2.1 to V6.0 |
 |
|
Apprentice
Joined: 29 May 2008
Posts: 27
|
Hello All,
While trying to create the broker to migrate from V2.1 to V6.0 i am getting the following error.
mqsicreatebroker IHUB01BR -i ihub01 -a ****** -q IHUB01 -n IHUB01BR -u ihub01 -p ******
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager 'IHUB01' starting.
9 log records accessed on queue manager 'IHUB01' during the log replay phase.
Log replay for queue manager 'IHUB01' complete.
Transaction manager state recovered for queue manager 'IHUB01'.
WebSphere MQ queue manager 'IHUB01' started.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8703S: Column 'RTD_MSG_SET_ALIAS' is missing from database table 'IHUB01.BRMRTDINFO'
BIP8703S: Column 'PROCARCHITECTURE' is missing from database table 'IHUB01.BROKERAAEG'
BIP8703S: Column 'QOPLEVEL' is missing from database table 'IHUB01.BACLENTRIES'
BIP8703S: Column 'CLIENTINFO' is missing from database table 'IHUB01.BCLIENTUSER'
BIP8703S: Column 'OPTIONS' is missing from database table 'IHUB01.BPUBLISHERS'
BIP8703S: Column 'SUBINFO' is missing from database table 'IHUB01.BSUBSCRIPTIONS'
BIP8703S: Column 'PASSWORD, PROTOCOL' is missing from database table 'IHUB01.BUSERNAME'
BIP8702W: Post-migration check failed; see previous messages for possible causes.
The migration utility found configuration errors for the component. This means that the component configuration is not correct in some way; previous messages should provide the exact errors.
Examine previous messages, and errors reported during migration steps, to determine the cause of the failure. The migration may need to be reversed, or completed manually.
Please tell me what I am missing.
background:
we had three broketrs on the same machine. all were at V2.1
One year ago two of the brokers were migrated successfully to V6.0.( I was not part of it that time  )
Now when i am trying to migrate the thrid one I am getting the above mentioned error.
please help me in this regard.
Harish |
|
| Back to top |
|
 |
| MrSmith |
| Posted: Tue Jun 24, 2008 8:14 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
| This thread is in nthe wrong topic - on eof the admin people needs to move it to WBIMB / MQSI etc etc forum then you may get more responses. This is the MQ installation config forum |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Jun 25, 2008 1:29 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Did you try running mqsimigratecomponents? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jun 25, 2008 1:40 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As you are trying to create a new broker, personaly, I would drop the broker database and re-create it.
My guess is that broker internally tries to use a certain table. If it is NOT there it creates all the tables needed for the V6.0 broker to use and then carries on with the broker creation.
If might be that the table broker uses as its check table has the same name as that used by V2.1. Thus the 'does it exist' check succeeds.
Another reason for starting with a clean database would be that the structure of tables between V2.1 & V6.0 may well have changed even if they have the same name.
Just my 0.02tenge worth.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| 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
|
|
|
|
