Author |
Message
|
sarathmattam |
Posted: Sun Nov 18, 2012 11:58 pm Post subject: Migration to MB 8.0.0.1 Fails at Stage 3 |
|
|
Voyager
Joined: 05 Sep 2008 Posts: 94
|
Dear All,
I am trying to migrate MQ and WMB on Solaris x86-64 System. Details are mentioned below.
Current Version :
MQ : 6.0
WMB : 6.1.0.10 ( It was 6.1.0.2 and i applied patch as a part of migration)
DB2 : 9.1.3
Targeted Version:
MQ : 7.1.0.0
WMB : 8.0.0.1
DB2 : 9.1.3
Current Status : I have completed the migration of MQ and started the queue managers and it works fine. The migration of publish/subscribe components are also completed and i can see the Subscriptions and Topics created under the queue manager. When i try to migrate my brokers, am getting the below error
"solaris10% mqsimigratecomponents TST.OTH.BRK
BIP8849I: Broker 'TST.OTH.BRK' (Version 6.1) with Queue Manager 'TST.OTH.BRK.QMGR' and Data Source 'TSTBRKDB' specified for migration.
BIP8040E: Unable to connect to the database.
BIP2393E: Database error: ODBC return code '-1' from data source ''TSTBRKDB'' using ODBC driver manager ''''.
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration.
BIP2347E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.'
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0'
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.
BIP8851S: Migration Failed
One of the migration steps failed, please see messages above for more details.
"
When i did a step by step migration, steps 1 and 2 went fine, but the 3rd failed.
My odbc.ini and odbcinst.ini files are as below
solaris10% cat odbc.ini
;##########################################################################
;# ODBC database driver manager initialisation file. #
;##########################################################################
;# It is recommended that you take a copy of this file and then edit the #
;# copy. #
;# #
;# 1. For each data source, add the name of the data source into #
;# the 'List of data sources stanza' section. #
;# #
;# 2. For each data source, create a stanza in the #
;# 'Individual data source stanzas' section. #
;# #
;##########################################################################
;#######################################
;#### List of data sources stanza ######
;#######################################
[ODBC Data Sources]
TSTBRKDB=IBM DB2 ODBC Driver
;#TSTAPPDB=IBM DB2 ODBC Driver
ORACLEDB=DataDirect 6.0 ODBC Oracle Wire Protocol
ORACLERACDB=DataDirect 6.0 ODBC Oracle RAC Wire Protocol
SYBASEDB=DataDirect 6.0 ODBC Sybase Wire Protocol
SYBASEDBUTF8=DataDirect 6.0 ODBC Sybase UTF8 Wire Protocol
INFORMIXDB=IBM Informix ODBC Driver
SOLIDDB_DB=IBM Solid DB ODBC Driver
;###########################################
;##### Individual data source stanzas ######
;###########################################
;# DB2 stanza
[TSTBRKDB]
DRIVER=/opt/IBM/db2/V9.1/lib64/libdb2o.so
Description=IBM DB2 ODBC Database
Database=TSTBRKDB
;#[TSTAPPDB]
;#DRIVER=/opt/IBM/db2/V9.1/lib64/libdb2o.so
;#Description=IBM DB2 ODBC Database
;#Database=TSTAPPDB
;# Oracle stanza
[ORACLEDB]
Driver=<Your Broker install directory>/ODBC/V6.0/lib/UKora24.so
Description=DataDirect 6.0 ODBC Oracle Wire Protocol
HostName=<Your Oracle Server Machine Name>
PortNumber=<Port on which Oracle is listening on HostName>
ServiceName=<Your Oracle Service Name>
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
LoginTimeout=0
;# Oracle Real Application Clusters stanza
[ORACLERACDB]
Driver=<Your Broker install directory>/ODBC/V6.0/lib/UKora24.so
Description=DataDirect 6.0 ODBC Oracle RAC Wire Protocol
HostName=<Your Oracle Server Machine Name>
PortNumber=<Port on which Oracle is listening on HostName>
ServiceName=<Your Oracle Real Application Cluster Service Name>
;#This shows one alternate server definition. Add extra ones using a ',' to seperate each definition.
AlternateServers=(HostName=<Your alternative hostname>:PortNumber=<Port number on which Oracle is listening on the alternative host>:ServiceName=<Your Oracle Real Application Cluster Service Name>)
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
LoginTimeout=0
;# Sybase Stanza
[SYBASEDB]
Driver=<Your Broker install directory>/ODBC/V6.0/lib/UKase24.so
Description=DataDirect 6.0 ODBC Sybase Wire Protocol
Database=<Your Database Name>
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=<Your Sybase Server Name>,<Your Sybase Port Number>
SelectUserName=1
ColumnSizeAsCharacter=1
EnableSPColumnTypes=2
LoginTimeout=0
TimestampTruncationBehavior=1
XAConnOptBehavior=3
;# Sybase Stanza for a UTF8 datasource
[SYBASEDBUTF8]
Driver=<Your Broker install directory>/ODBC/V6.0/lib/UKase24.so
Description=DataDirect 6.0 ODBC Sybase UTF8 Wire Protocol
Database=<Your Database Name>
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
SelectMethod=0
NetworkAddress=<Your Sybase Server Name>,<Your Sybase Port Number>
SelectUserName=1
ColumnSizeAsCharacter=1
Charset=UTF8
EnableSPColumnTypes=2
LoginTimeout=0
TimestampTruncationBehavior=1
XAConnOptBehavior=3
;# Informix Stanza
[INFORMIXDB]
Driver=libinfWrapper.so
Description=IBM Informix ODBC Database
ServerName=<Your Informix Server Name>
Database=<Your Database Name>
;# Solid DB Stanza
[SOLIDDB_DB]
Driver=<Your SolidDB install Directory>/bin/socs0xi6465.so
Description=IBM Solid DB ODBC database
Database=SOLIDDB_DB
;##########################################
;###### Mandatory information stanza ######
;##########################################
[ODBC]
InstallDir=/opt/IBM/mqsi/8.0.0.1/ODBC/V6.0
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8
solaris10% cat odbcinst.ini
;##########################################################################
;# ODBC database driver manager system initialisation file. #
;##########################################################################
;# It is recommended that you take a copy of this file and then edit the #
;# copy. #
;# #
;# 1. Complete the 'Mandatory information stanza' section #
;# at the end of the file. #
;# #
;##########################################################################
;##########################################
;###### Mandatory information stanza ######
;##########################################
[ODBC]
;# To turn on ODBC trace set Trace=yes
Trace=yes
TraceFile=/export/ibm/home/mbid/odbctrace.out
Threading=2
Now, when i try to connect manually to the broker database using the broker service ID, its connecting.
Any pointers to fix this would be of great help
Thank you,
Sarath |
|
Back to top |
|
 |
marko.pitkanen |
Posted: Mon Nov 19, 2012 1:41 am Post subject: |
|
|
 Chevalier
Joined: 23 Jul 2008 Posts: 440 Location: Jamsa, Finland
|
Hi Sarath,
Have you verified that ODBCINI environment variable is set and pointing to correct file before you run your migration command?
--
MArko |
|
Back to top |
|
 |
sarathmattam |
Posted: Mon Nov 19, 2012 2:48 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008 Posts: 94
|
Dear Marko,
Yes. I checked it and its setting properly.
my .profile file is as below
# This is the default standard profile provided to a user.
# They are expected to edit it to meet their own needs.
MAIL=/usr/mail/${LOGNAME:?}
. /opt/IBM/mqsi/8.0.0.1/bin/mqsiprofile
. /export/ibm/home/db2inst1/sqllib/db2profile
ODBCINI=/var/mqsi/odbc.ini
export ODBCINI
ODBCSYSINI=/var/mqsi/
export ODBCSYSINI
solaris10% echo $ODBCINI
/var/mqsi/odbc.ini
solaris10% echo $ODBCSYSINI
/var/mqsi/
Regards,
Sarath |
|
Back to top |
|
 |
marko.pitkanen |
Posted: Mon Nov 19, 2012 4:58 am Post subject: |
|
|
 Chevalier
Joined: 23 Jul 2008 Posts: 440 Location: Jamsa, Finland
|
And you have done all the necessary steps described in this document ?
--
Marko |
|
Back to top |
|
 |
sarathmattam |
Posted: Mon Nov 19, 2012 5:17 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008 Posts: 94
|
Dear Marko,
Yes. I did. My odbc.ini and odbcinst.ini is pasted in my previous post. Do you find any mistakes in those ?
Regards,
Sarath |
|
Back to top |
|
 |
sarathmattam |
Posted: Tue Nov 20, 2012 2:09 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008 Posts: 94
|
Dear All,
As i was not able to find a solution to my migration issue, i tried to create a new broker using MB 8.0 and tried to connect to database. But, there also am getting the same exception . So, i think its a common problem.
Could any one point out any configuration that i missed from the information above.
Regards,
Sarath |
|
Back to top |
|
 |
sarathmattam |
Posted: Tue Nov 20, 2012 11:53 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008 Posts: 94
|
Dear All,
The issue is fixed now .. I had to download IE02 Support pack which contains the libraries for connecting to DB. After installing this migration was smooth ..
Regards,
Sarath |
|
Back to top |
|
 |
j.f.sorge |
Posted: Mon Feb 25, 2013 7:49 am Post subject: |
|
|
Master
Joined: 27 Feb 2008 Posts: 218
|
Thanks for posting your solution! We had the same error and could solve our problem the same way! _________________ IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
NealM |
Posted: Mon Feb 25, 2013 1:39 pm Post subject: |
|
|
 Master
Joined: 22 Feb 2011 Posts: 230 Location: NC or Utah (depends)
|
Yes, I suggest you read "Configuring the WebSphere Message Broker ODBC Database Extender" in your v8.0.0.1 InfoCenter. The IE02 support pac was evidently supposed to be included as part of the Broker runtime install for all unix systems, but appears to have been forgotten by the packaging folks on several platforms, Solaris and zLinux having both been noted in prior posts.
For a quick check of your own installation, just go to /opt/ibm and see if there is an IE02 folder; It should appear at the same level as the mqsi folder. |
|
Back to top |
|
 |
tsuru |
Posted: Tue Jul 02, 2013 10:25 am Post subject: |
|
|
Novice
Joined: 25 Nov 2005 Posts: 24 Location: São Paulo
|
I had the same problem on AIX 7.1 Installing IE02 solved my problem! |
|
Back to top |
|
 |
|