Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

# backup
echo "connect internal;" > $SRVMGRDBA_CMD_FILE
echo "startup mount;" >> $SRVMGRDBA_CMD_FILE
echo "spool endbackup.log" >> $SRVMGRDBA_CMD_FILE
echo "select 'alter database datafile '''||f.name||''' end backup;'" >>
$SRVMGRDBA_CMD_FILE
echo "from v\$datafile f, v\$backup b" >> $SRVMGRDBA_CMD_FILE
echo "where b.file# = f.file# and b.status = 'ACTIVE'" >> $SRVMGRDBA_CMD_FILE
echo "/" >> $SRVMGRDBA_CMD_FILE
echo "spool off" >> $SRVMGRDBA_CMD_FILE
echo "!grep '^alter' endbackup.log >endbackup.sql" >> $SRVMGRDBA_CMD_FILE
echo "@endbackup.sql" >> $SRVMGRDBA_CMD_FILE
echo "!rm endbackup.*" >> $SRVMGRDBA_CMD_FILE
echo "alter database open;" >> $SRVMGRDBA_CMD_FILE
echo "exit;" >> $SRVMGRDBA_CMD_FILE
eval $SRVMGRDBA command=@$SRVMGRDBA_CMD_FILE >> $LOG 2>&1
Oracle Database Step: OR860
Configure the listener to listen on the relocatible name of the database package.
Perform the following steps as ora<sid>.
To do this, change all references from <local> to the relocatible name <relocdb> in the files on the
shared volume group. Be careful if these files were customized after the SAP installation. For example:
$ORACLE_HOME/network/admin/listener.ora
$ORACLE_HOME/network/admin/tnsnames.ora
When using Oracle 10g:
/sapmnt/<SID>/profile/oracle/listener.ora
/sapmnt/<SID>/profile/oracle/tnsnames.ora
Oracle Database Step: OR870
Copy $ORACLE_HOME/network/admin/tnsnames.ora to all additional application server hosts.
Be careful if these files were customized after the SAP installation.
Oracle Database Step: OR880
Be sure to configure and install the required Oracle NLS files and client libraries as mentioned in section
Oracle Storage Considerations included in chapter Planning the Storage Layout
Also refer to SAP OSS Note 180430 for more details.
Optional Step: OR890
If you use more than one SAP system inside of your cluster:
It is possible that more than one database is running on the same node. Even though one listener is capable
of serving many database instances problems can occur in switchover environments because needed file
systems may not be available at the startup time of the listener. Use a dedicated listener process for each
database.
You can use the standard file that is created during the installation of one SAP system <SID1> as a template.
Double its contents, for example:
cat listener.ora listener.ora >listener.ora.new
mv listener.ora.new listener.ora
The file consists of two identical parts
94 Step-by-Step Cluster Conversion