Oracle B32100-01 User Manual

Page of 258
Post-Installation Steps for OracleAS Cold Failover Cluster
Installing in High Availability Environments: OracleAS Cold Failover Cluster
8-31
8.9 Post-Installation Steps for OracleAS Cold Failover Cluster
8.9.1 Edit the ORACLE_HOME/Apache/Apache/htdocs/index.html File
In the ORACLE_HOME/Apache/Apache/htdocs/index.html file, change all 
occurrences of the physical hostname (example: node1) to the virtual hostname 
(example: vhost), where node1 appears as a hostname.
Note that if node1 is used as part of the Oracle Application Server instance name, do 
not change it.
8.9.2 Copy the /var/opt/oracle Directory to the Other Node
After the OracleAS Infrastructure installation is complete, copy the 
/var/opt/oracle
 directory from the node where you performed the installation to 
the other node in the OracleAS Cold Failover Cluster. This ensures that you can run 
the installer to update the Oracle home from either node in the cluster.
Be sure to keep the two /var/opt/oracle directories in sync. Whenever you run the 
installer to update the infrastructure, you need to copy the oracle directory to the 
other node.
The /var/opt/oracle directory is not used during runtime by Oracle Application 
Server. It is used only by the installer.
8.9.3 Running Database Console against a Cold Failover Cluster Database
Before you can start, stop or check the status of Database Console against a cold 
failover cluster database, you need to set the ORACLE_HOSTNAME environment 
variable to the virtual hostname. For example, in 
, the virtual hostname is 
vhost.mydomain.com. You would set ORACLE_HOSTNAME as follows:
C shell:
$ setenv ORACLE_HOSTNAME vhost.mydomain.com
Bourne or Korn shell:
% ORACLE_HOSTNAME=vhost.mydomain.com
% export ORACLE_HOSTNAME
7.
Oracle Database screens
Enter information for the OracleAS Metadata Repository database. See 
.
8.
--
Finish the installation. Se
 for details.
Table 8–10
(Cont.) Installing the OracleAS Metadata Repository Only
Screen
Action