Just a thought, you are using IP addresses for replication. But
hostname for Oracle, have you checked out local DNS issues with the
jdbc:oracle:thin:@hostname.company.com:1521:dbname ? Check the IP
address records are correctly setup, and everyone listed is connectable
and working. Check all your local DNS caching servers are operational.
However for DNS issues I would expect ping/ssh to be affected too.
Can you configure an IP address in the JDBC connection string ?
Do you have 2 default routes setup on your clustered boxes ? You do not
say in your original mail which directly connected network eth0 is on, I
now read it as 172.25.x.y from your follow up. What does your routing
table look like.
One reason why the oracle driver uses eth0 over eth1 is that when the
JDBC client opens the socket to connect it is not bound to any specific
interface. Where as with replication I'd guess the tcpListenAddress
forces which physical card it will use. Normal then the socket is
auto-bound (within the kernel) it will choose the default address of the
physical interface closest to the host (or gateway - if nto directly
connected).
Have you setup any interface aliasing that might confuse the kernel.
For example you have IP addresses in overlapping subnets on two physical
interfaces in the same host ?
When the JDBC client does get connected to the SQL server, what does
'netstat' show for the IP addresses of that connection ? Is it using
the 172.25.x.y:#### <--> 172.25.x.z :1521 as you expect ?
--
Darryl L. Miles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
