"Oracle DBA tips, scripts and error message solutions"
You’re here because you’re getting the ORA-16433: The database must be opened in read/write mode error message.
But first, here is how I got the error. The reason I’m writing this is so that it will help you understand the ORA 16433 error message a little better as it could be different for your specific situation.
While planning my Oracle database 11g upgrade from 10g to 11g, I decided to test out creating a guaranteed restore point before starting the upgrade so that I could flashback very easily if there were any issues.
ORA-16433: The database must be opened in read/write mode.
This looked promising, I thought, so now maybe I can flashback the database to the guaranteed restore point?
ORA-38757: Database must be mounted and not open to FLASHBACK.
So, it would seem that during the upgrade process from 10.2.0.4 to 11.2.0.3 the part of the control file which should be updated is not which means that when the 11.2.0.3 DB attempts to read it the mismatched information is there and causes a problem.
After raising this issue with support a new bug was raised, 11713495, as they were able to re-produce in house with my control file. I haven’t heard back from them about the status of this bug.
You may also be getting the ORA-38785: Media recovery must be enabled for guaranteed restore point error, which I have also written about.
Hopefully that helped you out and resolved your Oracle error. While you’re here, what steps are you taking to improve your Oracle knowledge?
Would you consider yourself an Oracle expert? Good, because that means you are serious about your career and that will always reap rewards. My personal belief is that experience trumps certifications.
© 2019 ORA00600. All rights reserved.