Dynamic workload broker fails to start after switching DB2® to Oracle

After migrating the IBM Workload Scheduler database vendor from DB2® to Oracle, the Dynamic Workload Broker fails to start. Following the procedure to switch the database vendor from DB2® to Oracle results in missing Dynamic Workload Broker tables in Oracle. Also, the configuration file DAOCommon.properties is not updated with the Oracle specific information. The DAOCommon.properties file is located in the following path:
On Windows operating systems
<TWA_home>\broker\config
On UNIX operating systems
<TWA_DATA_DIR>/broker/config

Cause and solution:

To correct the set of database tables, follow the procedure Upgrading the database for the server components. Also, manually update the DAOCommon.properties so that the rdbmsName=oracle, and not db2, and ensure that all three of the values for the setting *Schema= are set to the Oracle schema name for the IBM Workload Scheduler database.