This post is about the fact that a cluster installation fails due to a GaussDB abnormality. More information on how to solve this issue can be found below.
Diagnostic
Cluster installation fails and the following error message is displayed:
Possible causes and solutions
[Cause 1]:
The /etc/profile file contains read-only variables. As a result, executing source /etc/profile fails.
[Solution 1]:
Run the vi /etc/profile command and delete or comment out the read-only line.
[Cause 2]:
The permission on /home/omm/.profile is incorrect, causing a GaussDB abnormality.
[Diagnostic]:
$OMS_LOG_PATH/scriptlog/ha/scriptlog/ha.log contains java: command not found.
[Fault locating]:
The message java: command not found often indicates that Java commands cannot be recognized when database passwords are decrypted using WCC during the execution of the dbfunc.sh file.
To locate the fault, check whether:
The /home/omm/.profile file contains the JDK path.
The /home/omm/.profile file can be accessed under user ommdba. After confirmation, the permission of the /home/omm directory is 700 in the environment. As a result, user ommdba cannot access the /home/omm/.profile file.
[Solution 2]:
If the /home/omm/.profile file does not contain the JDK path, add the path to the file.
If /home/omm/.profile file can be accessed under the ommdba account, change the permission.
