Scribd
Upload
5 views3 pages

Database Connection Troubleshooting Guide

The document is a technical checklist for diagnosing connection issues between clients and a database server. It includes steps to identify when the problem first occurred, any changes made, client connection details, server type, and firewall presence. Additionally, it outlines specific commands and tests to perform to gather necessary information for troubleshooting the issue.

Uploaded by

Diego Nisperuza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views3 pages

Database Connection Troubleshooting Guide

The document is a technical checklist for diagnosing connection issues between clients and a database server. It includes steps to identify when the problem first occurred, any changes made, client connection details, server type, and firewall presence. Additionally, it outlines specific commands and tests to perform to gather necessary information for troubleshooting the issue.

Uploaded by

Diego Nisperuza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Technical Checklist

A. When was the problem first seen?


- When was the problem first observed?

- Did this ever work before?

B. Were there any changes made?


- Were there any changes made to the Database or Client configuration?

C. Is the problem seen on all clients?


- Is the problem seen on all clients?

- If not, where is the problem NOT seen?

D. Client Connection Details (All 3 parts must be addressed)


- Was the sqlplus connection tested from the same APPS Server?

- What type of client connections are failing? (JDBC Thin, JDBC Thick, ODBC, .NET, Sqlplus)

- What version of driver is being used? (10.X, 11.1, 11.2, 12.1, 12.2 or higher)

- Can you reproduce with a plain Sqlplus connection? (user/password@alias)

E. Remote vs Local Connection Test


- When remote clients get the error, can you make a local BEQ connection from the server?

- Test with both a general user account and the SYSDBA account.

- Do both show the same issue?

- Please supply a screen capture if possible.

As SYSDBA:

1. set oracle_sid=SIDNAME

2. sqlplus /nolog

3. connect / as sysdba

As General User:

1. set oracle_sid=SIDNAME

2. sqlplus /nolog
3. connect user/password

Note: This step is only valid when taken at the same time clients are reporting the issue.

Example:

SQL> set time on


[Link] SQL> connect / as sysdba
Connected.
[Link] SQL>

F. Server Type
- Is this server a standalone or a RAC setup?

G. Client Type
- Are the clients using dedicated or shared server?

H. Resource Limits Output


- Log in with SYSDBA and run:

SQL> select * from v$resource_limit;

Note: This must be done before restarting the Listener or Database to preserve
MAX_UTILIZATION.

I. Listener Status
- Run:

LSNRCTL> status <listenername>

J. Upload [Link]
- Upload the [Link] from the instance/service in question.

K. Upload [Link]
- Upload the [Link] file from the Database Home.

2. Firewall Questions

A. Firewall Presence
- Is there a firewall between the client and the database server?

Note: Load balancers can also act as firewalls.

B. Reproduction Inside Firewall


- If yes, can you reproduce the issue inside the firewall?
C. Idle Session Timeout
- Does your firewall have an idle session timeout set? If so, what is it?

D. Firewall Rules
- Does your firewall have any of the following rules active?

• SQLNet fixup protocol


• Deep Packet Inspection (DPI)
• SQLNet packet inspection
• SQL Fixup
• SQL ALG (Juniper firewall)

Reference: Document 742535.1

You might also like