Migrating ADB-Shared Environment Using Zero Downtime Migration

Autonomous Database on Shared Infrastructure (ADB-S) can be migrated to Cloud Manager using Zero Downtime Migration (ZDM)

Minimum PeopleTools requirements for migrating ADB-S to Cloud Manager are:

  • 8.59.01

  • 8.58.09

  • 8.57.20

Prerequisites for importing ADB-S database include:

  1. Backup Bucket must be set before taking backups through OCI (manual backup) or through PeopleSoft Cloud Manager.

  2. The following policies are required for ADB-S operations:

    • use vcns for the compartment which the VCN is in

    • use subnets for the compartment which the VCN is in

    • use network-security-groups for the compartment which the network security group is in

    • manage private-ips for the compartment which the VCN is in

    • manage vnics for the compartment which the VCN is in

    • manage vnics for the compartment which the database is provisioned or is to be provisioned in

To migrate a PeopleSoft database environment to Cloud Manager, perform the following steps:

  1. Use ZDM to migrate an on-premises PeopleSoft application database to Autonomous Database – Shared (ADB-S) on OCI.

    See PeopleSoft Application with Autonomous Database - Shared, Migration Guide with Oracle ZDM and Zero Downtime Migration documentation.

  2. Import the ADB-S database environment in Cloud Manager.

    See the ADB Instance Type section in Importing Environment.

    Note: When the ADB-Shared database is imported, the RefreshDBWallet policy is automatically added to the environment.

  3. Lift the APP DPK to the object store using the Application Lift (see Performing Application Lift) or copy the APP DPK to a path relative to the FSS of the Cloud Manager Instance.

  4. Use Manage Node on the imported environment to add the middle tier node.

    See Managing Nodes

Note: To support the refresh operation on Cloud Manager, it is advised to reset the passwords to 12 character passwords before migration or after migration to ADB-D.