Known Issues for Gen 1 Oracle Database Exadata Cloud at Customer (OCI-C)
(Doc ID 2252305.1)
Last updated on JUNE 13, 2023
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine)Linux x86-64
Purpose
This document describes known issues associated with Gen 1 Oracle Database Exadata Cloud at Customer, which is deployed in conjunction with Oracle Cloud at Customer using Oracle Cloud Infrastructure Classic (OCI-C).
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Details |
| Cannot use Service Manager to create a version 12.2 database deployment over upgraded Grid Infrastructure |
| Backup pieces on cloud storage not deleted during deletion of database deployment |
| Concurrently creating multiple database deployments fails using instantiate from backup |
| Older database deployments use TLS 1.0 |
| PDB name not set correctly for release 12.2 databases created using instantiate from backup |
| Potential for PDB name conflict after multiple Replace Database using Backup operations |
| Cannot create a Data Guard configuration using Oracle Database 12c Release 2 (12.2) with an additional database as the primary and a starter database as the standby |
| Deleting an Exadata Cloud at Customer instance used in a Data Guard configuration leaves behind the database on the other system |
| Manual patching required for Oracle Database 11g Release 2 (11.2.0.4) database deployments |
| Patch conflict applying April 2017 bundle patch on Oracle Grid Infrastructure |
| Clone database recovery failure |
| Automatic backups fail when the system is running commands containing orec or obkup |
| Cannot create a clone database deployment that uses ACFS and Oracle Grid Infrastructure 12c Release 2 (12.2) |
| Backup operations may fail with sqlite error |
| Database replacement using instantiate-from-backup may fail |
| Cannot create a Data Guard configuration using a starter database and more than one database instance at either the primary site or standby site |
| Instance re-creation fails |
| Patching log files may reference inaccessible storage containers in the oraclecloud.com domain |
| August 2017 bundle patch fails using old cloud tooling |
| Self-service user interface problems using a client that is not connected to the Internet |
| Cannot restart a release 12.2 database with an unencrypted tablespace |
| Cannot instantiate from an Oracle Database 12c Release 2 database backup that uses password (RMAN key) encryption |
| Must wait 10 minutes after database deployment is created before performing other deployment-level operations on it |
| Datapatch fails when host and instance names are too long |
| Need to apply the fix for bug 27169796 after October 2017 bundle patch |
| Need to apply the fix for bug 18774543 after rollback of October 2017 bundle patch on Oracle Database 12.1.0.2 |
| Need to rollback manually applied Grid Infrastructure patches before applying Grid Infrastructure bundle patches |
| Recovery fails with ORA-01102: cannot mount database in EXCLUSIVE mode |
| Exadata Snapshots not supported in conjunction with Oracle Database 18c |
| Creating a new database that uses a shared Oracle Home not supported in conjunction with Oracle Database 18c |
| An already applied patch may appear as an available patch in the service console |
| Data Guard switchover appears to hang indefinitely |
| Service console cannot force Data Guard failover |
| Data Guard broker in warning state after provisioning with Oracle Database 18c |
| Data Guard broker hangs intermittently |
| Patching fails on Data Guard configurations |
| Incorrect banner following July 2018 bundle patch |
| Cannot create snapshot Primary using ACFS storage |
| Exadata Cloud Service database backups fail with ORA-01017 |
| July 2018 Bundle Patch prerequisite check fails when database instance is down |
| July 2018 Bundle Patch prerequisite check fails because of not enough space |
| Site specific requirements for cloud tooling updates |
| Incorrect banner following October 2018 bundle patch |
| Enterprise Manager 11g Database Control not automatically configured |
| Cannot perform CPU bursting using the Web console |
| Cannot create a VM cluster containing only one node |
| Cannot perform instantiate from backup using Oracle Database 18c |
| Operations fail due to a lack of free memory |
| VM Clusters page displays incorrect amount for DB Home Storage |
| January 2019 bundle patch prerequisite check fails for Oracle Database 18c |
| January 2019 bundle patch prerequisite check fails for Oracle Database 12c Release 1 |
| Cannot scale CPU cores below the initial value |
| Datapatch fails following January 2019 bundle patch for Oracle Database 12c Release 1 |
| DomU patching fails for clusters containing one compute node |
| Unexpected compute node reboots and degraded performance following the addition of CPU resources |
| Cluster operations fail following Grid Infrastructure upgrade |
| Adding a node to a VM cluster fails due to customization on existing nodes |