Loading in 2 Seconds...
Loading in 2 Seconds...
Installing Oracle Grid 11gR2 on Red Hat Enterprise Linux 5. Preparation Steps. Login to virtual server tom as user grid. Copy linux_11gR2_grid.zip into /u01/staging. Unzip the file using "unzip" command: [grid@tom staging]$ unzip linux_11gR2_grid.zip
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Preparation Steps • Login to virtual server tom as user grid. • Copy linux_11gR2_grid.zip into /u01/staging. • Unzip the file using "unzip" command: [grid@tom staging]$ unzip linux_11gR2_grid.zip • Make sure the time settings on tom and jerry are in sync: [grid@tom ~]$ date Wed Jun 9 22:17:06 PDT 2010 [grid@jerry ~]$ date Wed Jun 9 22:17:07 PDT 2010 • If the time difference is more than a few seconds, the installation could fail, so you would have to adjust the time, for example: [root@tom ~]$ date +%T -s "10:13:13" [root@jerry ~]$ date +%T -s "10:13:13" • Go to /u01/staging/grid directory and start the installation by issuing: ./runInstaller
Enter values for "Cluster Name", "SCAN Name", and "SCAN Port". Also, deselect "Configure GNS" checkbox.
Click "Add" button to add jerry to the Grid Infrastructure configuration.
Click "SSH Connectivity" button, enter OS password for user "grid", and then click "Setup".
After SSH connectivity between the nodes is successfully established, click "OK".
Confirm settings on the "Network Interface Usage" screen. If necessary, make appropriate changes.
Select "Use same password for these accounts"; enter and confirm password of your choice.
For our purpose we can ignore "[INS-30011] The password entered does not conform to the Oracle recommended standards." warning. If the message box pops up, click “Yes” to proceed.
Verify information one the "Summary" screen and click "Finish".
Executing "root" scripts in the right order a. Execute orainstRoot.sh script on tom first and wait for successful comlpetion: [root@tom ~]$ /u01/app/oraInventory/orainstRoot.sh b. Execute orainstRoot.sh script on jerry only after it successfully completes on tom: [root@jerry ~]$ /u01/app/oraInventory/orainstRoot.sh c. Execute root.sh script on tom first and wait for successful comlpetion: [root@tom ~]$ /u01/app/11.2.0/grid/root.sh d. Execute root.sh script on jerry only after it successfully completes on tom: [root@jerry ~]$ /u01/app/11.2.0/grid/root.sh e. Click "OK" on "Execute Configuration Scripts" window.
What if a root script fails? If any of the above scripts fails, do not try to rerun. • To deconfigure unsuccessful installation (as user root): # cd /u01/app/11.2.0/grid/crs/install # perl rootcrs.pl - deconfig -force [-lastnode] • To completely uninstall (as user grid): $ /u01/app/11.2.0/grid/deinstall/deinstall
Possible Bug 8670579 • Happens when 32-bit client OS (Linux) is installed on 64 bit host OS on certain types of hardware • Known bug 8670579 • Download Patch 8670579 (p8670579_112010_LINUX.zip) from Oracle Support site (account required) • Deconfigure Grid as previously explained • Install Patch 8670579 • Rerun root script(s)
Login to virtual server tom as user grid and start ASMCA. Click "Create".