Ora-01033:oracle initialization or shutdown in progress

Cold backup of your database. You are on the server side, using the SVRMGRL command
Svrmgrl> Connect internal;
Svrmgrl> SHUTDOWN IMMEDIATE; --or NORMAL
Svrmgrl> STARTUP MOUNT;
svrmgrl> ALTER DATABASE datafile '/ORACLE/ORADATA/ORCL/USERS01.DBF ' offline drop;
svrmgrl> ALTER DATABASE OPEN;

Delete this file in the database because this file corresponds to the table space that is dedicated to the general
User, deletion has no effect on the database.

D:/oracle/oradata/orcl/redo03. LOG is overwritten with incorrect files

Corrupted online log, just fix it.

C:/CD Oracle9/ora92/bin Anyway, the bin file goes in.

C:/......bin>sqlplus/nolog

Sql>connect sys/sting as Sysdba

sql> shutdown abort; ORACLE routines are closed

sql> startup Nomount; The ORACLE routine has started.

An online log block that prompts for an error after the Sql>startup database has finished loading

To perform an incomplete recovery:
sql> recover database until cancel as if to do a few more

Log on as SYSDBA in SYS
Sqlplus/nolog
Sql>connect sys/user Password as Sysdba
Sql>shutdown Normal
Sql>startup Mount
Sql>alter Database Open
Sql>shutdown Normal
Sql>startup

Results appear
Sql> ALTER DATABASE Open
2;

ALTER DATABASE Open

See which data file is having problems and try again and again

sql> ALTER DATABASE create DataFile XXX; XXX indicates the wrong data file number
sql> ALTER DATABASE datafile XXX offline drop; Repeat the above steps and keep the land connected until the error is not repeated

May be able to use the above:

Sql>alter Database Clear unarchivelog logfile group xxx, xxx for your log file group, for recovery

Sql>alter database open resetlogs; Log file for new Open database

Other people's answers

Method One

Recreate the dbf file with the same name and recover from the backup file
If this file is not needed,
Shutdown immediate
Startup Mount
ALTER DATABASE datafile ' C:/XXX.DBF ' drop offline (the syntax here is not very clear, check it yourself)
ALTER DATABASE Open

Method Two

[Q] lost a data file, but no backup, how to open the database
[A] If no backup can only be deleted this data file, will cause the corresponding data loss.
Sql>startup Mount
--archivelog mode command
Sql>alter database datafile ' file name ' offline;
--noarchivelog mode command
Sql>alter database datafile ' file name ' offline drop;

Sqll>alter database open;
Note: This data file cannot be a system data file

Sql>select group#,sequence#,archived,status from V$log; View some properties of the machine log file

The steps that I'm doing are as follows

Sql> ALTER DATABASE Clear unarchived logfile Group 1
2/
ALTER DATABASE Clear unarchived logfile Group 1
*
ERROR is on line 1th:
ORA-01624: Thread 1 requires log 1 for emergency recovery
ORA-00312: Online log 1 thread 1: ' D:/oracle/oradata/oemrep3/redo01. LOG '

sql> Recover database until cancel
ORA-00283: Recovery session canceled due to error
ORA-01124: Unable to recover data file 1-file in use or in recovery
ORA-01110: Data file 1: ' D:/oracle/oradata/oemrep3/system01. DBF '

Let the data file go offline, you can open the database
C:/>svrmgrl
Svrmgrl>connect Internal
Svrmgrl>shutdown
Svrmgrl>startup Mount
--archivelog mode command, file name to uppercase
Svrmgrl>alter database DataFile ' c:/test. ORA ' offline;
--noarchivelog mode command
Svrmgrl>alter database DataFile ' c:/test. ORA ' offline drop;
Svrmgrl>alter database open;
--Querying data file union, offline status
Sql> select File#,name,status from V$datafile;
sql> Drop tablespace test;
Table space has been discarded.
Missing online log files
To handle in two different situations
1. The missing log files are inactive;
2, the missing is the currently active log file.
If this is the first case, the failed log filegroup has more than one member, you can shutdown the database, and then use the operating system command to overwrite the corrupted log member file with the corrupt member file (each of the log files in the same log member group is mirror-like). If its physical location is not available, copy it to a new drive, change the file location using ALTER DATABASE rename file ' xxxx ' to ' xxxx ', and then start the database if a cold backup is done normally. If there is only one log member in the corrupted log group, mount the database first, convert it to Noarchivelog mode, execute ALTER DATABASE add logfile member ' xxx ' to group ' X ' adds a member to the related group, then executes ALTER DATABASE drop logfile ' Bad_ File ' will delete the corrupted log file, because the database structure changes need to back up the control file, then change the database back to Archivelog mode, do a cold backup.
If the current active log file is missing, the database is not mirrored and all members of the current log group become unavailable. First, the database is shutdown abort, all the data files are recovered from the most recent full backup, and the database is booted to the Mount State. If the original log file physical location is not available, change the location of the file using ALTER DATABASE rename file ' xxx ' to ' xxx '. Then, use the Recover DB until cancel command to recover the database until you are prompted to use the last archive log, and then enter Cancel. Then open the database with ALTER DATABASE open resetlogs, and if there is no problem, make a cold backup immediately. Attention. All information contained in the corrupted redo log will be lost, meaning that data submitted before the database crash is likely to be lost. This can be costly for some demanding applications, so try to have multiple log members per log group and place them on different drives to prevent media failure.