Oracle 19c — Grid Infrastructure Upgrade in Dry-Run Mode

By -

 Upgrading the Grid Infrastructure to a higher version may fail due to missing prerequisites. To address this, Oracle introduced a new feature in version 19c that allows the upgrade process to be executed in Dry-Run mode before the actual upgrade. This helps identify and resolve potential errors in advance.

Below is how this operation can be performed.

[grid@RAC1 ~]$ cd /grid19c/home/

[grid@RAC1 home]$ ./gridSetup.sh -dryRunForUpgrade

Launching Oracle Grid Infrastructure Setup Wizard…

At the end, the rootupgrade.sh script is executed only on the local node and by the root user:

[root@RAC1 ~]# /grid19c/home/rootupgrade.sh

Performing root user operation.

The following environment variables are set as:

    ORACLE_OWNER= grid

    ORACLE_HOME=  /grid19c/home

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.

Relinking oracle with rac_on option

Performing Dry run of the Grid Infrastructure upgrade.

Using configuration parameter file: /grid19c/home/crs/install/crsconfig_params

The log of current session can be found at:

  /grid18c/base/crsdata/rac1/crsconfig/rootcrs_rac1_2020-09-08_02-20-47PM.log

2020/09/08 14:21:12 CLSRSC-464: Starting retrieval of the cluster configuration data

2020/09/08 14:21:23 CLSRSC-729: Checking whether CRS entities are ready for upgrade, cluster upgrade will not be attempted now. This operation may take a few minutes.

2020/09/08 14:23:19 CLSRSC-693: CRS entities validation completed successfully.

Comments

Post a Comment

Popular posts from this blog

Oracle 21c Enhancements for TTS Export/Import

By -
  In Oracle version 21c, new features have been introduced for transportable tablespace (TTS) export/import. This article explores these capabilities in detail. Improvement 1: Parallel Execution of TTS Export/Import In Oracle 19c, TTS export/import operations could not be executed in parallel, as demonstrated by the following: Connected to: Oracle Database 19c Enterprise Edition Release 19.0 .0 .0 .0 – Production ORA-39002: invalid operation ORA-39047: Jobs of type TRANSPORTABLE cannot use multiple execution streams. Oracle addressed this limitation in version 21c, enabling parallel execution for TTS export/import: [oracle@oLinux7 ~]$ expdp directory=drm dumpfile=TTS_DUMP%U.dmp transport_tablespaces=tbs1,tbs2 transport_full_check= y parallel= 2 Export: Release 21.0 . 0 . 0 . 0 – Production on Tue Oct 12 06 : 48 : 54 2021 Version 21.3 . 0 . 0 . 0 Processing object type TRANSPORTABLE_EXPORT/STATISTICS/TABLE_STATISTICS Processing object type TRANSPORTABLE_EXPOR...
Read more

Automatic Service Failback to Preferred Instance in Oracle RAC 19c

By -
  As you know, in a RAC environment when creating a service, you can define   preferred instances   and   available instances . In this case, the service will by default run on the preferred instance. If for any reason the preferred instance fails, or the entire node becomes unavailable, the service will be moved to the available instance. Even after restarting the preferred instance, the service will not automatically fail back; it will continue running on the available instance. To move it back to the preferred instance, you need to manually perform a  relocate  operation. Example: In this example, we create a service named  mysrv  in Oracle 11g: [ grid@node1 ~ ]$ crsctl query crs releaseversion Oracle High Availability Services release version on the local node is [ 11.2 .0 .4 .0 ] [ oracle@node1 ~ ]$ srvctl add service -d mydb -s mysrv -r instance1 -a instance2 After creating the service, start it. You will see that the service is runnin...
Read more

SQL Diagnostic Report(23ai, 19.28)

By -
Image
Before Oracle Database 23ai, the awrsqrpt.sql script was commonly used to analyze the evolution of a SQL statement’s execution plan, plan statistics, CPU usage, I/O, and elapsed time over a specified period. However, this approach had two main limitations: It required specifying two specific AWR snapshots. The information provided in its report was relatively limited. Sample Output of awrsqrpt.sql: Press enter or click to view image in full size With the introduction of Oracle Database 23ai, a new function, REPORT_SQL, was added to the  DBMS_SQLDIAG  package. This function generates a comprehensive HTML diagnostic report for a specified SQL statement, providing deeper performance insights. This functionality is also backported to Oracle Database 19.28. The REPORT_SQL function provides a graphical report in HTML format, allowing for the analysis of: Execution plan history Cursor sharing information Optimizer statistics history Index details And more REPORT_SQL Function: SQL ...
Read more