You are here means you are facing “ora-01033 oracle initialization or shutdown in progress” error while trying to login into the Oracle database. A few days ago I faced the same issue and here are the steps that I have followed to troubleshoot which helped me login into the database successfully.
This article will help you understand the error message, possible causes, and their solutions. So without wasting time, let’s start digging into the error message.
What does “ora-01033 oracle initialization or shutdown in progress” error mean?
The error message is very clear and explains that the Oracle initialization or shutdown process is in progress, hence we cannot perform any other action on the database till initialization/shutdown is in progress. After completion of either initialization or shutdown, you will be able to perform the required action on the database.
There are following five reasons that may result in the error message and the steps you need to follow in order to fix the error.
1. The database is in the middle of starting or shutdown process
Reason:
If you have just started or shut down the database and executed a new command then you may end up receiving “ora-01033 oracle initialization or shutdown in progress” error message as already some process is going on and you are trying to execute a new command.
Solution:
Wait for the process to complete. Sometimes starting or shutdown down the database may take some time due to system performance or some processes are used in another application. If you still facing the same error after some time, then check out the below point.
2. An issue with the database services
Reason:
There may be some issues with the database services. Either database services are stopped or getting issues while starting. Many users have observed that they faced an issue while starting the database service due to updated security settings. Due to security settings, users may face port or access-related issues.
Solution:
Restart the database services. Check if database services are up and running. There is a possibility of the database service got hung and in that case, restarting the Oracle services will solve the issue. Here are the steps to do so.
- Got to search bar, type Services and select Services app.
- Restart Oracle Service and then Oracle Listener Service as shown below.
3. Forced shutdown or incomplete shutdown of database
Reason:
When you execute a command to shut down the database, database software internally executes some stepwise procedures to shut down the database. And it may take a few minutes. If you forcefully close the database service or shut down the system due to a power cut issue in between the database shutdown process then it may result in a complete shutdown of the database. Which can cause the above error message while login into the database again.
Solution:
Shut down and start the database. If there is any issue during the shutdown and startup process then try shutting down the database forcefully and start again using the below steps.
- Open command prompt and log in as sysdba using the following command
sqlplus / as sysdba - Enter the following command to forcefully shutdown database
shutdown abort; - Execute the below command to startup the database again
startup;
Now try to login into the database and you should be able to log in without any error message. If you are still getting the error then try the next step.
4. The database is not mounted or opened
Reason:
If the database is not mounted properly, while starting the database then it can result in the error message “ora-01033 oracle initialization or shutdown in progress“. If the database is mounted then it’s available for the database administrators only. Normal users can’t access a database that is mounted but not opened.
Solution:
Try to mount and open the database using the following steps and it should fix the error.
If the database is mounted but not open then you may end up getting the error as well. To check whether the database is MOUNTED or OPEN or neither of those, you can execute points #4 and #6 to understand the current status.
Note: If STATUS is MOUNTED then it means the database is mounted but not opened.
- Open command prompt and log in to database as sysdba.
sqlplus / as sysdba - Forcefully shutdown database.
shutdown abort; - Mount the database.
startup mount; - Check whether the database is mounted or not.
select status, database_status from v$instance; - Open the database.
alter database open; - Check whether the database is open or not.
select status, database_status from v$instance;
5. Corrupted database files
Some intentional or unintentional invalid activity may damage some database files. If DBF, CTL, or ORA files are corrupted then it can cause the error “ora-01033 oracle initialization or shutdown in progress”.
If all the above steps do not work and you are still getting the same error message, then uninstall the database software and install it again. Before uninstalling the DB, make sure you take a backup of the data.
Create a new database instance and try to import the previous database files if you have taken the backup of the running instance.
Note: It’s highly recommended to take a backup of the database from time to time. If you come across such issues where it cannot be resolved, then restoring the DB to a previous stage is easy or else you will end up losing all the data.
Final thoughts:
We hope you are able to get rid of the “ora-01033 oracle initialization or shutdown in progress” error using the above steps. Let us know in the comments which steps helped you fix the error. If you are still having challenges, do mention them in the comment section and we would be happy to help you.
Read also:
How to use Column Mode Editing in Notepad++
Yesterday I installed Oracle 12c Enterprise edition on my laptop. When I tried to connect to DB via SQLPLUS i got the below error
C:UsersUSER>sqlplus
SQL*Plus: Release 12.1.0.2.0 Production on Sun Feb 28 14:12:46 2016
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Enter user-name: userdb
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
I tried all the tricks mentioned on internet but couldn’t get rid of this error.
I also tried below
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 1543503872 bytes
Fixed Size 3045984 bytes
Variable Size 989857184 bytes
Database Buffers 536870912 bytes
Redo Buffers 13729792 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10:
'C:ORACLEDB12CAPPUSERNAMEORADATAORCLPDBORCLEXAMPLE01.DBF'
also tried below but still getting error’s
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 1543503872 bytes
Fixed Size 3045984 bytes
Variable Size 989857184 bytes
Database Buffers 536870912 bytes
Redo Buffers 13729792 bytes
SQL> alter database mount;
Database altered.
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10:
'C:ORACLEDB12CAPPUSERNAMEORADATAORCLPDBORCLEXAMPLE01.DBF'
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 10:
'C:ORACLEDB12CAPPUSERNAMEORADATAORCLPDBORCLEXAMPLE01.DBF'
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10:
'C:ORACLEDB12CAPPUSERNAMEORADATAORCLPDBORCLEXAMPLE01.DBF'
Can someone help here? thanks!
Summary: in this tutorial, you will learn how to fix the ORACLE initialization or shutdown in progress error when you connect to the Oracle Database.
Sometimes, you may encounter the following error when you connect to an Oracle pluggable database in Oracle Database 12c:
Code language: SQL (Structured Query Language) (sql)
An error was encountered performing the requested operation: ORA-01033: ORACLE initialization or shutdown in progress 01033. 00000 - "ORACLE initialization or shutdown in progress" *Cause: An attempt was made to log on while Oracle is being started up or shutdown. *Action: Wait a few minutes. Then retry the operation. Vendor code 1033
To fix this issue, you use the follwing steps:
First, launch the SQL*Plus program and login to the database instance as a SYSDBA user:
Code language: SQL (Structured Query Language) (sql)
Enter user-name: ot@pdborcl as sysdba Enter password: <password>
This statement connected to the PDBORCL database using the OT user.
Second, issue the following statement to check the status of the current instance:
Code language: SQL (Structured Query Language) (sql)
SQL> select status, database_status from v$instance; STATUS DATABASE_STATUS ------------ ----------------- MOUNTED ACTIVE
The output showed that the instance status is mounted.
Third, change the state of the Oracle Database instance to OPEN:
Code language: SQL (Structured Query Language) (sql)
SQL> alter database open; Database altered.
For more information on the Oracle Database stages, check it out the Startup Oracle Database instance tutorial.
Finally, double check the database status by using the following statement:
select status, database_status from v$instance; STATUS DATABASE_STATUS ------------ ----------------- OPEN ACTIVECode language: SQL (Structured Query Language) (sql)
The instance status is open and available to all users for normal operations.
Now, you should be able to connect to the OT pluggable database without any issue.
Was this tutorial helpful?
Are you getting the ORA-1033: ORACLE initialization or shutdown in progress error each time when you try to get connect with your database?
If yes, then read out this informative post which contains detailed information about ORACLE initialization or shutdown in progress error. Moreover, the post also covers some best fixes on how to resolve ORA-1033 error.
The Oracle error 1033 is in the form of Hexadecimal format. It is a very common error code format used by windows and other windows compatible software and driver vendors. This code is generally used by the vendors in order to identify the error caused. This error has a numeric value and a technical description. In most of the cases, the error may have more parameters in Oracle Error 1033 format. These hexadecimal codes are the addresses of the memory locations where the instructions were loaded at the error time.
What Are The Different Oracle Database Shutdown And Startup Modes?
Well, there are various stages that come under the process of database startup and shutdown. Let’s know about them more briefly.
Oracle Database Startup
Before the database is been opened for use, your database has to go through the following stages.
- Nomount State:
In this state database file, the control file and online redo log files are been closed. So these are not accessible. During this stage, Oracle instance and some v$ views (dynamic performance views) seem available.
- Mount state:
It’s is the next stage through which the oracle database has to pass before starting up the database.
In this stage, the control file will get open and the presence of all online redo log files and database files is verified.
- Open:
In this phase, online redo log files and data files are being opened. Now your database is ready to get used.
If any of the data file and online redo log file has got corrupted or goes missing then Oracle won’t allow you to open your database.
Oracle Database Shutdown
Oracle shutdown has three main modes: normal, immediate, and abort.
- Shutdown normal:
It’s a default mode of shut down the Oracle database. In this state, the Oracle server needs to until all the users disconnected from the database.
- Shutdown Transactional:
In this stage, the database will wait until the entire transaction process gets over, after then only it shut down the database. In this phase, the oracle database denies setting any new connection.
- Shutdown immediate:
During this stage, all the sessions are being disconnected. So the database will roll back all the on-going transactions and after the shutdown itself.
- Shutdown aborts:
In this phase, there is no option of rollback any transaction. It simply shutdowns the database directly. So if you take any backup after the database enters into the shutdown abort mode then that backup is not consistent anymore.
What Causes Ora-1033: ORACLE Initialization Or Shutdown In Progress?
The following are the causes of Ora-1033: ORACLE initialization or shutdown in progress error.
- Ora-1033 error also occurs when someone tries to attempt to log on while Oracle is either shutting down or starting up.
- The “Oracle 1033 Error may take place due to Windows system file damage. The corrupted system files entries can be a real threat to your computer.
- Oracle database is not mounted correctly.
- Oracle Database files like CTL, DBF, or ORA is either corrupted or moved somewhere else.
- When there some problem has occurred in the database services.
How To Fix Ora-1033 error: ORACLE Initialization Or Shutdown In Progress?
Try the below mentioned fixes to resolve Ora-1033 error: ORACLE Initialization or Shutdown in Progress.
Fix 1# Restart Your System Or The Database Service
If your Oracle database is still continuing with the process of shutting down or startup. Wait for few minutes and let the Oracle application to finish this process. If after waiting for a long time still the process won’t get over then restart your oracle application again or restart your complete system.
Fix 2# Release RAM Memory
Behind getting these ORA-1033 error chances are high that your PC’s operating system has kept some RAM regions leftover which Oracle count as an instance.
In that case, you need to remove all the oracle processes which are mainly associated with ORACLE_SID.
Look into all the segments of RAM memory and after that release the unwanted space from RAM memory.
Fix 3# Mount The Database Properly
The problem of ORACLE initialization or shutdown in progress also arises when the database is not correctly mounted. You need to mount and restart your Oracle database. You can do this easily with the help of the “alter database open” and “alter the database mount” query.
Here is the code to be applied for mounting the database properly:
SQL> connect / as sysdba
ConnectÚ.
SQL> shutdown abort
Instance ORACLE arrÛtÚe.
SQL> startup nomount
Instance ORACLE lancÚe.
SQL> alter database mount;
SQL> alter database open;
After performing this don’t forget to restart the database.
Fix 4# Problem With The Database CTL , DBF Or ORA Files )
You need to recover the Oracle Database CTL , DBF Or ORA Files if by mistakenly you have moved or changed these files.
Additionally, if you are getting the error ORA-19809 along with the ORA-01033 then it means the limit for the recovery files has exceeded now.
Fix 5# Delete Service And Recreate The Database
If still you are getting the same Ora 1033: ORACLE initialization or shutdown in progress then deleting the service and database is the only option. After that just re-create the database.
Note: Before performing this operation, just make a proper backup of your complete data.
- Go to the service.msc. After that stop the respective service.
- Using the command prompt just delete the service.in the cmd window type: sc delete <service name >
- Now recreate your Oracle database.
Fix 6# Try The Automated Option
If the above-given fixes won’t work to resolve Oracle Error 1033 try this last option i.e Oracle File Repair Tool.
As it is seen that oracle stuck into this initialization or shutdown in progress like issues also when some oracle database file got corrupted. So by resolving the corruption issue you can easily get over this Oracle error ORA-1033.
This software successfully recovers the entire database whether it is lost in any situation. With this tool, you can also repair damaged Oracle database files and also helps to restore tables, user names, and much more stuff.
Steps To Use Oracle File repair tool
Step 1: Search the Initial screen of Oracle File repair tool with a pop-up window showing options to select or search corrupt Oracle databases on your computer.
Step 2: Click Scan File to initiate the scan process after selecting the oracle database. The recoverable database objects get listed in left-side pane.
Step 3: Click an object to see its preview.
Step 4: : Click Start Repair in the icon bar to start the repair process. A pop-up window is displayed which show the steps needed to perform further. Click next and continue.
Step 5: Give the user name, password and path of the blank database where you want to save the repaired database objects.
Step 6: Repairing and restoring various database objects after establishing a connection with blank oracle database.
Final Verdict:
Now that you know what’s causing this ORA-01033 error to get happened. So make sure that the Oracle database is not undergoing any process of shutting down or starting up. Also, check whether the database is mounted correctly or there is some problem with database files or services.
One very simple solution to fix many problems of the oracle database is to shut down and restarting the application again.
Even after trying all the fixes outlined above if the problem persists and still, you are getting ORA-1033 then contact the database administrator for further assistance. Or you can consult with the licensed Oracle professionals.
Jacob Martin is a technology enthusiast having experience of more than 4 years with great interest in database administration. He is expertise in related subjects like SQL database, Access, Oracle & others. Jacob has Master of Science (M.S) degree from the University of Dallas. He loves to write and provide solutions to people on database repair. Apart from this, he also loves to visit different countries in free time.
I had installed Oracle 11g on windows 07,everything was working fine.But today it is giving me an error saaying ORA-01033: ORACLE initialization or shutdown in progress . I followed the steps mentioned in the different communities but unable to solve the error. After connecting as sqlplus sys/sys as sysdba. and executing below statement,i got following error. How to solve this error?
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 9: 'C:APPMKHATALORADATAORCLVELODBDATA.DBF'
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'C:APPMKHATALORADATAORCLVELODBDATA.DBF'
Thanks in advance!!
asked Jun 27, 2013 at 7:26
2
First, check your ALERT.LOG file typically located in D:apporaclediagrdbmsDBNAMESIDtrace.
The latest entries in your ALERT.LOG should give you an indication on what is going on. Is the database starting? Shutting down?
Should the database be stuck in the shutdown process, you can try to kill the oracle.exe process and then restart the database via Windows Service.
Often, when the database seems to hang on startup, it is actually applying REDO to get a consistent state, so pay close attention on what the ALERT.LOG tells you.
answered Jun 27, 2013 at 7:45
SimonSimon
4,1512 gold badges24 silver badges34 bronze badges
1
There’s more info needed to be able to solve similar issues. Questions like these are interesting to get answered:
- To what level can you start the database ? None, nomount, mount or
open (exclude the last one in this case) - What does the ALERT.LOG file show ? This from the moment the first
issue is suspected to be around - An obvious question is just : what happened ? What action were you
doing when you saw the first error message ? - Can you shutdown the database ? If yes, which methods : normal,
immediate or abort only ? Know that stopping the database with ABORT
option may make problems bigger as they are already. - Did you try rebooting the server ? This is particularly an issue on
Windows, which is your case. - Depending on how you stopped the database, do you have a cold backup
? - Depending on RMAN still working : can you take a backup ? The RECOVERY you were trying is not bad, but it could be interesting to know what is happening on OS level with that file; Is it there ? If yes, is it locked or not ? Does the OS think it’s a valid file ?
answered Dec 7, 2014 at 17:55
tvCatvCa
7966 silver badges13 bronze badges
