Ora 01033 ошибка как исправить

Introduction

Before starting the topic, first I want to explain why this started up or shutdown error occurs. Sometimes while making the clone of production database into a test server this type of error may be encountered.So there are the following major reasons why ORA-01033 error occurs:

To fix this error follow the bellow steps,

Step 1

Open command prompt and give the command,

When you hit the ENTER key, it shows it’s connected to Oracle 12c.

Step 2

To check the connection name, use the following command,

When you hit the ENTER key, It shows connection CDB$ROOT (container Database Selected from root).

Step 3

Check the schema name and connection id using the below command–

When you hit the ENTER key, it shows the name of schema object with respect to their id’s.

Note that, in PDB$SEED the ‘SEED’ is template, used to create a new pluggable database within the container database (CDB).

Step 4

Now, select name of pluggable database from active services whose connection id=3, by using the following command –

When you hit the ENTER key, It shows the name ‘pdborcl’.

Step 5

Now, close the command prompt and follow the below procedure.

After opening the ‘ tnsnames.ora’ file in text editor, you see the following code. 

From the above code copy the last portion of the code i.e.:

And paste it at the end of the whole code. Then, make the change into it as follows. After making the following changes save it. 

Finally ensure that your entire code will looks as follows. And close the ‘tnsnames.ora’ file and also close the ‘app’ folder. 

Step 6

Open the command prompt as ‘administrator’ and give the following command.

When you hit the ENTER key, it shows a description about connection.

Step 7

Now, give the command,

When you hit the ENTER key, it shows a description about connection.

Step 8

To alter the session from container database to pluggable database give the command-

When you hit the ENTER key, it shows session altered.

Step 9

To check if the session is altered from CDB$ROOT to PDBORCL use the following command-

When you hit the ENTER key, It shows connection name as ‘PDBORCL’.

Step 10

Now check the connection mode, give the following command-

When you hit the ENTER key, It shows connection mode is ‘OPEN_MODE’ but pluggable database is ‘MOUNTED’

Step 11

Now, alter the pluggable database to change the open mode from ‘MOUNTED’ to ‘READ WRITE’, by using the command-

Step 12

To ensure the ‘OPEN_MODE’ of pluggable database is changed from ‘MOUNTED’ to ‘READ WRITE’, once again use the command-

When you hit the Enter key, ‘OPEN_MODE’ is ‘READ WRITE’.

Step 13

Now the pluggable database is altered and the open mode is also changed as ‘READ WRITE’. So we can unlock the HR Schema. To unlock the HR schema use the following command,

Step 14

To connect with the pluggable database using HR schema use the following command-

Step 15

In this way, we successfully fix the ORA-01033 error, to unlock th HR schema object. Now we can connect with pluggable database using HR user. Open the SQL developer tool and enter username as ‘HR’ and password is also ‘HR’ and click on ‘OK’ button.

Now you see that, the ORA-01033 error is successfully fixed and we successfully connected with pluggable database using HR schema object/HR user.

Summary

In this article we learned about how to fix the start up or shutdown error (ORA — 01033 error).

Introduction

Before starting the topic, first I want to explain why this started up or shutdown error occurs. Sometimes while making the clone of production database into a test server this type of error may be encountered.So there are the following major reasons why ORA-01033 error occurs:

To fix this error follow the bellow steps,

Step 1

Open command prompt and give the command,

When you hit the ENTER key, it shows it’s connected to Oracle 12c.

Step 2

To check the connection name, use the following command,

When you hit the ENTER key, It shows connection CDB$ROOT (container Database Selected from root).

Step 3

Check the schema name and connection id using the below command–

When you hit the ENTER key, it shows the name of schema object with respect to their id’s.

Note that, in PDB$SEED the ‘SEED’ is template, used to create a new pluggable database within the container database (CDB).

Step 4

Now, select name of pluggable database from active services whose connection id=3, by using the following command –

When you hit the ENTER key, It shows the name ‘pdborcl’.

Step 5

Now, close the command prompt and follow the below procedure.

After opening the ‘ tnsnames.ora’ file in text editor, you see the following code. 

From the above code copy the last portion of the code i.e.:

And paste it at the end of the whole code. Then, make the change into it as follows. After making the following changes save it. 

Finally ensure that your entire code will looks as follows. And close the ‘tnsnames.ora’ file and also close the ‘app’ folder. 

Step 6

Open the command prompt as ‘administrator’ and give the following command.

When you hit the ENTER key, it shows a description about connection.

Step 7

Now, give the command,

When you hit the ENTER key, it shows a description about connection.

Step 8

To alter the session from container database to pluggable database give the command-

When you hit the ENTER key, it shows session altered.

Step 9

To check if the session is altered from CDB$ROOT to PDBORCL use the following command-

When you hit the ENTER key, It shows connection name as ‘PDBORCL’.

Step 10

Now check the connection mode, give the following command-

When you hit the ENTER key, It shows connection mode is ‘OPEN_MODE’ but pluggable database is ‘MOUNTED’

Step 11

Now, alter the pluggable database to change the open mode from ‘MOUNTED’ to ‘READ WRITE’, by using the command-

Step 12

To ensure the ‘OPEN_MODE’ of pluggable database is changed from ‘MOUNTED’ to ‘READ WRITE’, once again use the command-

When you hit the Enter key, ‘OPEN_MODE’ is ‘READ WRITE’.

Step 13

Now the pluggable database is altered and the open mode is also changed as ‘READ WRITE’. So we can unlock the HR Schema. To unlock the HR schema use the following command,

Step 14

To connect with the pluggable database using HR schema use the following command-

Step 15

In this way, we successfully fix the ORA-01033 error, to unlock th HR schema object. Now we can connect with pluggable database using HR user. Open the SQL developer tool and enter username as ‘HR’ and password is also ‘HR’ and click on ‘OK’ button.

Now you see that, the ORA-01033 error is successfully fixed and we successfully connected with pluggable database using HR schema object/HR user.

Summary

In this article we learned about how to fix the start up or shutdown error (ORA — 01033 error).

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!

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.