Database Migration: Configuring DSERIES to connect to a new machine

Products

• DSERIES- SERVER
• ESP dSeries Workload Automation - Scheduler (dSeries)
• ESP dSeries Workload Automation

Issue/Introduction

This article provides steps to migrate the Workload Automation DE (dSeries) database to a new server or machine. This process includes updating connection properties for both primary and standby servers, validating database connectivity, and a rollback procedure for environment recovery. Use these instructions when moving from existing database instances (Oracle, Microsoft SQL Server, or PostgreSQL) to a new infrastructure.

Environment

• Product: Workload Automation DE (dSeries) 12.x and higher
• Operating Systems: Windows, Unix, Linux
• Databases: Oracle, Microsoft SQL Server, PostgreSQL

Resolution

Follow these steps in the exact sequence provided:

1. Backup Configuration: Take a backup of the db.properties file located in the /conf/ directory on both the primary and standby DSERIES servers.

2. Stop Services: Stop the DSERIES service on both servers. Stop the standby server first to avoid database updates during the migration process.

3. Database Migration: Perform a full backup of the DSERIES database and restore it on the new database server. Retain the original database until the migration is fully validated.

4. Configure Connection: On the primary server, run the setdbparm utility to point DSERIES to the new database URL.

   • Windows:
     cmd

     \bin\setdbparm.bat jdbc.URL

   • Unix/Linux:
     bash

     /bin/setdbparm jdbc.URL

   Note: For detailed utility parameters, refer to the Modify the Database Connection Properties.

5. Validate Connectivity: Run the validatedbconnection utility to ensure the primary server can reach the new database.

   • Windows:
     cmd

     \bin\validatedbconnection.bat

   • Unix/Linux:
     bash

     /bin/validatedbconnection

   If errors occur, resolve the network or credential issues and re-run the utility. For persistent issues, see Contact Broadcom Support.

6. Sync Standby: After a successful validation, copy the updated db.properties file from the primary server to the same directory on the standby server.

7. Restart Services: Start the DSERIES service on both servers, starting with the primary server first. Run functional tests to confirm the environment is stable.

Rollback Plan

To revert the migration and reconnect to the original database:

1. Stop the DSERIES service on both servers (standby first).
2. Restore the db.properties files from the backups created in Step 1.
3. Run the validatedbconnection utility on both servers to confirm the original connection is active.
4. Start the DSERIES service on both servers (primary first).