Data Preserving Reprovisioning

Which releases of Oracle Database Appliance are supported as the source versions for upgrade using the Data Preserving Reprovisioning feature?

Oracle Database Appliance releases 12.1.2.12, 12.2.1.4, 18.3.0.0.0, 18.5.0.0.0, 18.7.0.0.0 and 18.8.0.0.0.

Which database versions can be detached and recreated using Data Preserving Reprovisioning?

The following database versions are supported:

Oracle Database 11.2.0.4.170814 and 12.1.0.2.170814 on Oracle Database Appliance release 12.1.2.12
Oracle Database 11.2.0.4.180417, 12.1.0.2.180417, and 12.2.0.1.180417 on Oracle Database Appliance release 12.2.1.4
Oracle Database 11.2.0.4.180717, 12.1.0.2.180717, 12.2.0.1.180717, and 18.3.0.0.180717 on Oracle Database Appliance release 18.3
Oracle Database 11.2.0.4.190115, 12.1.0.2.190115, 12.2.0.1.190115, and 18.5.0.0.190115 on Oracle Database Appliance release 18.5
Oracle Database 11.2.0.4.190716, 12.1.0.2.190716, 12.2.0.1.190716, and 18.7.0.0.190716 on Oracle Database Appliance release 18.7
Oracle Database 11.2.0.4.191015, 12.1.0.2.191015, 12.2.0.1.191015, and 18.8.0.0.191015 on Oracle Database Appliance release 18.8

The databases of these versions are kept intact on the storage. Successful completion of the command odacli restore-node -d on the newly reprovisioned system leaves these databases running with the same version as the one prior to Data Preserving Reprovisioning. You can then patch the databases to the latest patchset release using the command odacli update-dbhome.

The following exception applies:

There is no patching support for Oracle Database release 11.2.0.4 databases from Oracle Database Appliance release 19.11 and later. There is no patching support for Oracle Database release 18c databases from Oracle Database Appliance release 19.12 and later. There is no patching support for Oracle Database release 12.2.0.1 databases from Oracle Database Appliance release 19.15 and later. You cannot use the command odacli update-dbhome to patch these databases. Use the OPatch utility to patch such databases. For the procedure to patch these databases, see the topic Out-of-Cycle Database Patches in the Oracle Database Appliance Deployment and User's Guide for your hardware model.

I have 11.2.0.4 databases on my 12.2.1.4 or 12.1.2.12 system. Are these databases preserved after running the odaupgradeutil detach-node command?

Yes.

Are all the patches required during Data Preserving Reprovisioning still available on ARU?

Yes. To view the patch numbers and details, refer to the Oracle Database Appliance Release Notes for your source system release. The database patches corresponding to 12.1.2.12, 12.2.1.4, 18.3, 18.5, 18.7, and 18.8 are still available for download. If the source Oracle Database Appliance version on which the odaupgradeutil detach-node command is run is an OAK stack, then after re-imaging to Oracle Database Appliance release 19.15 or later, the software runs on a DCS stack. The Oracle Database clone file corresponding to the DCS stack must be used.

Following are the patch numbers to search for DCS stack:

Oracle Database 11.2.0.4 clones: Patch 23494997. On the Patch page, make a selection from the drop down list.
- For Oracle Database 11.2.0.4.170814 clone, select Oracle Appliance Kit 12.1.2.12.0.
- For Oracle Database 11.2.0.4.171017 clone, select Oracle Appliance Kit 12.2.1.2.0.
- For Oracle Database 11.2.0.4.180116 clone, select Oracle Appliance Kit 12.2.1.3.0.
- For Oracle Database 11.2.0.4.180417 clone, select Oracle Appliance Kit 12.2.1.4.0.
- For Oracle Database 11.2.0.4.180717 clone, select Oracle Appliance Kit 18.3.0.0.0.
- For Oracle Database 11.2.0.4.181016 clone, select Oracle Appliance Kit 18.4.0.0.0.
- For Oracle Database 11.2.0.4.190115 clone, select Oracle Appliance Kit 18.5.0.0.0.
- For Oracle Database 11.2.0.4.190416 clone, select Oracle Appliance Kit 18.6.0.0.0.
- For Oracle Database 11.2.0.4.190716 clone, select Oracle Database Appliance Software (ODA) 18.7.0.0.0.
- For Oracle Database 11.2.0.4.191015 clone, select Oracle Appliance Kit 18.8.0.0.0.
Oracle Database 12.1.0.2 clones: Patch 23494992. On the Patch page, make a selection from the drop down list.
- For Oracle Database 12.1.0.2.170814 clone, select ORACLE DATABASE APPLIANCE X6-2 S and X6-2 M 12.1.0.2.170814 RDBMS Clone DOWNLOAD (Patch).
- For Oracle Database 12.1.0.2.170814 clone, select ORACLE DATABASE APPLIANCE X7-2 HA, X7-2 S and X7-2 M 12.1.0.2.170814 RDBMS Clone DOWNLOAD (Patch).
- For Oracle Database 12.1.0.2.171017 clone, select ORACLE DATABASE APPLIANCE X6-2 S and X6-2 M 12.1.0.2.171017 RDBMS Clone DOWNLOAD (Patch).
- For Oracle Database 12.1.0.2.180116 clone, select ORACLE DATABASE APPLIANCE X6-2 S and X6-2 M 12.1.0.2.180116 RDBMS Clone DOWNLOAD (Patch).
- For Oracle Database 12.1.0.2.180417 clone, select ORACLE DATABASE APPLIANCE RDBMS CLONE 12.1.0.2.180417 FOR ODACLI/DCS STACK (Patch).
- For Oracle Database 12.1.0.2.180717 clone, select ORACLE DATABASE APPLIANCE RDBMS CLONE 12.1.0.2.180717 FOR ODACLI/DCS STACK (Patch).
- For Oracle Database 12.1.0.2.181016 clone, select ORACLE DATABASE APPLIANCE RDBMS CLONE 12.1.0.2.181016 FOR ODACLI/DCS STACK (Patch).
- For Oracle Database 12.1.0.2.190416 clone, select ORACLE DATABASE APPLIANCE RDBMS CLONE 12.1.0.2.190416 FOR ODACLI/DCS STACK (Patch).
- For Oracle Database 12.1.0.2.190716 clone, select ORACLE DATABASE APPLIANCE RDBMS CLONE 12.1.0.2.190716 FOR ODACLI/DCS STACK (Patch).
- For Oracle Database 12.1.0.2.191015 clone, select ORACLE DATABASE APPLIANCE RDBMS CLONE 12.1.0.2.191015 FOR ODACLI/DCS STACK (Patch).
Oracle Database 12.2.0.1 clones: Patch 27449599. On the Patch page, make a selection from the drop down list.
- For Oracle Database 12.2.0.1.180417 clone, select Oracle Appliance Kit 12.2.1.4.0.
- For Oracle Database 12.2.0.1.180717 clone, select Oracle Appliance Kit 18.3.0.0.0.
- For Oracle Database 12.2.0.1.181016 clone, select Oracle Appliance Kit 18.4.0.0.0.
- For Oracle Database 12.2.0.1.190115 clone, select Oracle Appliance Kit 18.5.0.0.0.
- For Oracle Database 12.2.0.1.190416 clone, select Oracle Appliance Kit 18.6.0.0.0.
- For Oracle Database 112.2.0.1.190716 clone, select Oracle Database Appliance Software (ODA) 18.7.0.0.0.
- For Oracle Database 12.2.0.1.191015 clone, select Oracle Appliance Kit 18.8.0.0.0.
Oracle Database 18.x clones: 27604558. On the Patch page, make a selection from the drop down list.
- For Oracle Database 18.3.0.0.180717 clone, select Oracle Appliance Kit 18.3.0.0.0.
- For Oracle Database 18.4.0.0.181016 clone, select Oracle Appliance Kit 18.4.0.0.0.
- For Oracle Database 18.5.0.0.190115 clone, select Oracle Appliance Kit 18.5.0.0.0.
- For Oracle Database 18.6.0.0.190416 clone, select Oracle Appliance Kit 18.6.0.0.0.
- For Oracle Database 18.7.0.0.190716 clone, select Oracle Database Appliance Software (ODA) 18.7.0.0.0.
- For Oracle Database 18.8.0.0.191015 clone, select Oracle Database Appliance Software (ODA) 18.8.0.0.0.

Which are the versions of database clones that must be available on the appliance before running the command odacli restore-node?

The databases versions supported are listed in the previous FAQ. If the source was an OAK stack, the DCS clone version must be updated in the repository after the system is reimaged to Oracle Database Appliance release 19.15.

Can database clones that were used on Oracle Database Appliance system running OAK software be used when running the command odacli restore-node on Oracle Database Appliance deployment with release 19.15 or later DCS software?

No. If the source Oracle Database Appliance version on which the odaupgradeutil detach-node command is run is an OAK stack, then after re-imaging to Oracle Database Appliance release 19.15 or later, the software runs on a DCS stack. The Oracle Database clone file corresponding to the DCS stack must be used. For example, for 12.1.0.2 database, if the clone used on the OAK stack was patch number 19520042, then after reimaging to 19.15 or later, the clone 23494992 for the same version (12.1.0.2.170814) must be downloaded and used.

I have additional operating system RPMs installed on my system. Are these restored as part of Data Preserving Reprovisioning?

No. Since the Data Preserving Reprovisioning process involves reimaging using the latest Oracle Database Appliance ISO image, any previous customizations in operating system RPMs, or any customizations in the settings or configurations of services in the operating system are lost. You must uninstall these RPMs and then continue with the next step in the upgrade process. You can reinstall these custom RPMs as required, after the upgrade.

I have configured VLANs on my system. Will these VLANs be configured on the upgraded system?

Yes.

Do I need to take backups of my databases before running the odaupgradeutil detach-node command?

The database files are left intact on Oracle ASM disk groups and are used for bringing up the databases after successful reprovisoning. You must, however, take database backups as a safety measure.

I have a 2-JBOD configuration. Is Data Preserving Reprovisioning supported with this configuration?

Yes.

I have additional options (for example, ASO) enabled on my source databases. Are these options preserved?

Options that are part of the Oracle software are not preserved. The new database homes created as part of reprovisioning are created with the default options.

Is Data Preserving Reprovisioning supported on all supported Oracle Database Appliance hardware models?

Yes.

What happens to my database audit data after the reimage process in Data Preserving Reprovisioning?

The audit data of databases can be either in database tables or in operating system files or in SYSLOG. Only the data in database tables is preserved. You must save the audit data that is present on the root file system before initiating reimage of the system.

Can I run cleanup.pl after detaching the node on source ODA version?

No. Do not run cleanup.pl at any time during the upgrade process. This utility erases the Oracle ASM disk groups and then you cannot restore the databases. If there is a failure in running the command odacli restore-node -g, then you can use cleanup.pl to clean up the system while preserving Oracle ASM disk groups. Run cleanup.pl in DPR mode and do not use the -nodpr option.

What is the typical outage time for upgrade using Data Preserving Reprovisioning?

The total outage time depends on various factors such as system configuration, for example, CPU, memory, disk, and the number of databases configured. The process typically requires approximately 4 hours from the time of running the detach-node process. For a high-availability system, the typical outage is around 5 hours 30 minutes.

Are all files present in database homes preserved and restored?

Since the information on the local filesystem is deleted during reimage, the files on database homes such as TDE wallets are not preserved.

Is Oracle ASR restored?

Oracle ASR is not restored during the reprovisioning process. Oracle ASR information is saved at /opt/oracle/oak/restore/metadata/asr.info. After the reprovisioning process, you can manually configure Oracle ASR using the command odacli configure-asr, which automatically configures Oracle ASR to use the latest version available on the reprovisioned system.

Can database homes be created on the root file system after reprovisioning to Oracle Database Appliance release 19.15 or later?

No, database homes can only be created on Oracle ACFS.

How much space is required for database homes and database clones on Oracle ACFS?

For database clones on Oracle ACFS, a total of 150 GB is required. The space required for database homes is 15GB multiplied by the number of database homes to be restored. The space availability is also validated at the source by the odaupgradeutil prechecks.

Should I unpack Oracle Grid Infrastructure and Oracle Database clones together?

No, it is recommended that only the Oracle Grid Infrastructure clone is unpacked before running the command odacli restore-node -g. After the command odacli restore-node -g runs successfully, the database clones are moved to Oracle ACFS which has 150 GB of space.

Do the nodes restart during any of the operations?

When running the command odacli restore-node -g, if the number of licensed CPU cores is less than the maximum, the nodes are restarted to enable this setting.

Why does cleanup with -erasedata or -f fail after reprovisioning using Data Preserving Reprovisioning?

On Data Preserving Reprovisioning environments, the default cleanup mode is the Data Preserving Reprovisioning mode. This mode cleans up the appliance without erasing Oracle ASM disks to allow the command odacli restore-node -g to be reattempted. This mode is enabled after the command odacli update-repository completes the step to generate the server archives. This mode does not support usage of -erasedata or -f options.

Override this behavior and force regular cleanup with the -nodpr option as follows:

cleanup.pl -nodpr -erasedata / -f

Can multi-user access be enabled with Data Preserving Reprovisioning?

No, multi-user access cannot be enabled with Data Preserving Reprovisioning. Enabling multi-user access through BUI before running the command odacli restore-node -g may lead to failures in reprovisioning.