Reconfiguring a Family of Extracts
- Last UpdatedMar 18, 2022
- 1 minute read
When reconfiguring a whole extract family, the following considerations apply:
-
The REVERT/MERGE operation must be done bottom-up, to minimize the number of sessions kept.
-
Reconfiguring from Database (DB) to files must be done top-down.
-
Reconfiguring back from files to DBs must also be done top-down, and the administrator must complete the reconfiguration for the whole extract. For example, if the administrator reconfigures all three DB levels of a three-level extract to files but only reconfigure the top two file levels back to DBs, the third DB will be corrupted due to the reconfiguration of the other two. For further information, refer to Section Example of Reconfiguring a Three Level Extract.
-
Before reconfiguring out from a file, refresh the extract.
-
Before reconfiguring in from a file, the extract must be refreshed from its parent.
Example
Given a simple two-level extract containing TEAMA/MASTER, TEAMA/EXTRACT, the sequence would be:
-
Refresh TEAMA/EXTRACT.
-
Reconfigure TEAMA/MASTER to file /A, /B.
-
Reconfigure TEAMA/EXTRACT to file /C, /D.
-
Use REVERT TEAMA/EXTRACT to revert to Session 1.
-
Use MERGE CHANGES on TEAMA/EXTRACT.
-
Use REVERT TEAMA/MASTER to revert to Session 2.
-
Use MERGE CHANGES on TEAMA/MASTER.
-
Reconfigure from file /A, /B to TEAMA/MASTER.
-
Refresh TEAMA/EXTRACT (to pick up changes made in Step 8).
-
Reconfigure from file /C, /D to TEAMA/EXTRACT.