Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORA-01089: immediate shutdown in progress - no operations are permitted

1001500Apr 8 2013 — edited Apr 8 2013
hii guys I am beginner in sql. Please help me out from this error:

ORA-01089: immediate shutdown in progress - no operations are permitted

I am not able to connect the server.
I have reinstalled the Database 11g xe software 5 times but still geting this same error.
ANd also use SHUTDOWN ABORT cmd but it is showing no privilege.

Comments

dbthought
Have you used / as sysdba ? for abort

Login to system by root or Administrator and check

Thanks
Fran
ORA-01089: immediate shutdown in progress - no operations are permitted --> happends when you connect to database with a current user, not as sysdba.

1.- Wait
2.- connect "/ as sysdba" and execute "shutdown abort", when database is down, "startup"
option 2 is not recommeded, unless database/server have abnormal behavior. shutdown abort is the last option.
864103
just wait , due to if you do shutdown abort this kind of shutdown is called dirty shutdown cuz there is no checkpoint and at the end when database
is startup the oracle internally should be perform instance recovery , and if you need to do that just connected as sysdba and shutdown abort
no privs messages that mean your user don't have this privs to do a shutdown .
Fran
just wait , due to if you do shutdown abort this kind of shutdown is called dirty shutdown cuz there is no checkpoint and at the end when database
correct
is startup the oracle internally should be perform instance recovery , and if you need to do that just connected as sysdba and shutdown abort 
smon do the recovery, correct
no privs messages that mean your user don't have this privs to do a shutdown .
incorrect, you must have privileges to shutdown database. When you issue a shutdown, only the SYS/SYSTEM user will be able to connect (or sysdba privilege). That's the point i tried to explain, maybe i was understood or my explain was really bad (sorry if it was).
SQL> show user
USER es "SYS"
SQL> conn fran/fran
Conectado.
SQL> shutdown immediate;
ORA-01031: privilegios insuficientes
864103
thanks but please check the below
SQL> conn abs/abs
Connected.
SQL> shutdown immediate;
ORA-01031: insufficient privileges


SQL> grant sysdba to abs;

Grant succeeded.

SQL>
SQL>
SQL>
SQL>
SQL> conn abs/abs as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 1603411968 bytes
Fixed Size                  2228784 bytes
Variable Size            1124077008 bytes
Database Buffers          469762048 bytes
Redo Buffers                7344128 bytes
Database mounted.
Database opened.
SQL>
this is what i mean .
1001500
I have tried this but it is showing another error:
ORA-28056: Writing audit records to windows Event log failed
ORA-28056: Writing audit records to windows Event log failed
1001500
I have tried to login as sysdba but it is showing another error:

ORA-28056: Writing audit records to windows Event log failed
ORA-28056: Writing audit records to windows Event log failed
1001500
I have tried to login as sysdba but it is showing another error:

ORA-28056: Writing audit records to windows Event log failed
ORA-28056: Writing audit records to windows Event log failed
1001500
I have tried to login as sysdba but it is showing another error:

ORA-28056: Writing audit records to windows Event log failed
ORA-28056: Writing audit records to windows Event log failed
1001500
I have tried to login as sysdba but it is showing another error:

ORA-28056: Writing audit records to windows Event log failed
ORA-28056: Writing audit records to windows Event log failed
EmaxG
Control Panel --> Administrative Tools --> Event Viewer --> Clear All Events

Increase the log size.
1 - 11
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 6 2013
Added on Apr 8 2013
11 comments
48,984 views