search

oraclebase / vagrant

Vagrant Builds
https://oracle-base.com/
GNU General Public License v3.0
194 stars 170 forks source link

OL7 19C RAC Installation node1 error #17

Closed ghost closed 3 years ago

ghost commented 3 years ago

Hi Tim,

I was following the steps from your site and I ran into an error very similar to the one in #15 . The only changes I made were amending the file paths and slightly reducing the memory allocated to each node. I'm not sure if related, but I was also experiencing the "Windows Host Build Failure" issue that is in the README and I got past it using the suggested fix (to restart the DNS node). If you have any suggestions, that would be great. Thank you very much!

default: Do grid software-only installation. Fri Jan 8 22:45:48 UTC 2021
default: ******************************************************************************
default: Launching Oracle Grid Infrastructure Setup Wizard...
default: [WARNING] [INS-41808] Possible invalid choice for OSASM Group.
default:    CAUSE: The name of the group you selected for the OSASM group is commonly used to grant other system privileges (For example: asmdba, asmoper, dba, oper).
default:    ACTION: Oracle recommends that you designate asmadmin as the OSASM group.
default: [WARNING] [INS-41809] Possible invalid choice for OSDBA Group.
default:    CAUSE: The group name you selected as the OSDBA for ASM group is commonly used for Oracle Database administrator privileges.
default:    ACTION: Oracle recommends that you designate asmdba as the OSDBA for ASM group, and that the group should not be the same group as an Oracle Database OSDBA group.
default: [WARNING] [INS-41812] OSDBA and OSASM are the same OS group.
default:    CAUSE: The chosen values for OSDBA group and the chosen value for OSASM group are the same.
default:    ACTION: Select an OS group that is unique for ASM administrators. The OSASM group should not be the same as the OS groups that grant privileges for Oracle ASM access, or for database administration.
default: [WARNING] [INS-40109] The specified Oracle Base location is not empty on this server.
default:    ACTION: Specify an empty location for Oracle Base.
default: [WARNING] [INS-13014] Target environment does not meet some optional requirements.
default:    CAUSE: Some of the optional prerequisites are not met. See logs for details. gridSetupActions2021-01-08_10-45-48PM.log
default:    ACTION: Identify the list of failed prerequisite checks from the log: gridSetupActions2021-01-08_10-45-48PM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.
default: The response file for this session can be found at:
default:  /u01/app/19.0.0/grid/install/response/grid_2021-01-08_10-45-48PM.rsp
default:
default: You can find the log of this install session at:
default:  /tmp/GridSetupActions2021-01-08_10-45-48PM/gridSetupActions2021-01-08_10-45-48PM.log
default:
default: As a root user, execute the following script(s):
default:
default:    1. /u01/app/oraInventory/orainstRoot.sh
default:    2. /u01/app/19.0.0/grid/root.sh
default: Execute /u01/app/oraInventory/orainstRoot.sh on the following nodes:
default: [ol7-19-rac1, ol7-19-rac2]
default: Execute /u01/app/19.0.0/grid/root.sh on the following nodes:
default: [ol7-19-rac1, ol7-19-rac2]
default:
default: Run the script on the local node first. After successful completion, you can start the script in parallel on all other nodes.
default:
default: Successfully Setup Software with warning(s).
default: As install user, execute the following command to complete the configuration.
default:    /u01/app/19.0.0/grid/gridSetup.sh -executeConfigTools -responseFile /u01/app/19.0.0/grid/install/response/gridsetup.rsp [-silent]
default:
default: Moved the install session logs to:
default:  /u01/app/oraInventory/logs/GridSetupActions2021-01-08_10-45-48PM
default: ******************************************************************************
default: Run grid root scripts. Fri Jan 8 22:50:37 UTC 2021
default: ******************************************************************************
default: Changing permissions of /u01/app/oraInventory.
default: Adding read,write permissions for group.
default: Removing read,write,execute permissions for world.
default: Changing groupname of /u01/app/oraInventory to oinstall.
default: The execution of the script is complete.
default: Changing permissions of /u01/app/oraInventory.
default: Adding read,write permissions for group.
default: Removing read,write,execute permissions for world.
default: Changing groupname of /u01/app/oraInventory to oinstall.
default: The execution of the script is complete.
default: Check /u01/app/19.0.0/grid/install/root_ol7-19-rac1.localdomain_2021-01-08_22-50-37-602963170.log for the output of root script
default: Check /u01/app/19.0.0/grid/install/root_ol7-19-rac2.localdomain_2021-01-09_00-03-05-829161842.log for the output of root script
default: ******************************************************************************
default: Do grid configuration. Sat Jan 9 00:03:34 UTC 2021
default: ******************************************************************************
default: Launching Oracle Grid Infrastructure Setup Wizard...
default: The configuration that needs to be performed as privileged user is not completed. The configuration tools can only be executed after that.
default: You can find the logs of this session at:
default: /u01/app/oraInventory/logs/GridSetupActions2021-01-09_00-03-34AM
default:
default: As a root user, execute the following script(s):
default:    1. /u01/app/19.0.0/grid/root.sh
default:
default: Execute /u01/app/19.0.0/grid/root.sh on the following nodes:
default: [ol7-19-rac1, ol7-19-rac2]
default:
default: Run the script on the local node first. After successful completion, you can start the script in parallel on all other nodes. After the successful root script execution, proceed to re-run the same 'gridSetup.sh -executeConfigTools' command.
default:
default: Successfully Configured Software.
default: ******************************************************************************
default: Create additional diskgroups. Sat Jan 9 00:04:05 UTC 2021
default: ******************************************************************************
default:
default: SQL*Plus: Release 19.0.0.0.0 - Production on Sat Jan 9 00:04:05 2021
default: Version 19.3.0.0.0
default:
default: Copyright (c) 1982, 2019, Oracle.  All rights reserved.
default:
default: Connected to:
default: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
default: Version 19.3.0.0.0
default: SQL>   2
default: Diskgroup created.
default:
default: SQL>   2
default:
default: Diskgroup created.
default: SQL>
default: SQL> SQL> SQL>
default:
default: NAME                              COMPATIBILITY
default: ------------------------------ ------------------------------------------------------------
default: CRS                               19.0.0.0.0
default: DATA                              19.0.0.0.0
default: RECO                              19.0.0.0.0
default:
default: SQL>
default: Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
default: Version 19.3.0.0.0
default: ******************************************************************************
default: Check cluster configuration. Sat Jan 9 00:04:24 UTC 2021
default: ******************************************************************************
default: ******************************************************************************
default: Unzip database software. Sat Jan 9 00:04:24 UTC 2021
default: ******************************************************************************
default: ******************************************************************************
default: Do database software-only installation. Sat Jan 9 00:07:56 UTC 2021
default: ******************************************************************************
default: Launching Oracle Database Setup Wizard...
default: [FATAL] [INS-35355] The node ol7-19-rac2 specified in response file is not part of the Oracle Clusterware detected.
default:    CAUSE: The node list for the Oracle RAC database specified in the response file does not match the configuration stored in the OCR.
default:    ACTION: Please specify a valid node or add this node ol7-19-rac2 to the cluster.
default: ******************************************************************************
default: Run DB root scripts. Sat Jan 9 00:08:09 UTC 2021
default: ******************************************************************************
default: Check /u01/app/oracle/product/19.0.0/dbhome_1/install/root_ol7-19-rac1.localdomain_2021-01-09_00-08-09-790757046.log for the output of root script
default: sh: /u01/app/oracle/product/19.0.0/dbhome_1/root.sh: No such file or directory
default: ******************************************************************************
oraclebase commented 3 years ago

Hi.

Comparing your output to mine I see something odd.

Under the "Do grid configuration." section, you have this line, which I do not see in my output.

default: The configuration that needs to be performed as privileged user is not completed. The configuration tools can only be executed after that.

So it looks like the installation did not complete during your build. Specifically the root.sh stuff.

At the bottom of the "Run grid root scripts." section it lists the logs of the output from the root.sh runs. From your output that would be the following.

default: Check /u01/app/19.0.0/grid/install/root_ol7-19-rac1.localdomain_2021-01-08_22-50-37-602963170.log for the output of root script default: Check /u01/app/19.0.0/grid/install/root_ol7-19-rac2.localdomain_2021-01-09_00-03-05-829161842.log for the output of root script

You need to check those scripts and identify the failures. That should give you a clue about what you need to do to fix this.

Note. This does not appear to be the same as that other issue. If it were, you would not get as far as installing the GI software. The problem you are having is after that failure point.

Regarding your changes,

Cheers

Tim...

ghost commented 3 years ago

Hi Tim, Thanks for the very detailed and insightful reply. I looked into those logs and saw that some items failed to start. The issue was fixed when I increased the allocated memory back to your recommended values.

Thank you very much!