Modifying the database

To modify the database for a deployed addition or extension, execute the Rollback SQL scripts as follows:

Procedure

Connect to the InfoSphere® MDM database.
Run the following scripts, where <project name> is the name of the project you are working with.
- For DB2® on Linux®, UNIX, or Windows:
  - - db2 -tvf Rollback_<project name>_MetaData_DB2.sql
  - - db2 -tvf Rollback_<project name>_CONSTRAINTS_DB2.sql
  - - db2 -v -td@ -f Rollback_<project name>_TRIGGERS_DB2.sql
  - - db2 -tvf Rollback_<project name>_SETUP_DB2.sql
- For DB2 for z/OS®:
  - - db2 -tvf Rollback_<project name>_MetaData_ZOS.sql
  - - db2 -tvf Rollback_<project name>_CONSTRAINTS_ZOS.sql
  - - db2 -v -td@ -f Rollback_<project name>_TRIGGERS_ZOS.sql
  - - db2 -tvf Rollback_<project name>_SETUP_ZOS.sql
  Important: the SQL Setup scripts generated by the MDM Workbench for Physical MDM Development Projects typically insert new column names into tables. All versions of DB2 except DB2 for z/OS prior to version 11 permit individual column names to be dropped from a table, which means that such modifications can be easily reversed using the MDM SQL Rollback scripts. You should therefore be aware that under DB2 for z/OS, inserting new column names is a not an easily reversible operation. You can either ignore redundant column names or manually remove them. The latter option requires that data from an affected table be exported, the table itself then dropped and recreated without the redundant column names, and the data be re-imported. These steps should only be performed by experienced database administrators.
- For Oracle:
  - - sqlplus userid/password@host @ Rollback_<project name>_MetaData_ORACLE.sql
  - - sqlplus userid/password@host @ Rollback_<project name>_CONSTRAINTS_ORACLE.sql
  - - sqlplus userid/password@host @ Rollback_<project name>_TRIGGERS_ORACLE.sql
  - - sqlplus userid/password@host @ Rollback_<project name>_SETUP_ORACLE.sql