1. New mechanism to update the database schema for DB2 and Oracle databases IBM Workload Scheduler IBM

2. Background When upgrading the master domain manager, or its backup, or the dynamic domain manager or its backup, the following database schemas also need to be upgraded due to changes to the database introduced by new features: MDM and BKM: IBM Workload Scheduler database schema Dynamic workload broker database schema DDM and BDM: Dynamic workload broker database schema

3. Why is this a painpoint? From customer feedback, we know that the current upgrade procedure we provide is neither flexible, nor recoverable, nor reliable. Common painpoints: Unexpected configuration changes made after the last update interfere with the upgrade. The DB2 Server is not correctly catalogued on the DB2 client. The user accessing the DB does not have sufficient persmissions to run the SQL upgrade scripts. The DB admin made manual changes to the schema (i.e., added indexes) to improve performance. Current solution : Call IBM Support

4. How the problem was solved - manual The new upgrade mechanism is based on a a single script that takes in input a property file containing the majority of information required to perform the upgrade: launchUpgradeIWSDB.bat where, is DB2: The fully qualified directory path to the JDBC driver JAR file that contains the JDBC driver class. Oracle: The ORACLE_HOME directory.

5. How the problem was solved - UI The script can be run manually or, when upgrading with Installation Manager wizard or the silent installation method, this script is called and the database schema is upgraded during the installation of the product component.

6. What are the benefits of this method? The new upgrade/update tool: Adapts to the environment that is being upgraded and dynamically generates the SQL statements to be applied. If changes were made to the schema or if it contains unsupported objects, the upgrade mechanism restores the situation to permit a successful upgrade. If the upgrade/update procedure is interrupted, the tool can be re-run as many times as necessary to recover, without requiring any clean-up in between runs, and without making any changes to the SQL scripts. Changes already applied are automatically skipped during subsequent runs. In addition to the upgrade context, the tool can also be used stand-alone to reliably verify at any time if the database schema has changed, and repair any inconsistencies. The tool is flexible and can be used for MDM, DDM, and their backups, independently of whether the database is DB2 or Oracle. It can be run during the installation or manually as a preliminary step to generate an SQL script to pass on to the DB admin. This reduces the number of steps and scripts that an admin needs to manage. For DB2 databases, the tool eliminates the need for the DB2 client to upgrade a database that is located on a remote DB2 server. Using the JDBC drivers, the tool can update the remote DB without the client, minimizing the overhead of installing and maintaining a database client and reducing the risks of incorrect cataloguing of the database server on the DB2 client.

7. Any questions? Questions?

8. Thank you IBM