Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Database Configuration
Chapter 3166
All these parameters can be used to tune the duration of Instance / Crash
recovery.
More details on these useful High-Availability features can be found both
in the Oracle8i and Oracle9i documentation Oracle8i Designing and
Tuning for Performance (Chapter 24: Tuning Instance recovery
Performance) and Oracle9i Database Performance Tuning Guide and
Reference Release 2 (9.2).
The following steps have to be performed in order to adjust the Oracle
RDBMS setting to the High Availability configuration.
Logon as root to the primary host of the database where the package is
running in debug mode.
OR850 Oracle Database Step:
Perform the following step as <sid>adm.
To ensure that a database that crashed during an online backup starts
correctly after the crash, all data files that were in begin backup state
need to be altered with an end backup statement. Adjust the required
steps in /sapmnt/<SID>/exe/startdb.
Therefore, startdb needs to be adjusted accordingly. Insert / Change
the following code within the /sapmnt/<SID>/exe/startdb file. The
sample code can be found in the file: ${SAPSTAGE}/SID/startdb.sql
#
# Startup the database without changing the ARCHIVELOG state
#
echo "connect internal;" > $SRVMGRDBA_CMD_FILE
echo "startup;" >> $SRVMGRDBA_CMD_FILE
echo "exit;" >> $SRVMGRDBA_CMD_FILE
eval $SRVMGRDBA command=@$SRVMGRDBA_CMD_FILE >> $LOG 2>&1
#
# Startup the database without changing the ARCHIVELOG state
# alter datafile 'end backup' when instance crashed during
# backup
echo "connect internal;" > $SRVMGRDBA_CMD_FILE