How to Migrate DB2 Objects › View DB2 Object Relationships

View DB2 Object Relationships

The Visualizer in CA Chorus provides a pictorial view of your CA Chorus for DB2 Database Management DB2 catalog objects in your system and their relationships. Labeled shapes identify each object, and lines connect objects to show parent-child relationships. Each shape symbolizes a different object type. Each object appears with text to indicate the object type and object name. For example, a table space appears as a square with the words Table Space: SYSDDF. This functionality lets you quickly see the object type and identify the object name. This view can simplify your ability to identify relationships as you manage your data because the pictorial view can be easier to read than a tabular view. You can also drill down to isolate data within your system. The Visualizer provides a better understanding of the DB2 object relationships before you migrate changes and can help when you are performing the following tasks:

• Troubleshooting
• Taking inventory of your system
• Identifying migration sources

  You can launch the Visualizer for any row of object data in the catalog of the Investigator. You cannot display application performance or subsystem performance activity in the Visualizer.

Note: This task is not required to migrate DB2 objects. However, we recommend that you view the object relationships before proceeding with a migration. Viewing the object relationships provides a clear understanding of the relationships between the objects to help determine the possible impact of the migration before it occurs.

Follow these steps:

1. Log in to CA Chorus. Your user ID must have CA Chorus for DB2 Database Management privileges.
2. Add the Investigator to your workspace from the Module Library.
3. Click Start New Investigation.
4. Click DBA for DB2 from the role drop-down list.
5. Navigate to the DB2 catalog object (storage group, database, table space, table, index, or view) that you want to migrate, and highlight one or more rows of data.

   The Actions pane opens.

6. Select Add to Visualizer under Navigation in the Actions pane.

   The Visualizer opens and displays your data pictorially. The default view is hierarchical. Use the toolbar at the top of the Visualizer pane to customize the view. The header displays the system name to which the selected object belongs.

7. Find the object that you want to evaluate using the search options. Hide unrelated objects using the Visualizer Actions to provide a better view.

   After you have a clear understanding of the DB2 object relationships, proceed with the next step in the migration.

Example: Visualize Objects in the ADMNUSER Table

A DBA often must find the family of objects that relate to a table (that is, the database name, table space name, indexes, and views). With the CA Chorus for DB2 Database Management role, you can log in to a central web browser and access all systems across multiple LPARs. Not only one LPAR as is the case with the 3270. In the following example, the DBA is trying to identify the objects that are associated with the ADMNUSER table in the DA0G subsystem. This information is especially useful for troubleshooting and planning exercises.

To visualize table data, complete the following steps:

1. Launch the Investigator module, and click Start New Investigation.
2. Enter the subsystem name in the tree search area. As you start typing letters, the tree filters to the applicable subsystem.
3. Select the Catalog to display its contents.
4. Select the Table folder.
5. Enter your filter criteria, and click Filter.
6. Select the applicable table row, and click the Visualize Action in the right pane.

   The Visualizer opens, loads, and displays the objects that are related to the ADMNUSER table. In this case, the table has two index children. Additionally, the table is part of a table space, which is part of a database and storage group.