Another option is to identify that Oracle process (assuming that there is
one, you can look for a child process of your local sqlplus command with
ps) and run pstack on it to see where it's stuck. The process name should
something like this: oracleSID (DESCRIPTION=(LOCAL=YES)(ADDRESS=(
Pstack may be to microscopic though, hanganalyze can provide more context
(like if you're waiting for a latch or lock, who's holding it at the same
On Tue, Oct 15, 2019 at 2:28 PM Tanel Poder <tanel@xxxxxxxxxxxxxx> wrote:
While the login hang is ongoing, connect in another terminal window with a
sqlplus preliminary connection & run hanganalyze to see what's preventing
you from logging on:
1) sqlplus -prelim "/as sysdba"
2) oradebug hanganalyze 3
There are some gotchas to be aware of if you don't see proper hanganalyze
output in the tracefile, I've written about these here:
On Tue, Oct 15, 2019 at 11:40 AM Howard Latham <howard.latham@xxxxxxxxx>
I'm doing an upgrade from 184.108.40.206 to 18
The instructions say shut down the target db and startup upgrade from the
But I can't connect
Connect from sqlplus connect / as sysdba and connect sys/xxxxxx as
sysdba both hang
Anyone got any ideas?
Its RH Linux BTW.
Howard A. Latham