Oracle 23ai — Applying Grid Infrastructure Patches via GUI(Zero-Downtime)

By -

 In Oracle 23ai, it is possible to apply patches to the Grid software using the gridSetup.sh script through a wizard-based graphical interface. This process can also be performed with zero downtime. In this guide, we aim to apply Release Update 23.6 to Grid Infrastructure version 23.5.

Currently, Grid Infrastructure 23.5 is running:

[grid@OL810 ~]$ sqlplus "/as sysasm"
SQL*Plus: Release 23.0.0.0.0 – for Oracle Cloud and Engineered Systems on Wed Nov 27 12:57:14 2024
Version 23.5.0.24.07
Copyright © 1982, 2024, Oracle.  All rights reserved.
Connected to:
Oracle Database 23ai Enterprise Edition Release 23.0.0.0.0 – for Oracle Cloud and Engineered Systems
Version 23.5.0.24.07
SQL>

To apply the patch, the Grid Infrastructure software version 23.6 must first be installed as software only.

[root@OL810 ~]# /grid/23.6/root.sh
Performing root user operation.
The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /grid/23.6
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
To configure Grid Infrastructure for a Cluster or Grid Infrastructure for a Stand-Alone Server execute the following command as grid user:
/grid/23.6/gridSetup.sh
This command launches the Grid Infrastructure Setup Wizard. The wizard also supports silent operation, and the parameters can be passed through the response file that is available in the

The software was installed without errors. In the next step, we run the gridSetup.sh script again. This time, by selecting Patch Oracle Grid Infrastructure, we apply patch 23.6 to version 23.5:

The final step to apply the patch is to execute the root.sh script:

[root@OL810 ~]# /grid/23.6/root.sh
Performing root user operation.
The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /grid/23.6
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Executing command '/grid/23.6/perl/bin/perl -I/grid/23.6/perl/lib -I/grid/23.6/crs/install /grid/23.6/crs/install/roothas.pl  -dstcrshome /grid/23.6 -prepatch                           '
Using configuration parameter file: /grid/23.6/crs/install/crsconfig_params
The log of current session can be found at:
  /grid/base/crsdata/ol810/crsconfig/hapatch_2024-11-27_12-59-47AM.log
acfsutil info fs: ACFS-03036: no mounted ACFS file systems
2024/11/27 13:00:08 CLSRSC-347: Successfully unlock /grid/23.6
2024/11/27 13:00:08 CLSRSC-671: Pre-patch steps for patching GI home successfully completed.
Executing command '/grid/23.6/perl/bin/perl -I/grid/23.6/perl/lib -I/grid/23.6/crs/install /grid/23.6/crs/install/roothas.pl  -dstcrshome /grid/23.6 -postpatch'
Using configuration parameter file: /grid/23.6/crs/install/crsconfig_params
The log of current session can be found at:
  /grid/base/crsdata/ol810/crsconfig/hapatch_2024-11-27_01-00-09PM.log
2024/11/27 13:00:30 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'
2024/11/27 13:01:44 CLSRSC-672: Post-patch steps for patching GI home successfully completed.

The patch has been successfully applied to the Grid Infrastructure software, and the Oracle Grid Infrastructure version has been upgraded to 23.6:

[grid@OL810 ~]$ sqlplus "/as sysasm"
SQL*Plus: Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems on Wed Nov 27 13:04:06 2024
Version 23.5.0.24.07
Copyright (c) 1982, 2024, Oracle.  All rights reserved.
Connected to:
Oracle Database 23ai Enterprise Edition Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems
Version 23.6.0.24.10
SQL>

Comments

Post a Comment

Popular posts from this blog

Oracle 23ai — Speed up IMPDP Using NOVALIDATE Constraints

By -
  When executing the   IMPDP   command, some operations do not support parallel execution. Creating constraints is one such operation. Oracle must validate the current data in the table before creating a constraint, which requires a full table scan for each validation. This process can be very time-consuming. Consider the following constraints: ALTER TABLE VAHID.MYTB ADD CONSTRAINT CHECK1 CHECK (col3 > 50 ); ALTER TABLE VAHID.MYTB ADD CONSTRAINT CHECK2 CHECK (col9 IN ( 5 , 15 )); We drop the  MYTB  table and recreate it using a dump file: SQL > drop table mytb; Table dropped. W -1 Processing object type TABLE_EXPORT / TABLE / TABLE_DATA W -1 . . imported "VAHID"."MYTB" 19 GB 337830912 rows in 83 seconds using external_table W -1 Processing object type TABLE_EXPORT / TABLE / CONSTRAINT / CONSTRAINT W -1 Completed 2 CONSTRAINT objects in 208 seconds As shown, creating the two constraints ta...
Read more

Staging Tables in Oracle 23ai

By -
  As you may know, using   staging tables   is a common practice in   Data Warehouse   environments, primarily during the data loading process into the   Warehouse Database . Typically, raw data received from   source databases   is first loaded into a temporary area, referred to as   staging tables . After cleansing inconsistent and invalid data and transforming it into a standard format, the cleaned data is stored in the final operational tables. In addition to initial data loading,   staging tables   are also used for updates and are often truncated before reuse. In   Oracle 23ai , a new minor feature has been introduced for this purpose, allowing users to create tables specifically designed as   staging tables . This is achieved by adding the   FOR STAGING   clause to the   CREATE TABLE   statement. Creating Staging Tables Using the   FOR STAGING   clause, staging tables can be created as ...
Read more

Oracle 23ai — Track Table and Partition Scan Access

By -
Image
  In Oracle 23ai, a new view named   [dba|all|user]_table_access_stats   has been introduced, enabling users to view the access history of tables and partitions. This view shows how many times each table or partition has been scanned in each instance and the last time a table was accessed. SQL > create table jadval(id number, name varchar2( 100 ), last_name varchar2( 100 )); Table created. SQL > insert into jadval values ( 1 , 'payan' , 'rafat' ); 1 row created. SQL > select TABLE_NAME, PARTITION_NAME, INSTANCE_ID, READ_COUNT, LAST_ACCESSED_TIME from user_table_access_stats; no rows selected SQL > select * from jadval; ID NAME LAST_NA ---------- ------- ------- 1 payan rafat SQL > select TABLE_NAME, PARTITION_NAME, INSTANCE_ID, READ_COUNT, LAST_ACCESSED_TIME from user_table_access_stats; TABLE_NAME PARTITION_NAME INSTANCE_ID READ_COUNT LAST_ACCESSED_TIME ---------- --------------- ----------- --------...
Read more