Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Application Configuration
Chapter 280
Application Configuration
This section describes the application configuration through the
following topics:
• Additional Steps for Oracle Databases
• Additional Steps for SAPDB Databases
• SAP WAS Configuration
Additional Steps for Oracle
Logon as root to the primary host of the database where the package is
running in debug mode.
OR900 Oracle Database Step:
Create additional links for the environment files in /oracle/<DBSID>.
Several environment scripts may exist, depending on the ORACLE and
SAP releases. Typical filenames are .dbenv_<primary>.csh,
.sapenv_<primary>.csh and .sapsrc_<primary>.csh.
ln .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
The following statements should automate this activity for standard
directory contents:
su - ora<sid>
ls .??*|awk '/<primary>/ { system(sprintf (“ln %s %s\n”, $0,\
gensub( “<primary>”, “<secondary>”, 1))) }'
exit
OR910 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
datafiles that were in ‘begin backup’ state need to be altered with an ‘end
backup’ statement. Change the following code within the
/sapmnt/<SID>/exe/startdb file.
#