oraclebase / vagrant

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

run error on node1 #19

Closed kobe24shou closed 3 years ago

kobe24shou commented 3 years ago

default: Running transaction default: Preparing : 1/1 default: default: Running scriptlet: cvuqdisk-1.0.10-1.x86_64 1/1 default: default: Using default group oinstall to install package default: Installing : cvuqdisk-1.0.10-1.x86_64 1/1 default: default: Running scriptlet: cvuqdisk-1.0.10-1.x86_64 1/1 default: default: Verifying : cvuqdisk-1.0.10-1.x86_64 1/1 default: default: default: Installed: default: cvuqdisk-1.0.10-1.x86_64 default: Complete! default: ** default: Do grid software-only installation. Fri Jan 15 03:23:26 UTC 2021 default: ** default: Preparing the home to patch... default: Applying the patch /u01/software/31720429/31750108... default: OPatch command failed while applying the patch. For details look at the logs from /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/. default: ** default: Run grid root scripts. Fri Jan 15 03:23:33 UTC 2021 default: ** default: sh: /u01/app/oraInventory/orainstRoot.sh: No such file or directory default: sh: /u01/app/oraInventory/orainstRoot.sh: No such file or directory default: Check /u01/app/19.0.0/grid/install/root_ol8-19-rac1_2021-01-15_03-23-33-682121533.log for the output of root script default: sh: /u01/app/19.0.0/grid/root.sh: No such file or directory default: ** default: Do grid configuration. Fri Jan 15 03:23:34 UTC 2021 default: ** default: default: ERROR: The home is not clean. This home cannot be used since there was a failed OPatch execution in this home. Use a different home to proceed. default: ** default: Create additional diskgroups. Fri Jan 15 03:23:34 UTC 2021 default: ** default: /vagrant/scripts/oracle_grid_software_config.sh: line 48: /u01/app/19.0.0/grid/bin/sqlplus: Permission denied default: ** default: Check cluster configuration. Fri Jan 15 03:23:34 UTC 2021 default: ** default: /vagrant/scripts/oracle_grid_software_config.sh: line 63: /u01/app/19.0.0/grid/bin/crsctl: No such file or directory default: ** default: Unzip database software. Fri Jan 15 03:23:34 UTC 2021 default: ** default: ** default: Do database software-only installation. Fri Jan 15 03:25:01 UTC 2021 default: ** default: Preparing the home to patch... default: Applying the patch /u01/software/31720429/31750108... default: OPatch command failed while applying the patch. For details look at the logs from /u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/opatchauto/. default: ** default: Run DB root scripts. Fri Jan 15 03:25:08 UTC 2021 default: ** default: Check /u01/app/oracle/product/19.0.0/dbhome_1/install/root_ol8-19-rac1_2021-01-15_03-25-08-275219312.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: ** default: OJVM Patch for DB Software. Fri Jan 15 03:25:08 UTC 2021 default: ** default: ** default: Patch Oracle Grid Infrastructure Software. Fri Jan 15 03:25:08 UTC 2021 default: HOSTNAME=localhost.localdomain default: ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1 default: ** default: ** default: Unzip software. Fri Jan 15 03:25:08 UTC 2021 default: ** default: Can't call method "uid" on an undefined value at /u01/app/oracle/product/19.0.0/dbhome_1/OPatch/auto/database/bin/module/DBUtilServices.pm line 28. default: ** default: Patch Oracle Grid Infrastructure Software. Fri Jan 15 03:25:09 UTC 2021 default: HOSTNAME=ol8-19-rac2 default: ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1 default: ** default: ** default: Unzip software. Fri Jan 15 03:25:09 UTC 2021 default: ** default: /vagrant_scripts/oracle_software_patch.sh: line 26: opatchauto: command not found default: ** default: Create database. Fri Jan 15 03:27:42 UTC 2021 default: ** default: [FATAL] java.lang.NullPointerException default: ** default: Save state of PDB to enable auto-start. Fri Jan 15 03:27:44 UTC 2021 default: ** default: /vagrant/scripts/oracle_create_database.sh: line 32: /u01/app/oracle/product/19.0.0/dbhome_1/bin/sqlplus: Permission denied default: ** default: Check cluster configuration. Fri Jan 15 03:27:44 UTC 2021 default: ** default: ** default: Output from crsctl stat res -t Fri Jan 15 03:27:44 UTC 2021 default: ** default: /vagrant/scripts/oracle_create_database.sh: line 44: /u01/app/19.0.0/grid/bin/crsctl: No such file or directory default: ** default: Output from srvctl config database -d cdbrac Fri Jan 15 03:27:44 UTC 2021 default: ** default: /u01/app/oracle/product/19.0.0/dbhome_1/bin/srvctl: line 259: /u01/app/oracle/product/19.0.0/dbhome_1/srvm/admin/getcrshome: No such file or directory default: PRCD-1027 : Failed to retrieve database cdbrac default: PRCR-1070 : Failed to check if resource ora.cdbrac.db is registered default: CRS-0184 : Cannot communicate with the CRS daemon. default: ** default: Output from srvctl status database -d cdbrac Fri Jan 15 03:27:44 UTC 2021 default: ** default: /u01/app/oracle/product/19.0.0/dbhome_1/bin/srvctl: line 259: /u01/app/oracle/product/19.0.0/dbhome_1/srvm/admin/getcrshome: No such file or directory default: PRCD-1027 : Failed to retrieve database cdbrac default: PRCR-1070 : Failed to check if resource ora.cdbrac.db is registered default: CRS-0184 : Cannot communicate with the CRS daemon. default: ** default: Output from v$active_instances Fri Jan 15 03:27:44 UTC 2021 default: ** default: /vagrant/scripts/oracle_create_database.sh: line 59: /u01/app/oracle/product/19.0.0/dbhome_1/bin/sqlplus: Permission denied default: ** default: Setup End. Fri Jan 15 03:27:44 UTC 2021 default: **

oraclebase commented 3 years ago

If you read the output from the top down, the first problem you see is this.

default: ** default: Do grid software-only installation. Fri Jan 15 03:23:26 UTC 2021 default: ** default: Preparing the home to patch... default: Applying the patch /u01/software/31720429/31750108... default: OPatch command failed while applying the patch. For details look at the logs from /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/.

The patch of the software failed, so everything beyond this point is pointless. It's not going to work unless the patch is successful. Do as the error message says and check the logs for what caused the failure. Correct whatever is causing it and try again.

kobe24shou commented 3 years ago

thanks you,is works but I have a question, why there is no grid user?

default: Database is administrator managed default: ** default: Output from srvctl status database -d cdbrac Sat Jan 16 03:59:46 UTC 2021 default: ** default: Instance cdbrac1 is running on node ol8-19-rac1 default: Instance cdbrac2 is running on node ol8-19-rac2 default: ** default: Output from v$active_instances Sat Jan 16 03:59:47 UTC 2021 default: ** default: default: SQL*Plus: Release 19.0.0.0.0 - Production on Sat Jan 16 03:59:47 2021 default: Version 19.9.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.9.0.0.0 default: default: SQL> default: default: INST_NAME default: -------------------------------------------------------------------------------- default: ol8-19-rac1:cdbrac1 default: ol8-19-rac2:cdbrac2 default: default: SQL> default: Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production default: Version 19.9.0.0.0 default: ** default: Setup End. Sat Jan 16 03:59:48 UTC 2021 default: **

[oracle@ol8-19-rac1 ~]$ ps -ef | grep asmpmon oracle 52986 1 0 02:57 ? 00:00:00 asmpmon+ASM1 oracle 159247 156332 0 04:51 pts/0 00:00:00 grep --color=auto asmpmon [oracle@ol8-19-rac1 ~]$ [oracle@ol8-19-rac1 ~]$ su - grid su: user grid does not exist [oracle@ol8-19-rac1 ~]$ [oracle@ol8-19-rac1 ~]$

oraclebase commented 3 years ago

The main purpose of the grid user is to provide separation of duties between the people who manage the grid infrastructure and ASM, and the people who manage the database.

I have NEVER worked in a company that has this separation. It is always the DBAs that look after both aspects. As a result, separating the GI and DB into different users does not make sense. In recent years Oracle have started to assume you will make this separation no matter what, even adding it as a warning into the installers, but that in my opinion is a mistake.

I build this using a single user because it is less hassle. Simple as that. :)

Am I OK to close this issue now?

kobe24shou commented 3 years ago

great! tanks a lot