Skip to main content

ORA-01033: ORACLE initialization or shutdown in progress

ORA-01033: ORACLE initialization or shutdown in progress



Cause: You are trying to access oracle database while  database is either starting up or shuting down (ORA-01033: ORACLE initialization or shutdown in progress).

Action: For ORA-01033: ORACLE initialization or shutdown in progress you need to wait for some time. Then retry the operation again (connect after some time) to check if ORA-01033: ORACLE initialization or shutdown in progress is there or not.


What is ORA-01033: ORACLE initialization or shutdown in progress?

This is very common error and not occurs much. But you must have some idea if you face ORA-01033: ORACLE initialization or shutdown in progress occurs. As we know We can only set database to  Shutdown or startup using SYSDBA privileges. So you must have SYSDBA privileges to troubleshoot. I suggest  to  wait for 5mins because may be your DBA has shutdown the Database and it's in progress.Or if you are a DBA then check the status of database  do start if it is down. My case below:-

[server@****** ~]$ sqlplus /nolog

SQL*Plus: Release 12.1.0.1.0 Production on Wed May 17 14:24:19 2017

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

SQL>conn test/test@test
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0

The ORA-01033 error also happens when the database is not open. SO in this case below is the solution :

"alter database open"


Brief about ORA-01033: ORACLE initialization or shutdown in progress :- 


Sometime when We stop our oracle database then if at the same time any user will try to access the database then that user will face the issue ORA-01033: ORACLE initialization or shutdown in progress .For work around to solve "The ORA-01033: ORACLE initialization or shutdown in progress" ask your user to wait for some time and check the status of the database. Also check the alert logs for error ORA-01033: ORACLE initialization or shutdown in progress.You need to check the status and see if your database is in the middle of startup or shutdown.

There may be other cause for error ORA-01033: ORACLE initialization or shutdown in progress is like when RAM regions held by the OS and that makes Oracle think that instance is already running. Then also Database will through the error ORA-01033: ORACLE initialization or shutdown in progress.

Solution for ORA-01033: ORACLE initialization or shutdown in progress provided by oracle. Check your database status and paas below command by SYSDBA if your database is not open.
1. wait for some time
2. check the status of DB
3. "alter database open"

Keep sharing :)

Labels:

Comments

Post a Comment

Popular posts from this blog

DBA_SCHEDULER_JOB_RUN_DETAILS and PURGE_LOG

How to purge DBA_SCHEDULER_JOB_RUN_DETAILS? Manually deleting from DBA_SCHEDULER_JOB_RUN_DETAILS is not recommended by oracle.DBA_SCHEDULER_JOB_RUN_DETAILS is a view that is using two master tables (scheduler$_job_run_details and scheduler$_event_log) and display the information about jobs history. As there is one procedure named PURGE_LOG and Oracle have Scheduler for this procedure. It will purges all rows in the job log that are older than 30 days.This is the default behavior of this procedure. You can change this to any number of days you want by setting the attribute "SET_SCHEDULER_ATTRIBUTE". e.g. exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','15'); It will purge all logs older than 15days and it will maintain the history of 15days. But If you want manually purge these logs, you can use below solution:- exec DBMS_SCHEDULER.PURGE_LOG(log_history => 15, which_log => 'JOB_LOG'); It will purge all entries from the jog log that are o...
Post a Comment
Read more

ORA-65016: FILE_NAME_CONVERT must be specified

ORA-65016: FILE_NAME_CONVERT must be specified I just started working on 12C version of oracle database.It's new to me and facing many problems. Error code: ORA-65016: FILE_NAME_CONVERT must be specified Description:"ORA-65016: FILE_NAME_CONVERT must be specified" normally occurs when you create a PDB.I will explain later what is a PDB. Cause and solution :  ORA-65016: FILE_NAME_CONVERT must be specified caused when Data files, and possibly other files, needed to be copied as a part of creating a pluggable database.Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause as a part of the statement and make sure the path you are giving to convert the file exists. I think if you are creating the PDB's using GUI then you will not face this error "ORA-65016: FILE_NAME_CONVERT must be specified". If you creating ODB using script and you have gave a wrong path then may you f...
2 comments
Read more

ORA-02051 Another Session Or Branch In Same Transaction Failed

ORA-02051 Another Session Or Branch In Same Transaction Failed (Doc ID 2253226.1)          SYMPTOMS for ORA-02051 Another Session Or Branch In Same Transaction Failed. Database performance is slow and caused   the transactions ORA-02051 another session or branch in same transaction failed or finalized CAUSE for ORA-02051 Another Session Or Branch In Same Transaction Failed. Session transactions branches caused the issue Excessive Waits On The Event "Global transaction acquire instance locks" SOLUTION Please use below sql and identified underscore parameter values for ORA-02051 Another Session Or Branch In Same Transaction Failed : SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value",c.ksppstvl "Instance Value"  FROM x$ksppi a,x$ksppcv b, x$ksppsv c  WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/'  AND (a.ksppinm like '%clusterwide_global%' or a.ksppinm like '%disable_autotune_...
Post a Comment
Read more