Enabling Full Deployments for AutoUpgrade

To enable a guaranteed restore point (GRP) so that you can flashback an upgrade, you must set up an archive, and you should complete other tasks to enable AutoUpgrade to complete the upgrade.

For AutoUpgrade to be able to perform a full deployment of the new release Oracle Database, the following must be true:

draft

The source database initialization parameters file must specify a recovery location and size using the parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE.
If the backups were created using transparent encryption, and if a password-based software keystore was used, then the keystore password must be provided before the restore operation is performed, unless you have configured an auto-login software keystore is used.
Your source Oracle Database must be running in ARCHIVELOG mode.

Note:

AutoUpgrade creates a guaranteed restore point (GRP) during Deploy processing mode. You do not need to have a previously defined guaranteed restore point.

Example 3-3 Setting up Archive Logging Before Using AutoUpgrade

sqlplus / as sysdba 
shutdown immediate;
startup mount;
alter system set db_recovery_file_dest_size = 50g scope=both sid='*'; 
alter system set db_recovery_file_dest =' /tmp/db-home/fast_recovery_area' scope=both sid='*';
alter database archivelog;
alter database open;
alter pluggable database all open;

Example 3-4 Password Files and Security Control Updates

During the upgrade, the AutoUpgrade utility copies the password from the source Oracle Database Oracle home to the target Oracle Database Oracle home. However, the copied password file retains the earlier release password control settings. To enforce stricter password controls, Oracle recommends that after the upgrade, you regenerate the password file in the target Oracle home.

Example 3-5 Transparent Data Encryption and AutoUpgrade

To enable the AutoUpgrade utility to obtain the privileges required for copying transparent data encryption wallets, you must enable auto-login for these wallets so that AutoUpgrade can copy them to the target Oracle Database release. If you do not enable auto-login, then AutoUpgrade cannot complete the upgrade.

To start Oracle Wallet Manager:

(Windows) Select Start, then Programs, then Oracle-Oracle-home (where Oracle-home is the source Oracle home, then Integrated Management Tools, and then Wallet Manager.
(UNIX) At the command line, enter: this command
```
owm
```

To enable auto login:

Select Wallet from the menu bar.
Select AutoLogin. A message at the bottom of the window indicates that auto login is enabled.

Related Topics

Oracle Database Enterprise User Security Administrator's Guide

Parent topic: Using AutoUpgrade for Oracle Database Upgrades