Data Preserving Reprovisioning: Databases
Understand FAQs on updating databases in the Data Preserving Reprovisioning process.
Are there any database homes on the local file system after the Data Preserving Reprovisioning process completes?
No. Database homes on the local file system are deleted when the system is reimaged.
Are databases patched to Oracle Database release 19.24 as part of the Data Preserving Reprovisioning process?
No. Data Preserving Reprovisioning only reprovisions the system and restarts all resources such as databases and DB systems on Oracle Linux 8. You must then run database patching commands such as odacli update-database after the reprovisioning steps are complete.
Are there any database customizations that I need to be aware of when using Data Preserving Reprovisioning?
Any customizations made to the database home, for example, SQL*Plus login file are
lost during the Data Preserving Reprovisioning process. It is the users responsibility to
backup your customizations before the node is reimaged. These changes will then need to be
manually applied after the odacli restore-node -d
job completes
successfully.
Will the TDE wallets, that is, Password Protected Wallet (ewallet.p12) and Autologin Wallet (cwallet.sso) be lost after the Data Preserving Reprovisioning process completes ?
No, since TDE wallets are placed in DATA location and the Data Preserving Reprovisioning process does not erase the contents of the DATA location, the TDE wallets are not lost after the Data Preserving Reprovisioning process completes.
Is it required to reset the database
initialization parameters WALLET_ROOT
and
TDE_CONFIGURATION
for TDE databases after the Data Preserving
Reprovisioning process completes?
No. Since the database initialization parameters WALLET_ROOT
and TDE_CONFIGURATION
are not deleted after the Data Preserving
Reprovisioning process completes, resetting these parameter values after DPR completes is
not required..
Why do I need to update the repository with database clones again?
Database homes existing on the local disk, before the reimage, are wiped out. These need to be created once again on the shared database home file system. You will be prompted to update the repository, if the clones are not available.
Are my customizations made to the database home also restored?
No. You must save any file that may have been customized, before the reimage.
The customization must be manually applied after the odacli restore-node -d
job completes successfully.
What is the type of database for which
the precheck Validate TDE wallet presence
is applicable?
The precheck Validate TDE wallet presence
is applicable to
TDE-enabled database whose TDE wallet management
attribute is set to the
value EXTERNAL
.
If TDE wallet management is
EXTERNAL
, will the wallet be saved and restored by the Data Preserving
Reprovisioning process?
No, TDE wallets are not saved and restored by the Data Preserving
Reprovisioning process. The TDE wallets (ewallet.p12
and
cwallet.sso
) must be copied by the user to the
dbhome/admin/db_uniquename/wallets
location and restoreed
to the earlier location after the Data Preserving Reprovisioning process completes
successfully.
The precheck TDE wallet presence
check
expects both password-protected TDE wallet (ewallet.p12
)
and Autologin TDE wallet (cwallet.sso
) to be present at the
dbhome/admin/db_uniquename/wallets
location. Is it
necessary to copy both the TDE wallets?
Yes, both password-protected TDE and Autologin wallets
(ewallet.p12
and cwallet.sso
) must be copied to the
dbhome/admin/db_uniquename/wallets
location.
Should the TDE parameters such as
SQLNET.ENCRYPTION_WALLET_LOCATION
or WALLET_ROOT
that
were used to configure TDE be updated to point to the copied TDE wallets at the
dbhome/admin/db_uniquename/wallets
location?
No, the TDE parameters need not be updated. Once the node is restored, both the
password-protected TDE and Autologin wallets (ewallet.p12
and
cwallet.sso
) can be copied to the same location that was present before
node restore. None of the TDE parameters are lost during node restore. Copy the TDE wallets
to the dbhome/admin/db_uniquename/wallets
location as a
precautionary measure so that TDE wallets are not lost accidentally during node restore.
After the Data Preserving Reprovisioning
process completes and the TDE wallets are copied to their previous location, can the TDE
wallets at the dbhome/admin/db_uniquename/wallets
location be
deleted?
Yes, the TDE wallets at the
dbhome/admin/db_uniquename/wallets
location can be deleted
after the Data Preserving Reprovisioning process completes, and the TDE wallets are copied
to their original location.
Is it recommended to change the TDE wallet management of the database from 'EXTERNAL' to 'ODA' after upgrading to Oracle Database Appliance release 19.21 or later? If yes, how can I change TDE wallet management?
Yes, it is recommended to change the TDE wallet management of the database from
EXTERNAL
to ODA
after upgrading to Oracle Database
Appliance release 19.21 or later. When you make this change, Oracle Database Appliance then
handles all TDE wallet management activities such as backup, restore, re-key and change of
password.
Use the --change-tdewallet-mgmt,-ctm
option in the
odacli modify-database
command to set TDE wallet management.