Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see ALTER and BMC AMI Change Manager for Db2 13.1.

Merging subsystems by using ALTER

Use the following procedures to merge subsystems by using the ALTER product with the unload and load utilities. Before you begin you should have access to the IBM documentation.

  1. Choose a Db2 subsystem’s catalog to be the original catalog for the data sharing group. For information about merging existing Db2 subsystems, see the IBM documentation. The subsystem that you select as the original will be referred to as the target, while the other subsystems will be referred to as the source subsystems.
  2. Perform the following steps for each source subsystem.

    1.  Identify objects from the other subsystems to move to the target subsystem. Determine whether name conflicts will occur when all of these objects are merged.Determine how each duplicate object will be handled. Answer the following questions:

      • Should one of them be renamed?
      • Can one set be identified as the master copy?
      • Does data from multiple tables need to be merged? If yes, identify how this will be accomplished.
      Warning

      Merging data from multiple tables can be very complex if the tables have application referential integrity.

    2. Grant system privileges of the source subsystems on the target subsystem, if they do not already exist.Resolve authorization name conflicts on all authorization types. Answer the following questions:
      • Should duplicates be eliminated?
      • Does one of the IDs need to be renamed?

    3. Create a migrate-type work ID with ALTER. The work ID name must be unique when it is received on the target subsystem. Set all of the migrate options in the work ID to Yes so that dependent objects, authorizations, and data will be migrated.Enable the buffer pools that are needed by objects from the source subsystems on the target subsystem. Buffer pool authorizations must be granted on the target subsystem. You can use migrate-type work ID change rules to change the buffer pools as the objects are migrated.

      For more information, see Creating-a-migrate-type-work-ID.

    4. Using the Specification component in ALTER, migrate the Db2 objects that were specified in Step 2.a. For more information, see Specifying-the-data-structures-in-a-migrate-type-work-ID.The dependents for an object can be omitted in either of two ways:
      • To omit all objects of a specific type, change the migrate options for an object. For example, all synonyms for a specific table can be omitted by typing the MO line command next to the table on the Mixed List panel. Set the include option for synonyms to No. This action will omit that object type and all of its dependents. If tables are omitted for a table space, the indexes, views and other dependents are also omitted.
      • To omit a specific dependent object, type the DROP command next to the dependent’s name on the Mixed List panel. This action works like an exclude in a migrate-type work ID, and that object and its dependents are excluded from the worklist.

    5. Analyze the migrate-type work ID and generate a worklist. For more information, see Analyzing-a-migrate-type-work-ID-and-generating-a-worklist.Consider the following items before analyzing the work ID:

      • You can migrate plans and packages for these objects by selecting Bind on the Analysis Worklist Command Options panel. You can also migrate plan and package authorizations by selecting Bindauth on this panel.
      • Analysis builds a worklist that contains the DDL that is needed to create these objects and their authorizations on the target subsystem. This worklist contains the utilities necessary to move the data. If the BMC utilities are available, verify that they are selected on the Analysis Utility Options panel. For more information, see Using-utilities-with-ALTER-and-Change-Manager.

      Note

      When you add OBJINFO in the Analysis ALUIN input stream, additional comments are placed in the worklist which shows the object’s original OBID, DBID, PSID, ISOBID, and data set names. This information is useful if you are going to follow the procedures in the IBM documentation to merge your catalog using the IBM DSN1COPY utility outside of ALTER or the original data sets. If you use DSN1COPY or the original data sets to merge the catalog, you must reorder the worklist.

    6. Execute phase 1 of the worklist to unload the data from the tables. For more information, see Restarting-a-worklist.
  3. Perform the following steps on the target subsystem.
    1. Create a receive-type work ID with the same name specified in Step 2.a. For more information, see Creating-a-receive-type-work-ID.
    2. Execute phase 2 of the worklist to create the objects on the target subsystem, run the utilities, and bind the packages and plans. See Restarting-a-worklist.
  4. Repeat Step 2 and Step 3 for the other source subsystems.

Related topic

Accomplishing-your-maintenance-goals


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*