Some useful DBA stuff...!
The versions in the table below represent the latest certified and available VM software for updating Exadata and Grid Infrastructure/Database software on systems already provisioned. Customers may update systems already provisioned to the latest certified version as desired. Note the following:
Exadata Database Service on Dedicated Infrastructure (ExaDB-D)
ExaOL8X - 25.1.8.0.0.250828
ExaOL8X - 24.1.14.0.0.250706
23ai - 23.9.0.25.07 5
19c - 19.28.0.0.250715
Exadata Database Service on Cloud@Customer (ExaDB-C@C / Gen2) 1
ExaOL8X - 25.1.8.0.0.250805
ExaOL8X - 24.1.15.0.0.250805
ExaOL7X - 23.1.27.0.0.250706
19c - 19.28.0.0.250715 2
Notes:
1. Latest certified versions for Cloud at Customer are shown in this table when they are released and ready to be staged to customer systems. Staging to customer systems so that a new version is available to be applied may take additional time. If the latest certified version shown in this table is not yet available on your system, but is required for immediate use, please open a service request.
2. To update Gen 1 Exadata Cloud at Customer systems to Database and Grid Infrastructure 19c, refer to the following documents:
3. ExaOL8X / ExaOL7X
4. Refer to Document 2997504.1 for information about Database releases older than what is shown in the table.
5. Virtual Machine OS requires an ExaOL8X Exadata version (e.g., Exadata 23.1) before updating Grid Infrastructure and Database to 23ai.
6. The table below indicates the planned date of the final Maintenance Release for each Exadata Release for Virtual Machine OS Update.
VM OS update from an ExaOL7X release to an ExaOL8X release performs an in-place Oracle Linux upgrade from OL7 to OL8, which is considered a major operating system upgrade. While planning a VM OS update from an ExaOL7X release to an ExaOL8X release, please note the following:
The preferred approach for updating the Exadata image version in the VM is to use the Oracle Cloud Console, which always performs a rolling update of all nodes with no delay between nodes. However, there are circumstances where the command line patchmgr-based approach described in Document 2936828.1 is needed, such as the following:
Available Exadata software versions and YUM repository URLs to use for update are shown below. Refer to Oracle Cloud Infrastructure Documentation for details about Region Identifier (region_identifier) that is used in the URL.
Available Exadata software versions for update:
Customers who do not have My Oracle Support patch download privilege may obtain the Exadata patchmgr update utility and recent Exadata System Software releases using the Exadata Cloud@Customer Gen 2 utility exadata_updates.sh. See Document 2730739.1 for details.
Update instructions available in Document 2391164.1.
For information about Cloud Tools RPM (dbaastools_exa RPM) releases refer to Document 2404336.1.
1.1 Carry Out Performance Evaluation in a Test Environment When upgrading your Oracle E-Business Suite database, it is essential to ensure...
No comments:
Post a Comment