10.5.3 How to Configure the HA-DBMS

1. Shut down SAP and the database.

   # su - <sapsid>adm $ stopsap all ... # su - ora<sapsid> $ lsnrctl stop

2. (For SAP 3.1x only) Adjust the Oracle alert file parameter in the init<SAPSID>.ora file.

   By default, SAP uses the prefix "?/..." in the init<SAPSID>.ora file to denote the relative path from $ORACLE_HOME. The Sun Cluster fault monitors cannot parse the prefix, but instead require the full path name to the alert file. Therefore, you must edit the /oracle/<SAPSID>/dbs/init<SAPSID>.ora file and define the dump destination parameters as follows:

   background_dump_dest = /oracle/<SAPSID>/saptrace/background

3. Register and activate the database.

   Run the hareg(1M) command from only one node. For example, for Oracle:

   # hareg -s -r oracle -h DBloghost # hareg -y oracle

4. Set up the database instance.

   See Chapter 5, Setting Up and Administering Sun Cluster HA for Oracle, for more information.

   For example, for Oracle:

   # haoracle insert <SAPSID> DBloghost 60 10 120 300 \ user/password /oracle/<SAPSID>/dbs/init<SAPSID>.ora LISTENER

5. Start fault monitoring for the database instance.

   For example:

   # haoracle start <SAPSID>

6. Test switchover of the HA-DBMS.

   For example:

   # scadmin switch clustername phys-hahost2 DBloghost