Methods to define the scope of a migration

You can define the scope of a migration either by using an outbound migrate profile or by explicitly specifying data structures.

See the following information in this topic:

• • Outbound migrate profile method
  • Specified data structures method
  • Identification of changes to data structures

Outbound migrate profile method

In an outbound migrate profile, you use scope rules and migrate options to define the set of data structures and the dependencies of those data structures to include in the migration.

Use the following guidelines when you create scope rules:

• In BMC AMI Change Manager for Db2, stored procedures are not dependent upon any other Db2 object. Thus, when you create a scope rule for an object that is modified by a stored procedure or that calls a stored procedure, you cannot include the stored procedure as a dependency. To include stored procedures in the scope, you must specify them explicitly.

• Auxiliary objects for a LOB column are dependent upon databases, table spaces, and tables.

  • If you select a database or a table space object, you must include the dependent tables or auxiliary objects.
  • If you select a table object, you must include the dependent auxiliary objects.

  To migrate auxiliary objects for a LOB column, migrate the auxiliary objects and the base table.

• Authorizations are the only dependency on sequence objects.
• To include the parent objects of tables in the scope, include the dependent database and table space. If the parent object is an implicit object, Change Manager ignores the object.

Specified data structures method

If you do not define the scope of a migration by using an outbound migrate profile, you can define the scope in a work ID by specifying the names of the data structures that you want to appear in a mixed list.

From the mixed list, you can specify the objects that you want to migrate for a migrate-type work ID. The following figure shows an example of a mixed list. The list displays different types of Db2 data structures.

The objects in a mixed list are displayed in hierarchical order by object type. For example, table spaces that are associated with a database appear under the database, as do the tables that are associated with a table space. The products retrieve data that can use any encoding scheme from the Db2 catalog. When the products execute SQL that uses an ORDER BY clause against the Db2 catalog, the query uses a Unicode collating sequence to sort data and typically uses the same sequence to display the data on panels and in reports. However, when the products sort the data retrieved from the Db2 catalog queries, the products display sorted data on panels and in reports in an EBCDIC collating sequence.

List of Db2 data structures

For object-type abbreviations that Specification uses in the Mixed List panel and for the data types for the object names, see Command-and-syntax-reference.

In Change Manager, stored procedures and sequences are not dependent upon any other Db2 object and are displayed in the Unattached Objects section at the end of the mixed list (as shown in the following figure).

As a result, if you want to migrate stored procedures that read or modify another object or that are called by another object, you must explicitly specify the stored procedures for the migration. Orphaned auxiliary indexes, which are auxiliary indexes that are not associated with an existing auxiliary table, are also displayed in the Unattached Objects section. (Orphaned auxiliary table spaces, however, are displayed in the hierarchy.)

You can use the FIND and ZOOM commands in the mixed list to find specific data structures and the dependents for those data structures.

• You can use the FIND command to quickly locate a specific data structure. Type FI on the Command line and specify a character string on which to search. For example, you can type FI EMP and press Enter. The cursor displays at the first occurrence of a match.
• You can use the ZOOM command in the Mixed List panel to list all of the dependents for an object in a hierarchical fashion. Type Z in the Act column adjacent to the object that you want to zoom. ZOOM displays all of the dependent objects, which includes dependent materialized query tables (MQTs).

You can use action codes (or Command line commands) on the mixed list to indicate the type of action that you want to perform. Some of the actions that you can perform are described in The following table.

You can also use the following command-line commands on a mixed list:

• (Migrate-type work ID only) MIGALL marks all of the data structures, except auxiliary objects, for migration. To migrate the associated auxiliary objects for a table, you must select tables and auxiliary objects from the Migrate Options Overrides panel. You cannot migrate orphaned auxiliary objects.
• DROPALL excludes all of the data structures that are marked for migration from being included in the migration. This command is the equivalent of typing D in the Act column for all data structures.
• UNDOALL reverses the action on all data structures. This command is the equivalent of typing U in the Act column for all data structures.

When you indicate the type of action that you want to perform, consider the following information:

• You can migrate auxiliary objects for a LOB column by migrating the base table that contains the LOB column and including auxiliary objects as dependents. To include the auxiliary objects as dependents, you must use the MO command on the base table, and then type Y adjacent to Migrate Tables and to Migrate Auxiliary Objects on the Migrate Options Overrides panel.You cannot edit, like, or drop auxiliary objects for a LOB column in a mixed list.

  Success

  Tip

  To migrate auxiliary objects for a LOB column, see Migrating-the-auxiliary-objects-for-a-LOB-column.

• To exclude a dependent object or an auxiliary table or index from a migration, type D in the Act column adjacent to the object. For example, if you want to migrate a database and all of its dependent objects except for one table space, type D in the Act column adjacent to the table space. The table space is excluded from the migration.
• You can create, like, edit, and drop external stored procedures and native SQL stored procedures.

For more information about the commands that you can use in a mixed list, see Command-and-syntax-reference.

Identification of changes to data structures

When you specify a change to an object, an asterisk (*) and a change-level indicator appears on a list panel adjacent to the Act column.

The M change-level indicator signifies that you selected to migrate an object. This indicator is not applicable to auxiliary objects.

When you request a change to a data structure, only the definition of the data structure and the requested changes are saved in the Change Definition (CD) tables. The specified changes do not occur in the Db2 catalog until you analyze the changes, generate a worklist, and execute the worklist.