Managing Db2 for z/OS databases before upgrading IBM Engineering Lifecycle Management
Each new Engineering Lifecycle Management (ELM) version or release updates the data model to change the database schema for Jazz® Team Server and the ELM applications by using the repository tools addTables command. The upgrade process tags the repository with a version and release number, which means that it can be used only with that version and release. You must ensure that you have adequate backups for the tables in case there is an error and you must roll back the data. In addition to any tools you might have, IBM also provides tools for using Db2 for z/OS UNLOAD and LOAD to create a backup copy. It is important to understand that just generating the DDL from the existing tables and loading the current data into them might not be sufficient, as the repository tools -createTables process creates the tables, inserts data into some tables, and establishes links between tables. Table owner names might be different between instances of the database.
About this task
It is critical that the backup and restore process for the data is understood and tested before any upgrade. Testing the backup and restore process also creates a set of duplicate tables that can be used to test the upgrade process itself, preferably in a separate subsystem.
The upgrade cannot be rolled back without a repository backup.