Current network environment: oracle11gr2+rhel6.4_x86_64 Two-node RAC
scanip:192.168.1.100
Service-name:orcl
Node Instance name: ORCL1, Orcl2
Symptom: The application server in the same network segment uses the JDBC Connection Scanip,url address is:
JDBC:ORACLE:THIN:@192.168.1.100:1521:ORCL,
According to the developer, it has been written before, there was no problem, but now the environment
is not connected, developers always think that there is a problem with the database, you can only start from the database
Level to exclude, after testing to determine the database monitoring, RAC-related services are normal,
So the positioning problem should be in the form of JDBC, or other procedural problems.
After consultation and verification, only know that there is scanip when JDBC to write in the following format
Jdbc:oracle:thin:@{scan-listener-hostname}:{port}/{service-name}
Then changed to: JDBC:ORACLE:THIN:@192.168.1.100:1521/ORCL
Finally can, hehe, is the accumulation of a little experience it
Web application failed to connect to RAC database using JDBC