Oracle11gR2 Silent Installation of RAC cluster and database software

Due to some remote installation requirements, the remote interaction of the oui gui is slow, which may affect the speed of DBA's RAC installation. Or some enterprises disable XWindow, which also causes failure.

Due to some remote installation requirements, the remote interaction of the oui gui is slow, which may affect the speed of DBA's RAC installation. Or some enterprises Disable X Window, which also causes failure.

Due to some remote installation requirements, remote interaction on the oui gui is slow, which may affect the speed of DBA's RAC installation. Or some enterprises Disable X Windows, which also makes it impossible to use OUI for standard RAC installation.

The following is a test of the Silent Installation of the Database Cluster software (gi home) and database software (rdbms home), hoping to help DBAs who cannot use the OUI above.

The test environment is a two-node RAC for Silent Installation of version 11.2.0.3. The OS environment is as follows:
$ Uname-
Linux nascds10 2.6.9-78.0.0.0.1.ELhugemem #1 SMP Fri Jul 25 14:53:18 EDT 2008 i686 i686 i386 GNU/Linux

-Bash-3.00 $ cat enterprise-release
Enterprise Linux AS release 4 (October Update 7)
The storage uses Oracleasmlib for configuration management:
[Root @ nascds10 ~] #/Etc/init. d/oracleasm listdisks
DATA
OCR
RECO
The procedure is as follows:

11.2.0.3 cluster software (GI) Silent Installation

Decompress the software installed in the 11.2.0.3 cluster to the/home/grid/11.2.0.3/grid path.
1. Run runcluvfy. sh to run the pre-check before installation to avoid installation failure caused by Environment configuration.

Su-grid
Cd/home/grid/11.2.0.3/grid
-Bash-3.00 $./runcluvfy. sh stage-pre crsinst-n nascds10, nascds11-verbose

Specific output
-Bash-3.00 $./runcluvfy. sh stage-pre crsinst-n nascds10, nascds11-verbose

Grouping pre-checks for cluster services setup

Checking node reachability...

Check: Node reachability from node "nascds10"
Destination Node Reachable?
------------------------------------------------------------
Nascds10 yes
Nascds11 yes
Result: Node reachability check passed from node "nascds10"

Checking user equivalence...

Check: User equivalence for user "grid"
Node Name Status
------------------------------------------------------------
Nascds11 passed
Nascds10 passed
Result: User equivalence check passed for user "grid"

Checking node connectivity...

Checking hosts config file...
Node Name Status
------------------------------------------------------------
Nascds11 passed
Nascds10 passed

Verification of the hosts config file successful

Interface information for node "nascds11"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
-----------------------------------------------------------------------------------------
Eth1 169.254.218.24 169.254.0.0 0.0.0.0 10.182.208.1 00: 14: 22: BD: 59: DE 1500
Eth1 192.168.10.2 192.168.10.0 0.0.0.0 10.182.208.1 00: 14: 22: BD: 59: DE 1500
Eth0 10.182.208.33 10.182.208.0 0.0.0.0 10.182.208.1 00: 21: 27: 04: F7: E3 1500
Eth0 10.182.208.33 10.182.208.0 0.0.0.0 10.182.208.1 00: 21: 27: 04: F7: E3 1500
Eth0 10.182.208.29 10.182.208.0 0.0.0.0 10.182.208.1 00: 21: 27: 04: F7: E3 1500
Eth0 10.182.208.34 10.182.208.0 0.0.0.0 10.182.208.1 00: 21: 27: 04: F7: E3 1500
Eth0 10.182.208.35 10.182.208.0 0.0.0.0 10.182.208.1 00: 21: 27: 04: F7: E3 1500

Interface information for node "nascds10"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
-----------------------------------------------------------------------------------------
Eth1 192.168.10.1 192.168.10.0 0.0.0.0 10.182.208.1 00: 14: 22: CB: 05: 5C 1500
Eth0 10.182.208.32 10.182.208.0 0.0.0.0 10.182.208.1 00: 19: E0: 3F: 50: 2B 1500

Check: Node connectivity of subnet "169.254.0.0"
Result: Node connectivity passed for subnet "169.254.0.0" with node (s) nascds11