My Oracle Support Banner

Solaris Cluster How to Configure SAP Transaction DB13 to Backup Database Used by the Central Instance (Doc ID 1616923.1)

Last updated on MARCH 09, 2017

Applies to:

Solaris Cluster Geographic Edition - Version 3.2 to 4.3 [Release 3.2 to 4.3]
Solaris Cluster - Version 3.2 to 4.3 [Release 3.2 to 4.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)

Goal

For SAP system with Oracle database that managed by Solaris Cluster, while using BRBACKUP (executed from transaction DB13, SM49 or directly from OS level) to make offline database backup. The BRBACKUP stops the Oracle database, but the Solaris Cluster detects Oracle database is offline and restarts it.

Following message are reported by Solaris Cluster when the backup is done and the database being shutdown by SAP:

Oct 17 19:07:29 paris Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource rs_ora_A01 status on node paris change to R_FM_FAULTED
Oct 17 19:07:29 paris Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group rg_ora-sapA01 state on node paris change to RG_ON_PENDING_R_RESTART 

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 1. Configuration of init<DBSID>.sap
 2. Configuration or oracle user's privilege


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.