Also check audit dump destination --- sys connections always create an aud
file - so make sure the audit dump dest is valid and not full and
writable by oracle.
Chris
On Tue, Oct 15, 2019 at 1:35 PM Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:
The most common cause of this is the recovery area is full. Look at your
alert log and see what it says.
On Tue, Oct 15, 2019 at 1:30 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:
https://blog.tanelpoder.com/2012/05/08/oradebug-hanganalyze-with-a-prelim-connection-and-error-can-not-perform-hang-analysis-dump-without-a-process-state-object-and-a-session-state-object/
--
Tanel Poder
https://blog.tanelpoder.com/seminar
On Tue, Oct 15, 2019 at 11:40 AM Howard Latham <howard.latham@xxxxxxxxx>
wrote:
I'm doing an upgrade from 11.2.0.4 to 18
The instructions say shut down the target db and startup upgrade from
the 18 home
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.
thanks
Best Wishes
Howard A. Latham
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
