We have a
Windows Server 2008 R2 Enterprise x64
Oracle 10.2.0.3
Adempiere – ERP
- We had a power breakdown at 03.00 AM.
- At 07.30 AM we started the server
- At 08.00 our colleagues observed that the ERP is not functioning
- We started Adempiere
- ERP was not able to connect to Oracle DB
- We entered EM Console and we checked the DB status
- The listener was functional – up and running
- DB was shotdown in progress
- We tried to abort shot down via SQL Plus using command :
shutdown abort - Nothing happen
- We tried shutdown – no result
- We tried shutdown immediate – no result
- Then we made Windows Shutdown from start menu
- After restart of the server we checked in Windows Services.MSC the Oracle running services
- Oracle JoobscheduleORCL was disabled, the rest were running. We set this one on automatic
- The listener was functional – up and running
- DB was shotdown in progress
- We tried to abort shot down via SQL Plus using command :
shutdown abort - Nothing happen
- We tried shutdown – no result
- We tried shutdown immediate – no result
- We tried to restart the Oracle Services with no result
- We searched on the forum.oracle.com and we found out that the problem could be that the undotablespace is corrupted.
- We tried to fix the table
- We used the following command line :
alter database datafile 'xxxxx\undotbs01.dbf' offline drop;
http://www.dbas-oracle.com/2011/06/recovery-from-undo-tablespace-block.html
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:5669213349582
-
The current situation is :
SQL> startup ORA-01081: cannot start already-running ORACLE - shut it down first SQL> shutdown immediate ORA-24324: service handle not initialized ORA-24323: value not allowed ORA-01092: ORACLE instance terminated. Disconnection forced SQL> startup ORA-01031: insufficient privileges
Best Answer
Be sure the ORACLE_HOME and ORACLE_SID environment variables are correctly set. Then run
sqlplus / AS SYSDBA
as a user who is a member of theoradba
group on the computer.Get the machine down forcibly:
Start it up, but try not to let stuff run wild:
Shut it down more gracefully. Don't stop until recovery is complete.
Start it up.