i have an error which is driving me crazy and i dont know how to deal with it. In a PC with windows 10 64-bit , i got an oracle database server 11g. Everytime the pc restarts or shuts down and then restarts i get the following error when i try to connect to the database :
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
the only way to get my database running is the following one:
open a cmd and type :
rman target /
recover database;
shutdown immediate;
startup mount;
alter database open resetlogs;
after that everything is fine , but if i restart the PC i get the same error again.
Has anyone dealted with anything like this before?
I have checked the hard disk and is ok, have defragmented it, have run test diagnostics, it is driving me crazy. Any idea would be welcome!
Thanx in advance!
That is a pretty general error. Your database can have issues with either starting up or maybe shuting down cleanly.
I would recommend you looking at the end of the alert.log file right after the server is started, before performing rman recovery.
You can find hints there as why the database did not started up to open state, where and why it is hanging, etc.
EDIT: So the error is ORA-00600 [dbkif_find_next_record_1]
Whenever an ORA-00600, or ORA-00700 or ORA-07445 occurs, this is an internal error within Oracle core. For this cases there is this neat tool at http://support.oracle.com which can search the knowledge base of Oracle MySupport network and try to find existing articles and/or patches, hotfixes for respective arguments of these internal errors.
The tool can be found as Oracle Support Doc ID 153788.1.
Unfortunatelly, the lookup tool did not found anything for argument ORA-00600 [dbkif_find_next_record_1]. In that case please make sure that your OS is updated and supported. Also if you are running on VM, that the VM has all parameters set according to Oracle's recommendations and if there is nothing suspicious there, you will have to open "Service request" at http://support.oracle.com
Related
We have this old software that with local oracle db. The computer started crashing yesterday. Somehow I was able to bring it back to life, but now I keep getting this "ORA-01033" error whenever trying to start the software. And unfortunately I do not have admin dba access to the database. So I can't try this guide
How to resolve ORA-011033: ORACLE initialization or shutdown in progress
So far I've tried
restarting the computer
restarting OracleService in "services"
restarting "Oracle TNS listener in "services"
Any tip would be greatly appreciated.
Try the below
sqlplus
shutdown abort
startup mount
recover database
alter database open
alter database open resetlogs
I am not able to run any query to change to CDB or PDB in SQL plus it shows the above error.
For instance I tried running the query
Alter pluggable database open
and got this error.
ERROR at line 1:
ORA-65090: operation only allowed in a container database
The correct command to change Container is
ALTER SESSION SET CONTAINER = containername;
If you are getting error then you must not be a privileged user
follow up this link for more information
https://docs.oracle.com/database/121/ADMIN/cdb_pdb_admin.htm#GUID-E73BCAED-FF57-474A-A8C5-207D3F465413
I solved it. Though the solution is not a preferable one but it worked for me as of now. I used Database configuration assistant and deleted the pdb in which I getting connected to when logging using sqlplus. I would appreciate some proper solution to this.
I am connecting to oracle 12 in Oracle cloud, from PowerBI Desktop windows server 2016.
Oracle client is installed and TNS file configured.
Oracle is hosted by a vendor so my only access is to directly query the database.
In powerBI, when using an oracle connection, i get ORA-03113 errors about 50% of the time when refreshing data. There is no discernible pattern to the appearance of the error.
If i connect via a System ODBC connection set up in windows, I dont get any issues or errors, although the data load is a bit slower.
I would appreciate ideas on what may be causing this issue or what to check to help get more information.
I'm afraid your issue needs some deeper analysis as ORA-03113 might have various reasons, but typically it means that the 'oracle' executable has terminated unexpectedly once there was an existing connection. You should try to isolate the SQL command that is executing when the error occurs. It can be done either by checking the trace files on the server or by using SQL*Net trace if you don't have access to the server. If a statement can be isolated which consistently raises the ORA-3113 error, then it can be further analysed (like execution plan, triggers, etc), or maybe the best to raise an SR so Oracle Support can work on the issue. If you have access to Oracle Support you can find more information about ORA-03113 troubleshooting in MOS Doc ID 1506805.1. Let me know if I can help you any further.
Im having some trouble with an oracle database. Every time i try to connect, i get this message.
ORA-01033: ORACLE initialization or
shutdown in progress
I searched the web, and found that the solution is to execute an alter database open command, but what I dont understand is where should i execute if, since I cant connect to the database.
Am I missing something?
Thanks in advance
You should connect AS SYSDBA:
sqlplus "sys/pwd AS SYSDBA"
An ORA-01033 would also be thrown if the connection attempt were made against a mounted standby database (Oracle Data Guard environment) by a non-sysdba user. Maybe a database role change (switchover or failover) has occurred since your last connection attempt.
Which OS are you using? The database is still shutting down - check the alert log as to the status of where it is at. Sometimes there are sessions hanging around that need to manually be killed off, there should be an indication of this in the alert log. It also depends how the database was shutdown, NORMAL, TRANSACTIONAL, IMMEDIATE. Even with a SHUTDOWN IMMEDIATE the sessions hanging around may still happen. To find the sessions on UNIX use the 'ps' to list all processes on the server ('ps -eaf' on Solaris) command and 'grep' for the ORACLE_SID name.
My team inherited an Oracle-based web application and they are fairly inexperienced with Oracle database servers.
The Oracle 10g server is running on a Windows 2003 Server with plenty of disk space and from time to time, all connectivity is lost, the application stops working, not even SQL Plus is able to connect to the database server.
But when we check the Windows Service manager, it says that the service is up and running. A restart usually fixes the problem, but we need to properly troubleshoot it so we know what's causing it and so we can avoid it to happen anymore.
Where should we start looking for clues? What are the criticial log files we should be investigating?
On the server you should have an environment variable called ORACLE_HOME which indicate the root of the Oracle install. Most likely the Oracle trace/dump folders will be under there. Search for a folder called "bdump" (background dump). That's where the main log file, knows as the alert log, will be, as well as trace files generated by background processes. There will be an adjacent file called "udump" which will contain any trace files generated by user processes.
However, my real advice is that you should either hire someone who knows Oracle or get Oracle Support involved.
The alert log would be the first file to check.
It will probably be in $ORACLE_HOME/admin/bdump and (probably) called alert_DATABASE-SID.log
It contains most of the important actions that the database does, as well as any important errors that occur.
I have to agree with cagcowboy. Check your alert logs for errors. If no errors then maintain a sysdba login into the database and when it hangs, attempt to do a hang analysis. See metalink note 215858.1 on hanganalyze.
Have you tried tnsping? We've occasionally run into problems with the listener that requires an assist from our DBA. tnsping is the diagnostic tool we use to do triage.
I would recommend hiring an experienced Oracle DBA if at all possible.
check the alert log to see how the Db is structured. sometimes badly set parameters make hangs or slow performance. or you can shutdown and start in mount mode, then check the v$parameter values for problems. setting total memory is very important.