| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB 6.1 failed to connect in terms of RAC failover |
« View previous topic :: View next topic » |
| Author |
Message
|
| Adreno |
 Posted: Tue Aug 04, 2009 2:13 am Post subject: WMB 6.1 failed to connect in terms of RAC failover |
 |
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Hey guys,
I´m actually struggling a bit with my WMB RAC setup. So we use WMB 6.1.0.3 and RAC 11g and all looked quite simple but the failover configuration.
Actually we installed a local ora client on each machine and use the tnsnames.ora which looks like this (without the blabla  )
tnsnames.ora:
------------------------------------
STEMB1 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = blabla)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = blabla)(PORT = 1521))
(FAILOVER = ON)
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = STEMB1)
)
)
-----------------------------------
So servicename is also referenced in the odbc.ini:
.odbc.ini
-----------------------------------
[TEMB01]
Driver=/usr/opt/mqsi/6.1.0.3/ODBC64/V5.3/lib/UKora23.so
Description=DataDirect 5.0 Oracle
EnableDescribeParam=1
OptimizePrepare=1
ServerName=STEMB1
WorkArounds=536870912
ProcedureRetResults=1
----------------------------------
Both RAC nodes are in the tnsnames so failover should be no prob, but indeed it is when the service moves to second node. Then I get an connection error while connection works fine if its all in place on the first node.
Cheked tns connection parameters during failover with the tnsping and sqlplus as broker user and this works also.
tnsping:
-------------------------------------
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = blabla)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = blabla)(PORT = 1521)) (FAILOVER = ON)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = STEMB1)))
OK (50 msec)
-------------------------------------
See error:
Aug 4 11:50:17 machine user:info WebSphere Broker v6103[1290274]: (TEMB01)[1]BIP8873I: Starting the component verification for component 'TEMB01'. : TEMB01.mqsistart: /build/S610_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 74: ImbComponentVerification::verify: :
Aug 4 11:50:18 machine user:err|error WebSphere Broker v6103[1290274]: (TEMB01)[1]BIP2322E: Database error: SQL State '08S01'; Native Error Code '0'; Error Text '[IBM][ODBC 20101 driver]7505'. : TEMB01.mqsistart: /build/S610_P/src/CommandLine/ImbCmdLib/ImbDatabaseVerification.cpp: 101: ImbDatabaseVerification::verify: :
Aug 4 11:50:18 machine user:err|error WebSphere Broker v6103[1290274]: (TEMB01)[1]BIP8891E: Verification failed. Failed to connect to datasource 'TEMB01' with user ID 'temb01'. Preceding messages contain further information. : TEMB01.mqsistart: /build/S610_P/src/CommandLine/ImbCmdLib/ImbDatabaseVerification.cpp: 222: ImbDatabaseVerification::verify: :
Aug 4 11:50:18 user:warn|warning WebSphere Broker v6103[1290274]: (TEMB01)[1]BIP8875W: The component verification for 'TEMB01' has finished, but one or more checks failed. : TEMB01.mqsistart: /build/S610_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 140: ImbComponentVerification::verify: :
Any ideas??
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Aug 04, 2009 3:41 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Its prompting user id is not authenticated or authorized to connect
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Adreno |
| Posted: Tue Aug 04, 2009 4:04 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Exactly,
but this makes absolutely no sense cause username and passwort ist the same on the service, except the listener of the oracle nodes are different.
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
|
| Adreno |
| Posted: Tue Aug 11, 2009 3:14 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Hi,
Problem was solved so here´s the solution:
In our tnsnames.ora virtual ip adresses were reffered for db connection to each db node. In this case this virtual ip is moved in terms of failover to the second node but there is no listener that can handle the request.
Instead of recieving a connect reset the broker misunderstood the connection problem and mentioned a username error.
While using physical ip adresses in the tnsnames the failover workes properly.
Thread closed!
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| 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
|
|
|
|
