This allows more time to establish the connection:įor example, if you use the value 600 for all parameters, then the connection time is set to 10 minutes. If you get the error because of a slow network, then configure the following parameters on the client side and server side.Even after the tracing parameters are removed, the tracing for the already connected sessions on the server side is stopped only after the client session is closed. To turn off tracing, remove the tracing parameters from the sqlnet.ora file. Create a backup of the sqlnet.ora file, and then modify the following parameters in the file: Then, reproduce the error and capture the details in the trace files. Turn on sqlnet tracing on the client side.For more information, see Modifying connection properties using sqlnet.ora parameters. You can modify these values according to your use case. The parameter values mentioned in this article are examples. Also, be sure that the server has sufficient disk space available. Therefore, it's a best practice to turn on tracing during non-peak business hours or under isolated conditions when no other user is connecting to the database. The process also requires close monitoring. In rare cases, the listener or even the database might need to be restarted to stop tracing after the troubleshooting is completed. A large number of trace files might be generated quickly. Important: Turning on server-level tracing might have a few potential impacts. If you're using the default parameter group, then create a custom parameter group, modify the following parameters, and then modify the instance to use the newly created parameter group. To turn on tracing on the server side, modify the custom parameter group attached to the instance. If you're using the JDBC Thick or OCI client, then turn on sqlnet tracing on the server side.network failure, which can cause connection tests and applications to hang for.
#Oracle jdbc thin client login hangs no error driver#
For more information, see Oracle documentation for Doc ID 793415.1. WLS is asking a JDBC driver for a connection and getting that exception. Therefore, if you're using the Oracle JDBC Thin driver, perform the equivalent of SQL*Net Client Tracing with Oracle JDBC Thin Driver.
If the application connects from an on-premises network, then make sure that the firewall rules are updated to allow connections to and from the RDS instance.