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

Hey Rene!

Great to chat with you and thank you for the response!

One question:  your blog post shows a database residing on a single disk.  Have you been able to repeat this outcome with more than one disk?

Thanks!

-Tim

On 6/8/2023 10:20 AM, Rene Antunez wrote:
> Hi Tim
>
> I've done this for GCP as a PoC for a client, and for an Azure client,
> we are not actually putting the DB in backup mode for the snapshot
> based cloning, we are emulating a crash of the DB and let SMON do it's
> thing when bringing up the DB in the new VM. I don't work with them
> anymore, but as to my knowledge it worked for them.
>
> René Antúnez | 101 Series Of Oracle In Google Cloud – Part III : Using
> GCP Snapshots To Clone a DB In A VM
> <https://rene-ace.com/101-series-of-oracle-in-google-cloud-part-iii-using-gcp-snapshots-to-clone-a-db-in-a-vm/>
>
>
>
>
>
>
>
>
> René Antúnez | 101 Series Of Oracle In Google Cloud – Part III :
> Using G...
>
> <https://rene-ace.com/101-series-of-oracle-in-google-cloud-part-iii-using-gcp-snapshots-to-clone-a-db-in-a-vm/>
>
>
>
> On Thursday, June 8, 2023 at 12:00:48 PM EDT, Tim Gorman
> <tim.evdbt_at_gmail.com> wrote:
>
>
> Andrew,
>
> No.  I am not seeking to disable Restart/SIHA/OHAS.  I could get a
> better result by changing the startoptions from open to mount, by the way.
>
> The problem is that, when the database doesn't need recovery, the
> customer wants it automatically opened. However, when the database
> needs roll-forward recovery, we do not want Restart/SIHA/OHAS to
> attempt to do anything more than MOUNT the database.
>
> That bit of basic intelligence is what the Restart/SIHA/OHAS product
> appears to be currently lacking.  With OPEN or MOUNT as the only
> available STARTOPTIONS, the product is going to disappoint (or cause a
> disaster) one way or the other.
>
> -Tim
>
>
>
> On 6/8/2023 9:50 AM, Andrew Kerber wrote:
> crsctl disable has will disable has entirely. Is that what you are
> looking for?
>
> On Thu, Jun 8, 2023 at 10:26 AM Tim Gorman <tim.evdbt_at_gmail.com
> <mailto:tim.evdbt_at_gmail.com>> wrote:
>
> 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
> --
> http://www.freelists.org/webpage/oracle-l
> <http://www.freelists.org/webpage/oracle-l>
>
>
>
>
> --
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
>

--
http://www.freelists.org/webpage/oracle-l