Session ID: 1164


Note: I presented this in 2015. A couple of IOUG Members (Noelle Stimely and Craig Shallahamer have requested I resubmit it)

Business Outcome:  Reducing and Preventing System Downtime

BTW, The Business Outcome is required to be something other than 'None'. so I just picked the closest appropriate choice.

Note: Mix of powerpoint and live demo

A user submits a trouble ticket: "Help! My application no longer connects to the database. It worked OK yesterday, but now after a few seconds I just get a message from the app that it cannot connect!"After following the usually litany of ensure the workstation is connected to the network, the database account is still active, the listener is up, etc., you start digging into the problem.

The next step might for the DBA to connect to the database herself.Since that worked, a remote session is started on the users workstation to find out what is happening.tnsping is usually the next step at this point. Hmm, that works OK.So, what now?Is your next step the Network Administrator? It could be a firewall issue after all.Oracle provides a wealth of information to track down network issues, maybe it is time to learn to use it.Do you know how to setup and use Oracle networking tracefiles ?Which tools can you use to parse any trace or log files?How about OS tracing utilities, can those be of any help?

There is no shortage of network related issue that a DBA must learn to cope with.Maybe the new trouble ticket is not for failure to connect, but slow access via the network.Now's the time to call the network admin, right? That may be the case, but now always.Oracle does provide methods to help troubleshoot network issues, and the issues may not be the fault of the network.

What about database links? Do you know how to find which sessions have also connected to remote databases?How do you determine which current connections are from another database via database link?
This presentation will answer these and other questions.

#IOUGeniusDBBeginner Certificate

Objective 1: Resolving Common SQL*Net issues
Attendees will learn steps to resolve common connectivity issue.

Objective 2: Attendees will learn how to setup sqlnet tracing.
More importantly, how to interpret the files.

Objective 3: Your job isn't done if you haven't rolled your own tools.
How to create your own DIY tools and trace processors. It does not have to be complex.

Audience: In-Depth