dbpatchmdg apply_async
Note:
This command is deprecated as of release 18.3.6 in September 2018. It is replaced by the dbaascli patch db apply command. You should discontinue using this deprecated command as it will be removed in a future release.
apply_async option of the dbpatchmdg utility is used to apply a patch to the Oracle Database home on an Oracle Database Classic Cloud Service database deployment hosting an Oracle Data Guard configuration.
dbpatchmdg -apply_async patch_id [-sshkey=/root/sshkey] [-txn_fl=/var/opt/oracle/log/dbpatchmdg/file_name] [-exclude_node=ip address] [-no_switchover]
The apply_async option of the dbpatchmdg utility applies the patch on all nodes in the Oracle Data Guard configuration, one after another. The node hosting the standby database is patched first. A switchover operation is performed after patching is complete on the standby and then the patch is applied to the node hosting the new standby.
Options of dbpatchmdg apply_async are as follows.
| Option | Description |
|---|---|
|
|
The ID of the patch to be applied. |
|
|
The SSH key. Provide this if the SSH key has changed. |
|
|
The file that the master transaction record will be written to. |
|
|
The IP address of a node that should be excluded from patching. If you want to specify this option, you must patch the standby database before patching the primary database. |
|
|
Indicates that no switchover should take place during patching. With this option, the primary database will incur downtime. If you want to specify this option, you must patch the standby database before patching the primary database. |