1. Provision and deploy a maximum availability solution for PeopleSoft on Oracle Cloud
  2. Switchover to Cloud

Switchover to Cloud

When your functional and performance tests show your new environment is ready, you can schedule and perform switching production operations to OCI.

There are three parts to this process:

  • Shut down the on-premises production PeopleSoft application.
  • Switchover to the database in the cloud, making the physical standby in OCI the primary and the on-premises database a physical standby.
  • Start the PeopleSoft applications in OCI at the new primary site.

After completing those tasks, you can take a backup of the primary OCI environment.

Perform a Full Stack Switchover

Perform an Oracle Data Guard switchover role change, making the physical standby on the Oracle Exadata Database Service on Dedicated Infrastructure in OCI the primary and the on-premises database a physical standby.

  1. Shut down on-premises production PeopleSoft applications.
    On the on-premises systems, shut the PeopleSoft Internet Architecture (PIA), batch, and application servers down. Let them shut down completely and cleanly.
  2. Log in to an OCI database server at the primary site as the oracle user. In the home directory, source the standby database environment.
    $ . ./CDBHCM.env
  3. Start Data Guard Broker as SYS.
    $ dgmgrl
DGMGRL> connect sys/password
  4. Using Data Guard Broker, verify that the database is ready for switchover.
    DGMGRL> validate database CDBHCM_iad1dx
  Database Role:     Physical standby database
  Primary Database:  CDBHCM_sca6dp
  Ready for Switchover:  Yes
  Ready for Failover:    Yes (Primary Running)
  Managed by Clusterware:
    CDBHCM_sca6dp:  YES            
    CDBHCM_iad1dx:  YES
  5. Perform the switchover.
    DGMGRL> switchover to CDBHCM_iad1dx;
Performing switchover NOW, please wait...
New primary database " CDBHCM_iad1dx" is opening...
Oracle Clusterware is restarting database " CDBHCM_sca6dp" ...
Connected to " CDBHCM_sca6dp"
Connected to " CDBHCM_sca6dp"
Switchover succeeded, new primary is "CDBHCM_iad1dx"
  6. Verify that the role-based database services have started. If they have not started, start them manually.
    For example, HR92U033_BATCH and HR92U033_ONLINE
    $ srvctl start service -db CDBHCM_iad1dx -s HR92U033_BATCH
$ srvctl start service -db CDBHCM_iad1dx -s HR92U033_ONLINE

    Note:

    You can start backing up the PeopleSoft OCI primary database, described in the next task, as soon as the database has taken the primary role.
  7. Start the PeopleSoft application using the scripts in Application Domain Server and PIA Web Server. Use basic sanity checks to be sure the environment started correctly.
    • Check the logs on the application servers to make sure the PeopleSoft application and process scheduler domains start all Tuxedo processes without errors.
    • When the PIA web servers are started, use the OCI Console to check the load balancer to be sure the backend sets are healthy, showing a green OK for each compute instance in the backend set.
    • Make sure you can log in to the application as an end user, using a browser.

    After switching over to cloud, you may need to re-enable SSL Termination at OCI Load Balancer at both the primary and secondary regions. This is because the databases were in SNAPSHOT STANDBY and once the databases were returned back to a physical standby, the changes within the databases were lost. You have already created a web profile within the configuration.properties file. To enable SSL termination at the OCI load balancer, do the following:

    1. Stop the PIA web services on all PIA compute instances.
    2. On one of the PIA web services, edit the configuration.properties file and set the web profile back to the non-SSL version (PROD) and save the change.
    3. Start the PIA web server just on the compute instance where this change was made.
  8. Log in to the PIA Web application as a PeopleSoft administrator, such as PS.
    • User: PeopleSoft Admin User, PS
  9. Copy the current or active web profile, as the PS user.
    • User: PeopleSoft Admin User, PS
    1. Click the navigation bar icon.
    2. Click Navigator.
    3. Click PeopleTools.
      You might need to scroll through the options.
    4. Click Web Profile.
      You might need to scroll through the options.
    5. Click Copy Web Profile.
    6. Click Search.
      You don't need to enter anything into the search box.
    7. Click on an active web profile from the list, such as PROD.
    8. Enter a name, such as PROD_SSL, in the To field.
    9. Click Save.
    10. Click the Home icon.
  10. Configure the copied web profile.
    • User: PeopleSoft Admin User, PS
    1. Click the navigation bar icon.
    2. Click Navigator.
      If you're in the same session as Step 2, then Navigator remembers where you are.
    3. Click Web Profile Configuration.
    4. Click Search.
      You don't need to enter anything into the search box.
    5. Click an active web profile from the list, such as PROD_SSL that you just created.
    6. Click the Virtual Addressing tab.
    7. Protocol: Enter https (lower case) for Default Addressing.
    8. Port: Enter 443 for the default port, or enter different port. Leaving it blank will default to port 443.
    9. Click Save.
    10. Exit the application.
  11. Stop the PIA web server.
  12. Edit the configuration.properties file and set the web profile to the SSL version, that is PROD_SSL, and save the change.
  13. Ensure all PIA web server compute instances have their web profile now set to the SSL enabled profile.
  14. Restart the PIA web server.

Back Up the PeopleSoft OCI Primary Database

Oracle recommends that you take a full database backup as soon as the switchover is complete and the database in OCI is in the primary role, to establish your baseline database backup in OCI. Perform the following to take a full backup now and set up automatic backups.

  1. Log in to the OCI Console.
  2. Select the compartment containing the Oracle Exadata Database Service on Dedicated Infrastructure cluster.
  3. Click the Oracle Exadata Database Service on Dedicated Infrastructure cluster.
  4. Click the database from the list of databases.
  5. Click Backups under Resources.
  6. Click Configure Automatic Backup.
    A new form for backups is displayed.
  7. Select Enable automatic backups.
    Complete the following to define your automatic backups:
    1. Backup retention period (7 days to 60 days).
    2. The day of the week that a full backup is to be taken.
    3. The two-hour time window (UTC) on the day selected above that the full backup will be taken.
    4. The two-hour window (UTC) on each day that the incremental backups will be taken.
    5. If you want a full backup taken right away, then select Take the first backup immediately.
      This will start a full backup once you save the changes in this form.
    6. Click Save Changes.

If you indicated the first backup should be taken immediately, OCI will start a full backup when you save your changes.

Backup activity from that point forward will take place during your specified backup window, starting the pattern of taking an incremental backup six days a week and a full backup once a week. Archived redo logs are automatically backed up once every 30 minutes. OCI-based backups will configure Oracle Recovery Manager (RMAN) to use the cloud backup module in OCI.

As each backup completes, it is listed in the table of backups on the database’s Resources page.

Remove the On-Premises Database

You have switched operations to your OCI environment, but you're still keeping your on-premises database in sync using Oracle Data Guard. While it is a good practice to do this for a brief period as a fallback, at some point you'll stop redo replay to your old on-premises database and drop that environment.

  1. Log in to an OCI database server at the primary site as the oracle OS user.
  2. Source the environment.
    $ . ./CDBHCM.env
  3. Log into Data Guard Broker as SYS with your syspassword.
    $ dgmgrl
DGMGRL> sys/syspassword
  4. Remove the redoroutes for all databases.
    You no longer need a cascade standby configuration and can remove the configurations. 
    DGMGRL> EDIT DATABASE CDBHCM_sca6dp reset property RedoRoutes;
DGMGRL> EDIT DATABASE CDBHCM_iad1dx reset property RedoRoutes;
DGMGRL> EDIT DATABASE CDBHCM_phx5s reset property RedoRoutes;
  5. Remove the on-premises database CDBHCM_sca6dp from the configuration.
    DGMGRL> REMOVE DATABASE CDBHCM_sca6dp;

The current primary sends its redo to the remaining standby database. You can now shut down the on-premises database.