Shulou(Shulou.com)06/01 Report--

Oracle login ORA-01033: the solution that ORACLE is initializing or shutting down

2015-03-16 01:20 | 160511 people read | Source

Oracle login ORA-01033: the solution that ORACLE is initializing or shutting down

There are multiple instances of Oracle

Execute accordingly under the DOS command:

1. Set the correct ORACLE instance: set ORACLE_SID = INSTANCE_NAME

two。 Start SQLPLUS:sqlplus / nolog

3. Log in as the DBA (usually several sys or system) user sqlplus: connect system/sys as sysdba

Oracle login error (ORA-01033:ORACLE initialization or shutdown in progress

The above mentioned example of creating table partitions, so when creating tablespaces, I created several tablespace physical files, and then I felt that there was something wrong with the creation, so I wanted to delete them, but I couldn't delete them (because the database process was started), so I turned off the database service and deleted the files directly by Shift+Del.

Here's the problem: after I started the oracle service again, I couldn't log in.

ORA-01033:ORACLE initialization or shutdown in progress appeared.

The reason is that I deleted the media file.

Resolution steps:

Log in as the DBA (usually several sys or system) user sqlplus

Please enter a user name: system/sys as sysdba

Then (unload data) enter:

SQL > shutdown normal

Will appear:

ORA-01109: the 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 that:

SQL > alter database open

An error occurred on line 1:

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

ORA-01110: data file 6: 'DJV _ r _ r

SQL > alter database create datafile 6

The database has changed.

SQL > alter database open

An error occurred on line 1:

ORA-01113: file 6 requires media recovery

ORA-01110: data file 6: 'DJV _ r _ r

SQL > alter database datafile 6 offline drop

The database has changed.

Go ahead

SQL > alter database open

If the above error occurs, continue with the relevant operation, and the above 6 corresponds to create and drop.

If

SQL > alter database open

Here it comes:

The database has changed.

It worked.

At this time, you can use PL/SQL and other client tools to log in and operate the database.

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

C: > sqlplus / nolog

SQL > connect sys/sys@oracle as SYSDBA

Connected

SQL > startup mount

ORA-01081: unable to start ORACLE that is already running-Please close first

SQL > alter database open read only

Alter database open read only

*

ERROR is on line 1:

ORA-16005: database needs to be restored

SQL > recover database

Complete the media recovery.

SQL > shutdown immediate

ORA-01109: the 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, when I used the client to connect to oracle, I found that ORA-01033: ORACLE is initializing or shutting down an error. In fact, this error has been reported for several days. It would be better to restart it the first two times. I couldn't get up today. I found it well by looking it up on the Internet.

First of all, I use the startup mount command, which works, and then I use alter database open to report an error, as shown in the following figure.

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

You can see that the group is not in its current state but has been archived, so use the clear command to rebuild the current group

SQL > alter database clear logfile group 3

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

SQL > alter database clear unarchived logfile group 3

Then the alter database open database can be connected.

I did it casually on my own machine, but if I'm on the production machine, I'd better make a backup right away.

Description:

1) if a non-current online log file is damaged, you only need clear to rebuild the log file, but if the database is archived but the log has not been archived, you need to force clear.

2) it is recommended that clear, especially after forced clear, make a full backup of the database.

3) this method is suitable for archived and non-archived databases.

Baidu experience:

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

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.