Merge pull request #3157 from oracle-devrel/exacc-update-260630

exacc-update-260630

Author: michalvitek-cloud

data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/README.md

@@ -4,19 +4,53 @@ Exadata Database Service on Cloud@Customer infrastructure brings Oracle's indust
 
 <img src="./../images/exadb-infra.png" alt="Infrastructure">
 
+## ECPU metric
+
+The ExaDB-C@C X11M adopts ECPUs as the standard billing metric for the Database Service. ECPU replace the OCPU metric that has been used so far and will be the only metric on ExaDB-C@C X11M.
+
+ECPU = Elastic Compute Units
+
+ECPUs are an abstract measure of compute resources, dynamically allocated from a pool of compute and storage servers. 
+
+By introducing ECPU’s, Oracle is providing a durable pricing metric which is not tied to the exact make, model, or clock speed of the underlying processor. This avoids the possibility of complex billing metric in the future (for example, as new hardware architectures are introduced).
+
+ECPU-based databases provide the same user-experience as OCPU-based databases, and you may convert existing OCPU databases to ECPU databases without disruption or downtime.
+
+ECPUs provide similar or better price-performance than OCPUs because
+
+- An OCPU is the equivalent of a physical core of a processor (CPU). A billing based on OCPUs binds the price to the make, model or clock speed of the underlying CPU. But CPU capacities increase with every new release, rendering a correct price to performance metric relation too complex.
+- An ECPU is based on the number of cores that are elastically allocated per hour to the VM Cluster from a pool of Exadata database servers and storage servers. This metric is independent of the underlying physical hardware, making it the basis for billing in the Cloud for the long-term future.
 
 # Useful Links
 
 - [Main Oracle Product Page](https://www.oracle.com/uk/engineered-systems/exadata/cloud-at-customer/)
 
-- [Oracle Exadata Database Service on Cloud@Customer X10M datasheet](https://www.oracle.com/a/ocom/docs/engineered-systems/exadata/exadb-cc-x10m-ds.pdf)
+- [Oracle Exadata Database Service on Cloud@Customer X11M datasheet](https://www.oracle.com/a/ocom/docs/engineered-systems/exadata/exadb-cc-x11m-ds.pdf)
 
 - [Documentation Home](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/)
 
 - [Oracle Exadata Configuration Assistant (OECA)](https://www.oracle.com/database/technologies/oeca-download.html)
 
 - [Oracle EMCC extracts sizing script and documentaion](assets/Oracle_EMCC_sizing_extracts.zip)
 
+- [ExaDB-C@C Data Collection for sizing](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/data-collection)
+
+- [ExaDB-C@C Configuration Collection](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-configuration-collection)
+
+- [ExaDB-C@C Health Check](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-healthcheck)
+
+- [ExaDB-C@C related list of MOS notes](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-mos-note-list)
+
+- [ExaDB-C@C Supported Database Versions](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-supported-db-versions)
+
+- [ExaDB-C@C VM Cluster scaling](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/vm-cluster-scaling)
+
+- [ExaDB-C@C Single Node VM Cluster](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/single-node-vm-cluster)
+
+- [VM serial consol access](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/vm-serial-consol-access)
+
+- [VM serial consol history and Cloud Shell integration](https://github.com/oracle-devrel/technology-engineering/tree/main/data-platform/database-cloud-at-customer/exadata-cloud-at-customer/vm-serial-consol-history-and-cloud-shell-integration)
+
 ## Useful Documentation
 - [Managing VM Clusters](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/ecccm/ecc-manage-vm-clusters.html)
 
@@ -42,7 +76,7 @@ Exadata Database Service on Cloud@Customer infrastructure brings Oracle's indust
 
 - [OCI Ops Insights - Cloud native support for Exadata Cloud@Customer Databases)](https://blogs.oracle.com/observability/post/oci-ops-insights-cloud-native-support-for-exadata-cloudcustomer-databases)
 
-Reviewed: 06/24/26
+Reviewed: 06/29/26
 
 # License
 

data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-healthcheck/healthcheck-awr-dump/README.md

@@ -224,5 +224,3 @@ Copyright (c) 2026 Oracle and/or its affiliates.
 Licensed under the Universal Permissive License (UPL), Version 1.0.
 
 See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details. 
-
-Reviewed 30/10/2024

data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-mos-note-list/README.md

@@ -2,11 +2,7 @@
 
 ## Collecting all ExaDB-C@C relevant My Oracle Support (MOS) notes
 
-To provide an easily accessible repository pointing to MOS notes and keeping this repository up-to-date.
-
-After initial collection review and update as necessary or at least once per month. 
-
-Anyone working with ExaDB-C@C service.
+We are providing an easily accessible repository pointing to MOS notes related to the ExaDB-C@C service. Please note that that list is not comprehensive you should always check MOS as well. 
 
 The ExaDB-C@C Specialist Team is updating the list manually and refreshing it as necessary. 
 
@@ -44,7 +40,7 @@ The ExaDB-C@C Specialist Team is updating the list manually and refreshing it as
 
 - [2940064.1](https://support.oracle.com/epmos/faces/DocumentDisplay?id=2940064.1) - (ODyS) Oracle Dynamic Scaling on Kubernetes: Setting up Dynamic Scaling on Kubernetes
 
-Reviewed: 06/11/26
+Reviewed: 06/28/26
 
 # License
 

data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/exacc-supported-db-versions/README.md

@@ -0,0 +1,46 @@
+# Exadata Cloud@Customer Supported Database versions
+
+Currently supported versions:
+
+- Oracle AI Database 26ai
+- Oracle Database 23ai
+- Oracle Database 19c (19.x)
+- Oracle Database 12c Release 2 (12.2.0.1) (requires a valid Upgrade Support contract)
+- Oracle Database 12c Release 1 (12.1.0.2) (requires a valid Upgrade Support contract)
+- Oracle Database 11g Release 2 (11.2.0.4) (requires a valid Upgrade Support contract)
+
+## Support for legacy Database releases
+
+**According to the current status, from the 31st of December, 2026, the cloud automation support for ALL Legacy Database Releases will be suspended. This applies for all 11.2.04, 12.1.0.2 or 12.2.0.1 Databases.** 
+
+18c version is already completely unsupported.
+
+Please note, that currently for creation and operating versions below 19c you need to have a valid Upgrade Support contract (formerly Market Driven Support) and an approval from Product Management. We are encouraging everyone to engage in a discussion as early as possible to upgrade these Databases. 
+
+For guidance please refer to the MOS notes linked below and for the Legacy Support Einstein note, which is getting updated regularly. As of 31st of December, 2026 it won't be possible to create a new Database environment with these versions using the cloud tooling.
+
+If we were running legacy versions without upgrade support in 2025 or keep running those in 2026, dbaascli is the only tool, that can be used to manage those environments. Furthermore, there is no guarantee, that future upgrades of the underlying infrastructure are not introducing unexpected behaviors for these Database environments after 31st of December, 2026. There is no official published end date when existing legacy DBs will stop working.
+
+Recent information indicates that in CY27, the Exadata storage server software will be upgraded to a version that is incompatible with any pre-19c Oracle Database release. The upgraded storage software will no longer include compatibility code pre-19c database behaviors. As a result, key Exadata “smart” features (for example, Smart Scan, Storage Indexes, and Columnar Cache) will not operate with pre-19c databases. In that scenario, the storage servers would fall back to block mode, which could lead to a significant performance degradation.
+
+We don’t yet have confirmed dates, but this is expected to occur at some point during CY27 as part of the quarterly infrastructure maintenance cycle. Customers will be able to defer the update by up to 180 days from their previous maintenance window.
+
+# Useful Links
+
+- [Introducing Oracle AI Database 26ai](https://blogs.oracle.com/database/oracle-announces-oracle-ai-database-26ai)
+
+- [Oracle Exadata Database Service on Cloud@Customer Service Description](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/ecccm/ecc-system-config-options.html#GUID-D35869C4-7F3F-423A-A498-1E74A4BD5F0C)
+
+- [Release Schedule of Current Database Releases (Doc ID 742060.1) MOS note](https://support.oracle.com/epmos/faces/DocContentDisplay?id=742060.1)
+
+- [Patching Guidelines for 18c and lower Database versions on ExaDB-C@C (Doc ID 2997504.1) MOS note](https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=461464200650747&id=2997504.1&_adf.ctrl-state=cpak90hw7_252)
+
+Reviewed: 06/29/26
+
+# License
+
+Copyright (c) 2026 Oracle and/or its affiliates.
+
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+
+See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.

data-platform/database-cloud-at-customer/exadata-cloud-at-customer/exacc-infra/single-node-vm-cluster/README.md

@@ -1,8 +1,8 @@
 # Exadata Cloud@Customer Single Node VM Cluster
 
-With this enhancement, you can deploy and run multiple single-instance databases in a single-node cluster without RAC licenses being required.
+It is possible to deploy and run multiple single-instance databases in a single-node cluster without RAC licenses being required.
 
-Please note. This functionality should only be used on non-production environments, where under BYOL licensing, RAC licenses are not available.
+Please note the following. This functionality should only be used on non-production environments, where under BYOL licensing, RAC licenses are not available.
 
 The lack of RAC licenses means that it is impossible to easily instantiate the DB instance on another DB Server in the Exadata Cloud@Customer infrastructure. This means that during maintenance, there will ALWAYS be an outage of the DB service unless there is a possibility to switch the service to a DR environment. 
 
@@ -14,7 +14,7 @@ Run each single instance database as a singleton workload or PDB in a shared RAC
 Run each single instance database as a singleton workload or PDB in a dedicated CDB
 Run each single instance database as a two–node cluster, but shut down unnecessary instances
 
-Reviewed: 01/22/26
+Reviewed: 06/28/26
 
 # Useful Links