Performing the Database Lift

The Database lift means lifting the database of PeopleSoft instance as a hot backup using RMAN.

Note: Database Lift using hot backup can only be performed on a database instance that has access to the internet.

It is recommended to bring the database patch level of the on-premises environment equivalent to that of the database patch level of the Oracle Database Cloud Service before starting the Lift and Shift process.

If the patch levels are different, then Cloud Manager will try to either rollback or update the patch. It is possible that there could be some incompatibilities during lift and shift due to rollbacks or updates. Users will then need to manually verify and rectify it.

Installing OCI-CLI is a prerequisite for the lift utility. See Installing Lift Prerequisites

Considerations Before Running Database Lift

  1. Lift can be performed on the DB instance (Local Lift) only.

  2. Ensure to use only the Database owner user (for example, oracle) to perform DB Lift.

  3. Ensure to have sufficient free disk space for DB Lift based on DB size.

  4. Oracle Database 19c and later is supported.

  5. Ensure to take the back up of your Database environment and the RMAN configurations before performing DB Lift. Optionally, it is recommended to use a clone of the environment for the Lift operation.

    Note: During the Lift process, the Oracle Database will not be shut down.

  6. Ensure to back up the ORACLE_HOME.

  7. Ensure that the user running the lift utility has permission to create files/directories at the user's home directory, Lift utility destination directory where the DPKs are saved, /tmp, and ORACLE_HOME directory.

Note: If you want to encrypt the database before lifting using TDE, see Encrypting Tablespaces Using Transparent Data Encryption.

RMAN Lift and Shift supports the following Oracle Databases:

  • Oracle 19c and later

  • Container Databases

  • Unicode and Non-Unicode Databases

  • TDE enabled Database

  • Database on ASM

Note: During Lift and Shift with RMAN the Oracle Database Cloud Backup Module (ODCBM) is used in the background to perform full RMAN Backup and Restore operations.

During Database Lift with RMAN the Lift Utility will create a fresh Bucket in the OCI Object storage and then the RMAN Backup of the source (on-premises) Database environment will be compressed and encrypted before being wired to the bucket in the OCI Object Storage. Along with the RMAN backup the "APP-DPK-<platform>-<app_type>-<db_name>-2of<X>.zip" is created to capture the sqlpatches, database parameter file and other metadata information.

The "APP-DPK-<platform>-<app_type>-<db_name>-2of<X>.zip" will be small, since we are not packaging the Database files (*.dbf) within this zip.

RMAN Lift and Shift does not support:

  • RAC Database

  • RMAN (L1) Incremental Backup.

Note: It is recommended that the DB Tier Database is started with a spfile.

Ensure the Database “Archive Log Mode” is enabled (My Oracle Support Doc ID 371139.1).

Ensure the proxy (if needed) is correctly specified and the proxy authentication does not have any special characters.

To perform an RMAN Lift of a PeopleSoft environment that was already lifted using the older version of Cloud Manager (Lift Utility), it is recommended to delete the existing Lifted DPK from the Cloud Manager “Lift and Shift” UI and then trigger a RMAN lift for the same.

To perform the Lift using Hot Backup:

  1. Navigate to the Lift and Shift tile.

  2. Download and copy the “LIFT_UTILITY.zip” to the target machine to perform lift.

    Note: If you have updated Cloud Manager with PRP (find PRP name/number), then SSH to Cloud Manager VM and delete the stale zip file from /tmp/LIFT_UTILITY.zip.

  3. Navigate to the below folder after extracting the LIFT_UTILITY.zip and set permissions: 

    chmod -R 777 <LIFT_UTILITY_PATH>
cd <LIFT_UTILITY_PATH>/setup

  4. Export Java home.

    export JAVA_HOME=/tmp/java18/jre

  5. For Linux, run the sh psft-osl.sh command to perform lift.

  6. At the prompt “Do you want to Lift the Application Environment”, enter “N” to Lift the DB instance.

  7. At the prompt input the following:

    – Container Database name (applicable only for Multitenant database)

    – Database name

  8. Performing Lift using Hot Backup requires the OCI details:

    See Locating OCI Credentials

    – Oracle Cloud Infrastructure Region Name

    – Oracle Cloud Infrastructure Tenancy Name

    – Oracle Cloud Infrastructure Tenancy ID

    – Oracle Cloud Infrastructure User ID

    – Private Key Location, indicates the API signing private key that was created during CM configuration and must be copied to the instance where lift utility will be run. This input refers to the full path to the file.

    – Passphrase, refers to the passphrase that was used to encrypt the keys.

    Note: You need to manually copy the key file or copy the key file contents and save locally in machine where you perform a lift. This is the corresponding Private Key to the Public Key that was set in the API Keys of the user setting.

    – OCI User name

    – OCI Auth Token

    Note: Ensure not to delete this OCI Auth Token (for the user) from OCI console, because the User name/Token will be used for Lift and Shift process. The OCI Auth Token is also required for a refresh from on-premises to Cloud.

    – OCI Infrastructure Compartment ID (OCID)

  9. To create the PeopleSoft Database DPK, you need to provide the following:

    – Container Database name (Applicable only for supported versions of Oracle multitenant database)

    – Database name

    – Number of channels (threads) for RMAN backup (Value between 1–8)

    – TDE KeyStore (Wallet) Password (If TDE is enabled on source Database)

    – RMAN Backup Encryption Password (If TDE is not enabled on source Database)

    – DB environment Proxy Host (* If Any)

    – DB environment Proxy Port (* If Any)

    – Destination Directory

    Note: If the utility is unable to fetch the data from the environment, it will prompt the user to input the same.

  10. The script then displays the details captured from the user and prompts for the user’s confirmation to proceed. The utility allows the user to modify the above listed inputs, if required.

  11. The entire process is logged into psft_lift_session_<session_name>_<session_count>_<PID>.log file.

  12. After DB Lift is complete, the following DB DPK will be created.

    APP-DPK-<platform>-<app_type>-<db_name>-2of3.zip

    Note: The APP-DPK*-3of3.zip will not be created as part of the Lift utility, however the APP-DPK*-3of3.zip DPK will be available from the PeopleTools DPK when the shift is triggered from Cloud Manager.