Re: How to prevent Oracle Restart/SIHA/OHAS from attempting to open database needing recovery

Not sure if I have my full posting privileges right now or not, but the old “action scripts” might be applicable here. We used them years ago on a similar setup. I think ours was a full CRS 11.2 cluster with single instance databases. A quick google search didn’t find the Oracle hosted version of this white paper, but here’s somebody else hosting it, https://levipereira.files.wordpress.com/2012/05/si-db-failover-11g-134623.pdf

You might be able to add logic there to do a startup mount, check for recovery, and then open the database. I don’t know if this would work with Oracle Restart instead of the full CRS stack.

Thanks,
Ross

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> on behalf of Tim Gorman <tim.evdbt_at_gmail.com> Date: Thursday, June 8, 2023 at 9:26 AM
To: ORACLE-L <oracle-l_at_freelists.org> Subject: How to prevent Oracle Restart/SIHA/OHAS from attempting to open database needing recovery CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Friends and colleagues,

I have a customer using Oracle Restart (i.e. single-instance installation of Oracle Grid Infrastructure, a.k.a. SIHA, a.k.a. OHAS) for access to Oracle ASM.

They have a situation where they are restoring the entire VM from storage-level snapshots, including the Oracle database which was in "backup mode" at the time of the snapshot, and Oracle Restart is attempting to automatically open the database (which needs roll-forward recovery).

This automatic restart makes sense under normal conditions, when the database is not in need of media recovery. However, when the database is in need of media recovery, then automatically opening the database eliminates any possibility of performing roll-forward media recovery.

We can use srvctl to set startoptions from open to mount, and that will solve the problem when roll-forward media recovery is needed, but it leaves the database in unusable mount mode when the automatic restart is expected to automatically open the database.

So, Oracle Restart apparently does either STARTUP OPEN or STARTUP MOUNT blindly, instead of perhaps first MOUNTing the database, then checking if media recovery is needed before an OPEN is attempted, which would be the intelligent thing to do, and not difficult to automate into srvctl.

Has anyone resolved this problem?

Thanks!

-Tim
--

https://urldefense.com/v3/__http://www.freelists.org/webpage/oracle-l__;!!N4fOi5Mv!cm5uEXrwOZkvOVWa5EQU8wRVtXZ4p9_d84wlZVcC22mJVaw646ylOSuIMA04g23raFOZTWnAGoSrbCrsbIUfhA$<https://urldefense.com/v3/__http:/www.freelists.org/webpage/oracle-l__;!!N4fOi5Mv!cm5uEXrwOZkvOVWa5EQU8wRVtXZ4p9_d84wlZVcC22mJVaw646ylOSuIMA04g23raFOZTWnAGoSrbCrsbIUfhA$>

--

http://www.freelists.org/webpage/oracle-l Received on Thu Jun 08 2023 - 18:13:27 CEST