Oracle Database Report ORA-01033 error

Oracle Login ora-01033:oracle is initializing or shutting down the workaround

2015-03-16 01:20 | 160511 people reading | source

Oracle Login ora-01033:oracle is initializing or shutting down the workaround

Oracle has multiple instances

The corresponding DOS commands are executed:

1. Set up the correct ORACLE instance: Set Oracle_sid = instance_name

2. Start Sqlplus:sqlplus/nolog

3. Log in as a DBA (usually with several SYS or system) users sqlplus: Connect System/sys as Sysdba

ORACLE Login Error (ora-01033:oracle initialization or shutdown in progress

This is the example of creating table partitions, so create a table space when you create several table space physical files, then feel the creation of the wrong, want to delete them, but delete (because the database process started), so the database service to shut down, directly shift+del the file to delete.

The problem is: After I start the Oracle-related service again, I can't log in.

Ora-01033:oracle initialization or shutdown in progress appeared

Because I deleted the media file.

Steps to resolve:

Log on as a DBA (usually with several SYS or system) User Sqlplus

Please enter user name: System/sys as Sysdba

Then (unload data) Enter:

sql> shutdown Normal

will appear:

ORA-01109: Database is not open

The database has been uninstalled.

The ORACLE routine has been closed.

Then (load data) Enter:

Sql> Startup Mount

The ORACLE routine has been started.

The database is loaded.

After:

Sql>alter database open;

An error occurred on line 1th:

ORA-01157: Unable to identify/lock data file 6-see DBWR trace file

ORA-01110: Data file 6: ' D:/oracle/product/10.1.0/oradata/railway/2008_1.dat '

sql> ALTER DATABASE create datafile 6;

The database has changed.

Sql>alter database open;

An error occurred on line 1th:

ORA-01113: File 6 requires media recovery

ORA-01110: Data file 6: ' D:/oracle/product/10.1.0/oradata/railway/2008_1.dat '

Sql> ALTER DATABASE datafile 6 offline drop;

The database has changed.

Go on

Sql>alter database open;

If the above error occurs, continue with the related operation, the above 6 will correspond to create and drop.

If

sql> ALTER DATABASE open;

Came up:

The database has changed.

was successful.

You can then use PL/SQL and other client tools, log on to the Operation database.

As for media recovery: ora-01172 ora-01151, the workaround is as follows:

C:>sqlplus/nolog

Sql> connect Sys/[email protected] as SYSDBA

is connected

Sql> Startup Mount

ORA-01081: Unable to start an ORACLE---that is already running please shut down first

Sql> ALTER DATABASE open read only;

ALTER DATABASE open Read only

*

ERROR on line 1th:

ORA-16005: Database needs to be restored

sql> Recover Database

Complete media recovery.

sql> shutdown Immediate

ORA-01109: Database is not open

The database has been uninstalled.

The ORACLE routine has been closed.

Sql> Startup

The ORACLE routine has been started.

Total System Global area 730931140 bytes

Fixed Size 454596 bytes

Variable Size 411041792 bytes

Database buffers 318767104 bytes

Redo buffers 667648 bytes

The database is loaded.

The database is already open.

Today with the client connection to ORACLE, found that the ora-01033:oracle is initializing or shutting down the error, in fact, this error reported a few days, the first two restart a little better, today is how to get up, through the online search, very good solved,

First I use the Startup Mount command, can be normal, and then use the ALTER DATABASE open will error, such as

You can see the problem with the archive file, and then

You can see that the reorganization is not the current state but is archived, so use the clear command to rebuild the current group

Sql>alter Database Clear logfile Group 3;

If the log group has not yet been archived, you need to use the

Sql>alter Database Clear unarchived logfile Group 3;

Then ALTER DATABASE open databases can be connected.

I am doing this on my own machine, but if it is best to make a backup at once on the production machine.

Description

1), if the damage is not the current online log file, generally only need to clear to rebuild the log file, but if the database is in an archive state but the log has not been archived, you need to forcibly clear.

2), the proposed clear, in particular, forcibly clear the database after the full backup.

3), this method is suitable for archiving and non-archive databases.

Baidu Experience:

Http://jingyan.baidu.com/article/36d6ed1f6e3bb61bcf4883e1.html

This article is from the "0805" blog, please be sure to keep this source http://zrxwcc.blog.51cto.com/6160351/1926042

Oracle Database Report ORA-01033 error