I got an exception when i want to start oracle which is
Erorr:ORA-01033: ORACLE initialization or shutdown in progress
this is the first time I face this problem, DBMS asks me to wait and then restart the system , since yesterday and i am trying to start it ,but I couldn't make it.
please can someone help!
As the error message indicates, this means that the database is currently either initializing or is shutting down.
ORA-01033: 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.
Sometimes, if one of the files needed for initialization is corrupted or needs recovery, you might see this message for ever. This is what you can do to see what the actual error is and then start debugging from there.
From your command prompt logon as sysdba
sqlplus /nolog
connect / as sysdba
Do a shutdown and a clean startup.
shutdown immediate;
startup;
This should indicate what is causing the issue and you'll be able to fix it.
A couple of useful links.
How to resolve ORA-011033: ORACLE initialization or shutdown in progress
http://forums.oracle.com/forums/thread.jspa?threadID=338394
Related
Conclusion: Nevermind, GCP was down ROFL
I have a MYSQL instance on cloud SQL and it has some read and write operations going on at all times, but neither the CPUs nor the memory is clogged or overloaded, I specifically checked.
It had been getting thread related issues for the past few weeks but this time it completely crashed and won't restart, every time I try and restart, it just says "An unknown error occurred"
These are the latest error logs from right before it crashed:
[Server] Can't create thread to handle new connection(errno= 11)"
and
[connection_h] Error log throttle: 742 'Can't create thread to handle new connection' error(s) suppressed"
Yesterday we moved the old data into a fresh new db and it was running well, but today it seems have been getting these thread related issues again and it crashed and won't restart.
Previously I tried to increase the ulimit by changing the limits.conf file but ulimit wasn't changing. Could that be the issue? Maybe a reconfiguration is needed?
BTW, max_connections flag is set to 10000, much higher than the default.
What can I do now? can't start the machine nor can I investigate. Feel free to ask anything.
Update:
I tried cloning the db but even clones are showing "unknown error"
Using mysql(v8.0.21) image with mac docker-desktop (v4.2.0, Docker-Engine v20.10.10)
As soon service up:
entrypoints ready
innoDB initialization done
ready for connection
But as soon try to run the direct script(query) it crashes, refused to connect (also from phpmyadmin) and restarted again.
terminal log
connection refused for phpMyAdmin
In the logs we are able to see an Error:
[ERROR] [MY-011947] [InnoDB] Cannot open '/var/lib/mysql/ib_buffer_pool' for reading: No such file or directory
The error we are able to see into log is not an issue, as it is fixed and updated by InnoDB already, here is the reference below:
https://jira.mariadb.org/browse/MDEV-11840
Note: docker-compose file we are pretty much sure that, there is no error as same is working fine for windows as well ubuntu, but the issue is only for macOS.
Thanks #NicoHaase and #Patrick for going through the question and suggestions.
Found the reason for connection refused and crashing, posting answer so that it maybe helpful for others.
It was actually due to docker-desktop macOS client there was by default 2GB Memory was allocated as Resource, and for our scenario it was required more than that.
We just allocate more memory according to our requirement and it was just started working perfectly fine.
For resource allocation:
open docker-desktop preferences
resources > advanced
My Cloud SQL instance(MySQL) with High Availability enabled is totally down now - I can't connect into MySQL service, mysqldump, Export and Clone on the console are all down, even the Stop or Restart button response nothing but error messages.
Is there any solution to save my data without data loss? If I restore instance from the last backup, it will result a 12 hours data loss, disaster.
I considered "point-in-time recovery", but the question is how to locate the binary log filename and recover position if I can't enter into MySQL.
the error log from the crashed instance:
2021-01-26 19:03:29.613 CST
2021-01-26T11:03:29.612303Z 0 [ERROR] InnoDB: Invalid redo log header checksum.
Error
2021-01-26 19:03:29.613 CST
2021-01-26T11:03:29.612315Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Error
2021-01-26 19:03:30.213 CST
2021-01-26T11:03:30.213169Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
Error
2021-01-26 19:03:30.214 CST
2021-01-26T11:03:30.214078Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Error
2021-01-26 19:03:30.214 CST
2021-01-26T11:03:30.214456Z 0 [ERROR] Failed to initialize builtin plugins.
Instances configured with High Availability should fail over to the secondary instance in a matter of minutes. While this operation is taking place is not possible to perform exports or other operations.
If the failover took 4 hour you may be eligible for a credit adjustment according to the Cloud SQL SLA. I would suggest to open support ticket if you would like to explore such path.
Lastly, I would not advise to use the legacy HA configuration as it won't be available anymore past Q1 2021 as mentioned here.
When I start infinidb, I am getting the following error message, making it impossible for the service to start. In the log file, it says there is a problem with the rollback. Is there a way to abort the rollback so I can start the service again? I am ok with losing some data.
Starting Calpont InfiniDB Database Platform: ....... DONE
Warning! The DBRM is currently in Read-Only mode!
Updates will not propagate!
Starting Calpont InfiniDB MySQL:
Starting MySQL
. *
Validate InfiniDB System Catalog:
Validation Succesfully Completed
Perform Functionality test:
InfiniDB Logging check: DONE
Platform Process check: ERROR: Problem with InfiniDB process DMLProc, should be a single version running
***Stopping InfiniDB to allow the process problem to be resolved.
Shutting down Calpont InfiniDB MySQL:
Shutting down MySQL
... *
Shutting down Calpont InfiniDB Database Platform:
/var/log/Calpont/crit.log
DMLProc[4292]: 41.458706 |0|0|0| C 20 CAL0002: DMLProc failed to start due to : problem with rollback. Version buffer file does not exists.
I already tried removing the files in /usr/local/Calpont/data1/systemFiles/dataTransaction but it still won't start.
This is how I was able to solve it.
While the service is starting:
# service infinidb start
In another ssh session go to /usr/local/Calpont/bin and look for the transaction ID causing the problem:
# ./rollback -p
Once you find out, immediately run the rollback command with the transaction id that you see:
./rollback -r 64536
It will respond with OK and the service started successfully this time. I had to do this twice because my first attempt was probably not able to rollback the transaction on time.
sorry for this post that it might be repeated, but I could not quite figure out from the other posts still.
I am unable to log on mysql localhost database, and the server is down says mysql#localhost:3366 - Refusing Connections. In mysql workbench start/shutdown mysql server, it is saying the database server instance is unknown (with start server button grayed out) and refreshing the status doesn't help.
Also, the mysql server should always be running automatically in the background whenever PC is restarted, but it is not showing in the services now.
when I try to execute mysqld from cmd, it just shuts down the server. And responds with
-"The Innodb memory heap is disabled"
-"the system tablespace must be writeable"
-"InnoDB init function returned error"
-"InnoDB registration as a storage engine failed"
Anybody has a solution to this? Thanks much!
Install it. Re-install it, if you're convinced it was already installed. The fact that it isn't even listed in the services suggests otherwise however. If it was installed but wouldn't start it would still show up, but not as started.