Database Reference
In-Depth Information
The following environment variables are set as:
ORACLE_OWNER= grid
ORACLE_HOME= /u01/app/grid/product/12.1.0.1/grid
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/app/grid/product/12.1.0.1/grid/crs/install/crsconfig_params
LOCAL ADD MODE
Creating OCR keys for user 'grid', privgrp 'oinstall'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node server1 successfully pinned.
2013/09/06 18:42:03 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.conf'
Server1 2013/09/06 18:42:32 /u01/app/grid/product/12.1.0.1/grid/cdata/server1/
backup_20130906_184232.olr
2013/09/06 18:43:18 CLSRSC-327: Successfully configured Oracle Grid Infrastructure
for a Standalone Server
If you see the last line “successfully configured Oracle Grid Infrastructure for a Standalone Server”, all is well you
have successfully executed the root.sh script.
In the past it has been difficult to troubleshoot problems with the root.sh script. These have gradually been
addressed with the latest releases. A major improvement is the verbose logging created during the execution of the
root.sh script. The file you need to consult is in somewhat hidden in
$GRID_HOME/cfgtoollogs/crsconfig/roothas.
log
. Should you run into problems during the execution of root.sh, begin your investigation there. It shows in great
detail which steps are performed on your behalf. Studying the contents of the roothas.log file can greatly improve
your understanding of how Grid Infrastructure works internally, but has to be left as an exercise to the reader to do so.
Unlike the root.sh for a clustered installation, the script does not seem to be restartable.
If you have adhered to the configuration described in Chapter 5, you should not have any problems with the
root.sh script. Common problems encountered in the field are mismatches between /etc/hosts and DNS entries, or
ignored prerequisites. Usually the error reported in roothas.log is specific enough to point you to the problem.
Finishing the installation
After the successful execution of the root scripts, click the “OK” button to dismiss the dialog. Control will return to
the Oracle Universal Installer session, and the final configuration will complete the installation. This is shown
in Figure
6-15
.
Search WWH ::
Custom Search