# ./rootconfig
Checking to see if Oracle CRS stack is already configured
Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory '/oracle/product' is not owned by root
WARNING: directory '/oracle' is not owned by root
Failure at scls_scr_create with code 1
Internal Error Information:
Category: 1234
Operation: scls_scr_create
Location: mkdir
Other: Unable to make user dir
Dep: 2
Failure initializing entries in /var/opt/oracle/scls_scr/HOSTNAME01.
So, I found out some information on metalink.
this case, I used choice II:
mv /usr/bin/awk /usr/bin/awk-org
ln -s /usr/bin/nawk /usr/bin/awk
and then run rootconfig again. It's OK.
Checking to see if Oracle CRS stack is already configured
Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory '/oracle/product' is not owned by root
WARNING: directory '/oracle' is not owned by root
Failure at scls_scr_create with code 1
Internal Error Information:
Category: 1234
Operation: scls_scr_create
Location: mkdir
Other: Unable to make user dir
Dep: 2
Failure initializing entries in /var/opt/oracle/scls_scr/HOSTNAME01.
So, I found out some information on metalink.
Cause :
This issue is caused by the host name problem as explained in Bug 4632899
Bug 4632899 -- CSS NOT STARTING UP IF HOSTNAME HAS CAPITAL LETTERS-
SOLARIS
Rediscovery Information:
On Solaris, when the hostname is in
Capital, the following
errors might be noticed when using crs scripts.
Solution :
This basically happens because awk does not have the tolower() function in
the Sun Solaris. The call to tolower() on Solaris 9 and Solaris 10 returns the
unchanged uppercase hostname.
The followings options are available to
resolve this:
1.
Change the host name to lower case.
OR
2. "nawk" has the tolower()
function. Setup a symbolic link to "nawk"
ln -s /usr/bin/nawk
/usr/bin/awk
this case, I used choice II:
mv /usr/bin/awk /usr/bin/awk-org
ln -s /usr/bin/nawk /usr/bin/awk
and then run rootconfig again. It's OK.
2 comments:
super post,,,,
i faced similar problem,,,,and this really helped me out.
Thanx
Thanks man! I'm doing an ATP at a customer site - just got me out of a jam! :)
Post a Comment