Generate patches file

Note:

Generate patches file is required only if the source environment is ExaDB-C@C.

Running this step requires access to a database server in the source ExaDB-C@C VM cluster.

1. Transfer the ecmasshutility binary from the client machine to any database server of the source VM cluster.

   For example:

   scp /home/opc/ecmasshutility opc@[ip address of db server ]:/tmp

2. Log in to the source VM Cluster database server where the utility is copied.
3. Grant the required permissions on the /tmp/ecmasshutility directory to the oracle user.
4. Switch to the oracle user and navigate to the directory where the utility was copied (for example, /tmp).

The ecmasshutility get_patches supports the following options:

Syntax

ecmasshutility get_patches [-p <patchesFileName>]

Table 2-10 ecmasshutility get_patches Commands

Command	Description
-p, --patchesFileName	Sets the patches file name.
-h, --help	Displays help information about the command and its options.
-V, --version	Displays the version of the utility.

For example, to generate the patches file: ./ecmasshutility get_patches.

Note:

• By default, the patches file is created with the name patches_file. This file contains details of the one-off patches and Release Updates (RU) applied to each ORACLE_HOME in the cluster.

  For example:

  • /u02/app/oracle/product/23.0.0.0/dbhome_1=35221462,37537949,37701424,37701421
  • /u02/app/oracle/product/19.0.0.0/dbhome_2=34672698,34697081,37499406,37542054,37654975,37642901
• If the patches file is generated using the steps above, ensure that it is copied to the client machine in the respective VM cluster input directory. This is required for the creation of DB Home software images, DB Homes, and database migration operations.
• Generation of the patches file is required only when the source is ExaDB-C@C and for the following commands:
  • migrate_infra
  • migrate_vmcluster
  • create_dbhomeimage
  • migrate_dbhome
  • migrate_database dgassociation
  • migrate_database switchover
  • migrate_database failover