Latest Oracle database hints and tips from online tech support. How to fix ORA-01031: insufficient privileges and Oracle shutdown abort. Find free Oracle computer help from our best computer technician.
The oracle database has bug insufficient privileges with shutdown commands. Let play through the most common way it appears and then online tech support computer technician will explain what it is occurring and how to fix it.
You have just executed a shutdown normal to your database and it just hangs. The oracle alert tells that the shutdown progress waits after an open user session. You have just killed all connections, but the shutdown is still hanging, so you’ll log on as SYSDBA:
# sqlplus / as sysdba
And executing oracle shutdown immediate:
SQL> shutdown immediate
The respond warns you about the shutdown that is in progress. Next you will try to do shutdown abort and the result is:
SQL> shutdown abort
This is quite strange situation? Sysdba does not have enough permission. The Online Tech Support says: when you executed “shutdown immediate” database oracle just levelled your permissions since the database will be shutdown and you couldn’t do anything “funny” or trying to cancel the half way shut downed process.
Your situation is different because the database shutdown is still hanging and to execute shutdown abort, you just log off and on again. With the fresh logging your permissions will be back and you can execute shutdown abort without problems. So do the following:
SQL> exit
Log on as SYSDBA again:
# sqlplus / as sysdba
And execute the shutdown command:
SQL> shutdown abort;
Of course, if you want to do start up then the follow and don’t forget to exit in the end:
SQL> startup;
SQL> exit
See Also:
Oracle Select Home