While it is generally recommended for components to stay in step with the recommended minimum release, you can choose to update different components at different times. For example, you could update RDMA Network Fabric switches at a later time than Exadata storage servers and Exadata database servers. However, you must check My Oracle Support Doc ID 888828.1 for any dependencies.
It is not mandatory to apply each and every Oracle Exadata System Software update that comes out. For example, you can skip two or three releases and update directly to a newer release. Oracle recommends that you update database servers twice a year.
viceversa pro 2.5 server keygen 12
Exadata Database Machine software update tool that updates all software (Oracle Linux, Oracle Exadata System Software, firmware) on Exadata Database Machine database servers, storage servers, or RDMA Network Fabric switches. For example, patchmgr updates Exadata Database Machine storage servers and database servers to Oracle Exadata System Software version 12.2.1.1.0, or InfiniBand Network Fabric switches to version 2.2.4-3.
The patchmgr update utility manages the update orchestration in a rolling or non-rolling manner for Exadata Database Machine infrastructure components (storage servers, database servers, and RDMA Network Fabric switches).
Typically, planned software updates require that the component be restarted after the update. For example, an Exadata database server must be restarted after applying an Exadata software release to update the system firmware and to make active a new Oracle Linux kernel. Similarly, an Oracle database instance must be stopped and restarted to apply a software update to the database home.
When performing storage server updates in a rolling manner with the databases remaining online, it is highly recommended to configure Oracle ASM disk groups with high redundancy. High redundancy disk groups can tolerate the failure of a disk in another storage server during rolling updates.
During rolling, or online, storage server updates, the disks for the storage server being updated are taken offline on one storage server by patchmgr while it is updated. After the update completes the disks are resynchronized by Oracle ASM, and then patchmgr starts to update the next storage server.
While disks are offline the disk group has reduced redundancy. A normal redundancy disk group with reduced redundancy during a rolling update may dismount and have data loss if a disk fails in another storage server.
Oracle ASM disk group redundancy is typically set during initial system configuration. Therefore, consider how you plan to perform storage server updates, rolling or non-rolling, prior to system configuration.
When performing Exadata database server, Oracle Grid Infrastructure, or Oracle Database software updates in a rolling manner on one database server at a time while database services remain running on the other servers in the cluster, the database services must be stopped on the Exadata database server being updated.
Oracle EXAchk is updated regularly to contain new features, fixes, best practice health checks, and version recommendations. Patchmgr for database servers is updated regularly to contain new features, fixes, and workarounds for known database server update issues. OPatch is updated regularly to contain new features and fixes.
It is supported to manually customize database servers, but note that customizing the operating system by adding or updating packages may require additional actions when applying a future Oracle Exadata System Software update with patchmgr (for example, removing customization prior to updating Exadata Database Machine servers and reapplying the customization after the update completes) because the additional software may add new dependencies which are not provided by a future Oracle Exadata System Software update. It is recommended to minimize database server customization. See the topic Updating Exadata Database Machine Database Servers for additional details.
Update a subset of Exadata Database Machine storage servers to a higher version of the Oracle Exadata System Software while the remaining storage servers remain at the earlier Oracle Exadata System Software version.
Update Exadata Database Machine storage servers to a higher version of the Oracle Exadata System Software while RDMA Network Fabric switches remain at the earlier Oracle Exadata System Software version.
Update RDMA Network Fabric switches to a higher version of the Oracle Exadata System Software while Exadata Database Machine storage servers remain at the earlier Oracle Exadata System Software version.
Update Exadata Database Machine storage servers to a higher version of the Oracle Exadata System Software while Oracle Grid Infrastructure or Oracle Database software remains at an earlier release and update level.
A specific Oracle Database release requires a minimum Oracle Exadata System Software release to fully support Exadata Database Machine features. For example, Oracle Database 12c Release 2 (12.2) requires Oracle Exadata System Software release 12.2.1.1.0 or higher on storage servers to support all Exadata Database Machine offload features.
Features supplied with a new Oracle Exadata System Software release may require a minimum Oracle Grid Infrastructure or Oracle Database software release or release update. For example, the Exadata Database Machine feature Smart Scan Offload for Compressed Index Scan requires Oracle Database 12.2 and Oracle Exadata System Software 12.2 on storage servers.
When updating a system with Oracle Advanced Cluster File System (Oracle ACFS) configured, the Oracle Grid Infrastructure home must contain the fix for bug 22810422 before updating the database server (non-Oracle VM or Oracle VM) to Oracle Exadata System Software release 12.2.
The Exadata version installed on an Exadata storage server or an Exadata database server is determined with the imageinfo command. The image version of an Exadata release consists of three components. For example, if the command imageinfo -ver returns 12.1.2.1.1.150316.2, then:
Patchmgr manages the update orchestration in a rolling or non-rolling manner for storage servers. When using the -rolling option, Oracle recommends that you use Oracle ASM high redundancy disk groups to tolerate the failure of a disk in another storage server during the update.
You can run patchmgr (which is packaged in dbserver.patch.zip) using sudo to perform any of patchmgr's functionalities, such as patching cells, patching RDMA Network Fabric switches, or orchestrating dbnodeupdate.sh execution.
Database servers contain all software necessary to run Oracle Database and are configured to run Oracle Database optimally. However, it may be necessary to manually install additional, site-specific software, such as monitoring agents or backup agents. It is supported to manually customize database servers, but note that customizing the operating system by adding or updating packages may require additional actions when applying a future Oracle Exadata System Software update with patchmgr.
Storage server or RDMA Network Fabric switch configuration or installed software may not be altered manually (update without using patchmgr) in any way unless Exadata Database Machine documentation contains steps to perform the desired change.
By default, the appropriate patchmgr distribution is included with the relevant server or switch update. However, it is recommended to always use the latest patchmgr from My Oracle Support when updating Exadata Database Machine servers or switches. The patchmgr utility is updated frequently to address known issues and best practices, and to support new hardware. See My Oracle Support document 888828.1.
Patchmgr runs on the "driving system", which is an Exadata Database Machine database server or a non-Exadata Database Machine system running Oracle Linux. This allows patchmgr to run from a central server to update multiple Exadata Database Machine systems. If patchmgr runs from an Exadata Database Machine database server, then that database server cannot be in the group file supplied to patchmgr.
The user running patchmgr must have root-level SSH equivalence configured to the servers or switches that patchmgr will update. The SSH equivalence must be bi-directional. That is, the user running patchmgr must be able to use SSH without a password to access the target servers or switches as the root user, and the root user on target servers or switches must be able to use SSH without a password to access the driving system as the user running patchmgr.
Patchmgr is run on the "driving system", which is an Exadata Database Machine database server or a non-Exadata Database Machine system running Oracle Linux. This allows patchmgr to run from a central server to update multiple Exadata Database Machine systems
Patchmgr may be run as the root user or as a non-root user. The user running patchmgr must have root-level SSH equivalence configured to the servers or switches that patchmgr will update. To run patchmgr as a non-root user, the -log_dir option must be used.
The following commands update storage servers on three Exadata Database Machine systems simultaneously from the same software directory; one update using a rolling update, the others updates are non-rolling.
Patchmgr is run on the "driving system", which is an Exadata Database Machine database server or a non-Exadata Database Machine system running Oracle Linux. This allows patchmgr to run from a central server to update multiple Exadata Database Machine systems. If patchmgr is run from an Exadata Database Machine database server, then that database server cannot be in the file that lists the servers to patch.
Patchmgr is run on the "driving system", which is an Exadata Database Machine database server or a non-Exadata Database Machine system running Oracle Linux. This allows patchmgr to run from a central server to update multiple Exadata Database Machine systems.
Note: Commencing with the August 2022 patchmgr release, patchmgr performs an additional series of checks on the RoCE Network Fabric. The checks occur immediately before any firmware upgrade and also during prerequisite checking using the --roceswitch-precheck option. These checks mitigate the risks of failure associated with unexpected problems in the RoCE Network Fabric. For example, if one of the RoCE Network Fabric ports on a storage server is down, the storage server would become unavailable if the switch connected to the only operational port is taken offline for an upgrade. If any check fails, patchmgr reports the problem and ends immediately. In this case, you must correct the problem with the RoCE Network Fabric before you can perform the upgrade. 2ff7e9595c
Comments