I would suggest enabling client side tracing. How you go about that depends
heavily on the application. If you are unable to do that, enable server
side tracing to find out exactly what is happening when the connection
takes place.
Something I have run into in the past is being able to connect to the SCAN
listeners but hitting the firewall when the SCAN listener does the hand-off
to a local listener. The way to make sure is to force your application to
connect to a local listener directly instead of going through SCAN.
Seth Miller
On Wed, Jul 20, 2016 at 12:17 PM, Chris King <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
Need your thoughts:
This is on Oracle RAC 11.2.0.4, using scan listener
Issue: A new user created on a new system is trying to connect remotely to
the Oracle RAC database. The listener.log file indicates the connection is
established with a "0" indicating success. However, I put a trigger on the
user to dump trace files on logon, and no trace files exist. Also, there
are no queries listed for that user in the gv$session + gv$sqlarea. So it
looks like the listener indicates user connected successfully, but there is
no trace of a connection in the database.
The application hangs and eventually returns with a timeout error.
We have verified that telnet to the port from the new server to the
database server is working. The application uses jdbc, and so we can not
test using tnsping or sqlplus.
Has anyone experienced a similar issue before? Any thoughts on what it
could be or what further troubleshooting I can do to figure this out? Would
listener tracing work on a scan listener?
Thanks in advance.
