Tips for More Efficient Cloning

When you first run dbutility define to populate the client control tables, you will notice that most DMSII data sets are set to be cloned. Although you can accept the default data sets and their items for cloning, note the following:

• Cloning an entire DMSII database can take several hours or more. Typically, most sites do not clone entire DMSII databases.
• The cloning of the DMSII restart data set is automatically disabled. The restart data set is related to restarting the DMSII database only.
• If you clone virtual data sets, do not disable the cloning of the data sets from which the virtual data set is derived. (Virtual data sets have a value of 17 in the subtype column of the DATASETS table.) Virtual data sets are created on the host and are explained in the DATABridge Programmer’s Reference.
• Make sure that you have enough disk space on the relational database server for the DMSII data. If there is not enough room, the cloning process stops. In addition to the space required for DMSII data, you must have some additional file space for the temporary files used by the bulk loader utilities (bcp for Microsoft SQL Server; SQL*Loader for Oracle).
• You do not have to clone all of the data sets at one time. One approach is to clone the most essential data sets and then determine how much space is still available.
• If you do not want to clone secondary tables (those tables generated from a data set), you have two choices. In either case, the primary table is still generated, while the resulting secondary tables are not.
  • Set the value of the active column (for that table) in the corresponding DATATABLES client control table entry to 0 (script.user_define.primary_tablename).
  • Set the value of the active column in the corresponding DMS_ITEMS client control table entry to 0 for an item with an OCCURS clause (script.user_layout.primary_tablename).
• If the active columns for all tables related to a data set are 0, DATABridge sets the active column of the corresponding entry in the DATASETS table to 0.a set and then set up a view in the relational database to achieve the same result as the remap. If you do want to clone a remap of a data set instead of the base data set, you can do so by changing the values of the active columns of the data sets in the DATASETS client control table. You can identify remaps by their base structure number (base_strnum). For example, if structure numbers (strnum) 11, 121, and 227 are remaps of structure number 10, the base structure number for structures 11, 121, and 227 is 10. For data sets that are not remaps, the strnum and base_strnum columns are equal.
• The cloning of DMSII remaps is automatically disabled because the remaps are just different views of the base data sets; the DATABridge Client assumes that the base data set will be cloned. It is recommended, therefore, that you clone the base datIf you do not want to clone anything related to a particular data set, set the value of the active column (for that data set) in the corresponding DATASETS client control table entry to 0. No tables (primary or secondary) are generated from this data set.