If you were logged in you would be able to see more operations.
|
|
|
Product Version: |
Oracle 10.2.0.4 Standard Edition, RAC
|
Operating System: |
Solaris
|
Operating System Version: |
10
|
Description:
The clients can not connect to the database with ORA-12545 error even if They can ping the database server.
Diagnostic Data for Oracle:
Remote and Local Listeners for Both Nodes:
Remote Listener Configuration for Both Nodes:
tns alias
sqlnet trace parameters
sqlnet trace
The host IP and port are resolved to <IP1> and 1521, respectively.
A connect packet (NSPTCN) sent to <IP1>.
A data packet (NSPTDA) sent to <IP1>.
Got a redirect packet (NSPTRD) from <IP1>.
Got a data packet (NSPTDA) from <IP1>.
As seen above, even if the initial request was sent to <IP1>, now it's redirected to an host named gdksun2.
Then, the client got ORA-12545 error.
|
Description
|
Description:
The clients can not connect to the database with ORA-12545 error even if They can ping the database server.
Diagnostic Data for Oracle:
Remote and Local Listeners for Both Nodes:
Remote Listener Configuration for Both Nodes:
tns alias
sqlnet trace parameters
sqlnet trace
The host IP and port are resolved to <IP1> and 1521, respectively.
A connect packet (NSPTCN) sent to <IP1>.
A data packet (NSPTDA) sent to <IP1>.
Got a redirect packet (NSPTRD) from <IP1>.
Got a data packet (NSPTDA) from <IP1>.
As seen above, even if the initial request was sent to <IP1>, now it's redirected to an host named gdksun2.
Then, the client got ORA-12545 error. |
Show » |
|
This is expected behavior as below:
For both cases, If listener sends an unreachable IP or hostname, client encounters an error.
Solutions: