ORA-01012:
not logged on
ORA-01012: not logged on
This may occur generally due to heavy load or out of
available connection in the database. If there is maximum number of sessions
connected to the database, which is defined by ‘processes‘ parameter and
database does not allow sysdba as well as other users to connect to the
database. Sometimes it may also occur due to improper shutdown the database. In
that case it shows connected but it does not allow to happening any query to
the database instead it fails with ORA-01012: not logged on
Sometimes connecting with sysdba shows database in idle
instance but whenever you issue startup it fails with ORA-01081:
cannot start already-running ORACLE - shut it down first.
Comments
Post a Comment