Considerations for RDS Custom for Oracle database upgrades - Amazon Relational Database Service

Considerations for RDS Custom for Oracle database upgrades

If you plan to upgrade your database, consider the following:

  • When you upgrade the database binaries in your primary DB instance, RDS Custom for Oracle upgrades your read replicas automatically. When you upgrade the OS, you must upgrade the read replicas manually.

  • When you upgrade a container database (CDB) to a new database version, RDS Custom for Oracle checks that all PDBs are open or could be opened. If these conditions aren't met, RDS Custom stops the check and returns the database to its original state without attempting the upgrade. If the conditions are met, RDS Custom patches the CDB root first, and then patches all other PDBs (including PDB$SEED) in parallel.

    After patching completes, RDS Custom attempts to open all PDBs. If any PDBs fail to open, you receive the following event: The following PDBs failed to open: list-of-PDBs. If RDS Custom fails to patch the CDB root or any PDBs, the instance is put into the PATCH_DB_FAILED state.

  • You might want to perform a major database version upgrade and a conversion of non-CDB to CDB at the same time. In this case, we recommend that you proceed as follows:

    1. Create a new RDS Custom for Oracle DB instance that uses the Oracle multitenant architecture.

    2. Plug in a non-CDB into your CDB root, creating it as a PDB. Make sure that the non-CDB is the same major version as your CDB.

    3. Convert your PDB by running the noncdb_to_pdb.sql Oracle SQL script.

    4. Validate your CDB instance.

    5. Upgrade your CDB instance.