Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

RAC11gR2 - unable to connect via SCAN - can connect directly on nodes

1008097May 9 2013 — edited May 15 2013
Hello,

I recently installed a two node RAC 11gR2 database on Oracle Linux. I'm trying to connect from an external windows client, using SQL Developer, but I keep getting the error "IO Error: The Network adapter could not establish the connection".

If I attempt to connect directly to one of the nodes (instead of putting the scan hostname I just use the node's hostname) it works without a problem. I'm thinking this might have something to do with a bad configuration on the scan listeners or the VIP.

After installing clusterware and the database I never manually configured any listener. I assume this was done automatically. Let me know what kind of information I should provide to make this easier to troubleshoot. I'm not using any hosts file entries (except the private interconnect hostnames) since everything has been configured on my DNS. This is the network schema I had in mind when creating the cluster (and it's how my DNS is configured):

#10.16.1.93 rac01-dev.elqrd.local rac01-dev -- public interfaces
#10.16.1.94 rac02-dev.elqrd.local rac02-dev

#10.16.1.95 rac01-vip.elqrd.local rac01-vip -- vip interfaces
#10.16.1.96 rac02-vip.elqrd.local rac02-vip

172.16.125.1 rac01-priv.elqrd.local rac01-priv -- private interconnect
172.16.125.2 rac02-priv.elqrd.local rac02-priv

#10.16.1.97 rac01-scan -- scan ip's
#10.16.1.98
#10.16.1.99

Here's the scan status of my cluster:

[grid@rac01-dev ~]$ srvctl config scan
SCAN name: rac01-scan.elqrd.local, Network: 1/10.16.1.0/255.255.255.0/eth0
SCAN VIP name: scan1, IP: /rac01-scan.elqrd.local/10.16.1.97
SCAN VIP name: scan2, IP: /rac01-scan.elqrd.local/10.16.1.98
SCAN VIP name: scan3, IP: /rac01-scan.elqrd.local/10.16.1.99


And here's the vip configuration:
[grid@rac01-dev ~]$ srvctl config vip -n rac01-dev
VIP exists.:rac01-dev
VIP exists.: /rac01-vip/10.16.1.95/255.255.255.0/eth0
[grid@rac01-dev ~]$ srvctl config vip -n rac02-dev
VIP exists.:rac02-dev
VIP exists.: /rac02-vip/10.16.1.96/255.255.255.0/eth0
[grid@rac01-dev ~]$


Here is the listener status:
grid@rac01-dev ~]$ lsnrctl service

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 09-MAY-2013 17:01:01

Copyright (c) 1991, 2009, Oracle. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:70 refused:0 state:ready
LOCAL SERVER
Service "ORCL" has 1 instance(s).
Instance "ORCL1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:83 refused:0 state:ready
LOCAL SERVER
Service "ORCLXDB" has 1 instance(s).
Instance "ORCL1", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: rac01-dev.elqrd.local, pid: 9331>
(ADDRESS=(PROTOCOL=tcp)(HOST=rac01-dev.elqrd.local)(PORT=64963))
The command completed successfully

It's the same on the second node, with the difference that it refers to the other instances (+ASM2, ORCL2)



A similar thread suggested I post this information also:
select inst_id, name, value from gv$parameter where name like '%_listener%'

1 local_listener (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rac01-vip)(PORT=1521))))
1 remote_listener rac01-scan.elqrd.local:1521
2 local_listener (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rac02-vip)(PORT=1521))))
2 remote_listener rac01-scan.elqrd.local:1521

Edited by: 1005094 on May 9, 2013 2:01 PM
Added listener status information

Edited by: 1005094 on May 9, 2013 2:06 PM

Edited by: 1005094 on May 9, 2013 2:17 PM
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 12 2013
Added on May 9 2013
8 comments
4,411 views