Minimum Available Space Requirements for Oracle Standalone Cluster With GIMR Configuration
Redundancy Level
DATA Disk Group
MGMT Disk Group
Oracle Fleet Patching and Provisioning
Total Storage
External
1 GB
28 GB Each node beyond four: 5 GB
1 GB
30 GB
Normal
2 GB
56 GB Each node beyond four: 5 GB
2 GB
60 GB
High/Flex/Extended
3 GB
84 GB Each node beyond four: 5 GB
3 GB
90 GB
a. The DATA disk group stores OCR and voting files, and the MGMT disk group stores GIMR and Oracle Clusterware backup files.
b. Starting with Oracle Grid Infrastructure 19c, configuring GIMR is optional for Oracle Standalone Cluster deployments.
Configuring Operating Systems for Oracle Grid Infrastructure on Linux
cat >>/home/oracle/.bash_profile <<"EOF" # Oracle 19c umask 022 export ORACLE_SID=coco1 export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=$ORACLE_BASE/product/19.0.0/dbhome_1 export PATH=$ORACLE_HOME/bin:$PATH export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib export CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib ifcommand -v rlwrap >/dev/null 2>&1; then alias sqlplus='rlwrap sqlplus' alias rman='rlwrap rman' fi EOF
Completing Preinstallation Tasks Manually
Configuring SSH Manually on All Cluster Nodes
Create SSH Directory and Create SSH Keys On Each Node
Logged in as grid, create the .ssh directory in the grid user's home directory, and set permissions on it to ensure that only the oracle user has read and write permissions:
mkdir ~/.ssh chmod 700 ~/.ssh
Create RSA or DSA key.
/usr/bin/ssh-keygen -t rsa
At the prompts, accept the default location for the key file (press Enter).
Repeat the steps 1 through 2 on each node that you intend to make a member of the cluster, using the DSA key.
Add All Keys to a Common authorized_keys File
To configure SSH, copy all the generated keys on all cluster node members into an authorized keys file that is identical on each node.
On the local node, add the DSA key to the authorized_keys file, then copy the authorized_keys file to the user .ssh directory on a remote node.
Repeat from each node to each other member node in the cluster.
Verifying SSH User Equivalency on Cluster Nodes
On the system where you want to run OUI, log in as the grid user.
If you have configured SSH correctly, then you can now use the ssh or scp commands without being prompted for a password. For example:
~]$ ssh oracle19crac02 date Wed May 10 11:02:23 CST 2023 ~]$ ssh oracle19crac03 date Wed May 10 11:02:27 CST 2023
Repeat from each node to each other member node in the cluster.
If any node prompts for a password, then verify that the ~/.ssh/authorized_keys file on that node contains the correct public keys, and that you have created an Oracle software owner with identical group membership and IDs.
Configuring Storage Device Path Persistence Using Oracle ASMLIB
If you configure disks using Oracle ASMLIB, then you must change the disk discovery string to ORCL:. If the diskstring is set to ORCL:, or is left empty (""), then the installer discovers these disks.
Installing and Configuring Oracle ASMLIB Software
To install and configure the Oracle Automatic Storage Management library driver software manually, perform the following steps:
Depending on your operating system version, download the required Oracle Automatic Storage Management library driver packages and driver:
Run the oracleasm initialization script with the configure option:
~]# /usr/sbin/oracleasm configure -i Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library driver. The following questions will determine whether the driver is loaded on boot and what permissions it will have. The current values will be shown in brackets ('[]'). Hitting <ENTER> without typing an answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: grid Default group to own the driver interface []: asmadmin Start Oracle ASM library driver on boot (y/n) [n]: y Scan for Oracle ASM disks on boot (y/n) [y]: y Writing Oracle ASM library driver configuration: done
Load the oracleasm kernel module:
~]# /usr/sbin/oracleasm init Creating /dev/oracleasm mount point: /dev/oracleasm Loading module "oracleasm": oracleasm Configuring "oracleasm" to use device physical block size Mounting ASMlib driver filesystem: /dev/oracleasm
Configuring Disk Devices to Use Oracle ASMLIB
Use either fdisk or parted to create a single whole-disk partition on the disk devices, only on local node.
fdisk /dev/sdb ...
Mark a disk as an Oracle Automatic Storage Management disk, only on local node:
To make the disk available on the other nodes in the cluster, enter the following command as root on each node:
~]# oracleasm scandisks Reloading disk partitions: done Cleaning any stale ASM disks... Scanning system for ASM disks... Instantiating disk "OCR01" Instantiating disk "OCR02" Instantiating disk "DATA01" Instantiating disk "MGMT01" Instantiating disk "OCR03" Instantiating disk "ARCH01" ~]# oracleasm listdisks ARCH01 DATA01 MGMT01 OCR01 OCR02 OCR03
Configuring Kernel Parameters for Linux
Create or edit the /etc/sysctl.d/97-oracle-database-19c-sysctl.conf file, and add or edit lines similar to:
[INS-06009] SSH performance is detected to be slow, which may impact performance during remote node operations like copying the software and executing prerequisite checks.
INS-41208 None of the available network subnets is marked for use by ASM
在 ASM 私有网络验证时，出现如下错误：
[INS-41208] None of the available network subnets is marked for use by Oracle Automatic Storage Management (ASM)
PRVG-11081 : unable to find the matching networks for the interface "ens256" and the subnet "100.100.100.0" on nodes "oracle19crac03"
Cause: Cluster Verification Utility (CVU) connectivity checking determined that the interface-subnet combination was not found on the indicated nodes.
Action: Ensure that the interface-subnet combination is installed, is online on the indicated nodes, and retry the node connectivity checks.
asmcmd> cd +DATA/COCO/ asmcmd> mkdir PDBSEED asmcmd> mkdir PDB
PRCR-1079
DBCA 创建数据库，出现数据库无法启动，共享内存段（SGA）分配错误
PRCR-1079 : Failed to start resource ora.coco.db
CRS-5017: The resource action "ora.coco.db start" encountered the following error:
ORA-27125: unable to create shared memory segment
查看数据库 alert_<sid>.log 日志文件，详细错误日志如下：
2023-05-24T13:11:59.696916+08:00 Error: ENOSPC while creating shared memory segment of size 6425673728 bytes Check the system shared memory parameters 2023-05-24T13:11:59.697766+08:00 Error: ENOSPC while creating shared memory segment of size 6425673728 bytes Check the system shared memory parameters 2023-05-24T13:11:59.698456+08:00 ********************************************************************** 2023-05-24T13:11:59.698751+08:00 Dump of system resources acquired for SHARED GLOBAL AREA (SGA)
2023-05-24T13:11:59.699297+08:00 Per process system memlock (soft) limit = 7168M 2023-05-24T13:11:59.699599+08:00 Expected per process system memlock (soft) limit to lock instance MAX SHARED GLOBAL AREA (SGA) into memory: 6146M 2023-05-24T13:11:59.700236+08:00 Available system pagesizes: 4K, 2048K 2023-05-24T13:11:59.700836+08:00 Supported system pagesize(s): 2023-05-24T13:11:59.701123+08:00 PAGESIZE AVAILABLE_PAGES EXPECTED_PAGES ALLOCATED_PAGES ERROR(s) 2023-05-24T13:11:59.701447+08:00 4K Configured 9 0 ORA-27125 2023-05-24T13:11:59.701942+08:00 2048K 3071 3073 5 ORA-27125 2023-05-24T13:11:59.702271+08:00 RECOMMENDATION: 2023-05-24T13:11:59.702601+08:00 1. Configure system with expected number of pages for every supported system pagesize prior to the next instance restart operation. 2023-05-24T13:11:59.725346+08:00 ********************************************************************** 2023-05-24T13:11:59.747369+08:00 SGA: Realm creation failed
bin]# ./crsctl start res ora.crsd -init CRS-2672: Attempting to start 'ora.ctssd' on 'oracle19crac02' CRS-2676: Start of 'ora.ctssd' on 'oracle19crac02' succeeded CRS-2672: Attempting to start 'ora.asm' on 'oracle19crac02' CRS-2672: Attempting to start 'ora.crsd' on 'oracle19crac02' CRS-2676: Start of 'ora.asm' on 'oracle19crac02' succeeded CRS-2676: Start of 'ora.crsd' on 'oracle19crac02' succeeded
~]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /soft/34130714 -analyze OPatchauto session is initiated at Tue May 23 23:22:37 2023
System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2023-05-23_11-22-43PM.log.
Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2023-05-23_11-23-02PM.log The idfor this session is QDHA Shared home /u01/app/19.0.0/grid can only be patched in nonrolling mode.
OPATCHAUTO-72030: Execution mode invalid. OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared. OPATCHAUTO-72030: Execute in non-rolling mode. OPatchAuto failed.
OPatchauto session completed at Tue May 23 23:23:32 2023 Time taken to complete the session 0 minute, 55 seconds
opatchauto failed with error code 42
found errors in System initialization log file /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2023-05-23_11-17-19PM.log.
Verification of shared storage accessibility was unsuccessful on all the specified nodes. NODE_STATUS::oracle19crac01:EFAIL The result of cluvfy command contain EFAIL NODE_STATUS::oracle19crac01:EFAIL 2023-05-23 23:17:39,697 SEVERE [1] com.oracle.glcm.patch.auto.db.integration.model.productsupport.topology.TopologyCreator - Stacktrace :: oracle.dbsysmodel.driver.sdk.prod uctdriver.ProductDriverException: Unable to determine if "/u01/app/19.0.0/grid" is a shared oracle home. Failed: Verifying '/tmp/' ...FAILED (PRVG-1901)
Verification of shared storage accessibility was unsuccessful on all the specified nodes. NODE_STATUS::oracle19crac01:EFAIL The result of cluvfy command contain EFAIL NODE_STATUS::oracle19crac01:EFAIL
Workaround
Since 19c(19.3) is already released a while ago, It does not contain Pre-req checks specific to OL/RHEL 8.
