1. Database Upgrade Guide for DB2 for z/OS
  2. Executing a Siebel Migration Plan

Executing a Siebel Migration Plan

This procedure describes how to use Siebel Migration to execute a migration plan for a migration.

This task is a step in Process of Using Siebel Migration to Migrate Data.

To execute a migration plan

  1. In the Siebel Migration Application, click Execution in the navigation menu in the side panel to go to the Execution screen.

    The following table shows the information that is available for each migration plan in the Execution screen.

    Field Description Example Value

    Name

    Migration plan name

    Data Export

    Description

    Migration plan description

    Data Export Migration

    Status

    Migration plan status, which can be one of the following: Null or Running.

    Running

    Action

    Migration plan action, which can be one of the following: Run or Stop.

    Run

    Source

    Migration plan source integration branch.

    DEV

    Target

    Migration plan target integration branch.

    TEST

    Archive ID

    Migration plan archive ID. This is read-only and will be populated only for migration plans that are currently executing.

    88-1WHQVG

    Start Date

    Start timestamp for migration operation.

    2022-03-03 20:59:13

    End Date

    End timestamp for migration operation.

    2022-03-03 21:10:10

    Package Filename

    Migration plan package filename.

    TEST_2022_03_03

  2. Select the migration plan that you want to execute, and then click Run in the Action field.

  3. Click OK when prompted with the following (or similar) message: 

    Are you sure you want to execute '<Name_of_Plan>' migration plan?

  4. In the Execution Details window that appears, complete the fields as required and then click OK.

    Depending on the configuration of the migration plan that you are executing (that is, the action and resources or services selected in the migration plan), the Execution Details window will prompt you to enter different information, as follows:

    • Package Filename. Enter the name of the package file (.zip) to export or import from. This field applies only to Export Only and Import Only migration plans.

    • Watermark. Enter the name of the watermark file (.txt). This field applies to Export Only migration plans that contain Incremental Runtime Repository Data Service (IRR) or File Prepare & Deploy.

    • Workspace Branch Name and Workspace Version. These fields apply only during an Incremental Runtime Repository migration. For Export and Import (Sync) migration plans, these fields are automatically populated based on the Waternark file.

      Note: In the case of Export Only migration plans, you must click Get Workspace Details to populate the fields. The value in the Workspace Version Number field defaults to the very latest version, but you can select a different version if required. The Workspace Version Number is the range between the next version of the Target and the latest available version on the Source.

    • Database Information for Target Environment. The fields in this section apply to the following migration plans that contain a Schema Service: Import Only, Export and Import (Sync). Complete the fields in this section as follows:

      • If you have already defined the database parameters for your target connection, then enter the password of the target connection’s Database Table Owner in the DB Schema Owner Password field — all other database information in this section will be read-only.

      • If you have not already defined the database parameters for your target connection, then enter the information described in the following table.

        Note: If you have to specify the database parameters during execution of a migration plan, then the database information will be saved for the connection as well, and you will not have to specify the database parameters for any subsequent executions of the migration plan.

        Field

        Description

        DB Schema Owner User ID

        (Required) Enter the database schema owner user ID for the target connection.

        DB Schema Owner Password

        (Required) Enter the database schema owner password for the target connection.

        Tablespace for Data

        Enter the name of the tablespace on the target where you want to import the tables. This field applies to Oracle and DB2 LUW. For any other database, this value will be ignored.

        Tablespace for Index

        Enter the name of the tablespace on the target where you want to import the indexes. This field applies to Oracle and DB2 LUW. For any other database, this value will be ignored.

        Tablespace for 16k Page

        Enter the name of the 16k tablespace on the target where you want to import the tables. This field applies to DB2 LUW only. For any other database, this value will be ignored.

        Tablespace for 32k Page

        Enter the name of the 32k tablespace on the target where you want to import the tables. This field applies to DB2 LUW only. For any other database, this value will be ignored.

        Database Encoding

        (Required) Select one of the following options:

        • UNICODE Database

        • Non-UNICODE Database

  5. In the Name field, expand the '<Name_of_Plan>' migration plan to show all resource task details for the migration plan.

    The following information is available for each resource task in the migration plan: Resource Name, Operation, Seq Num, Status, Action, Log, Start Date, and End Date. For more information about these fields, see Viewing Migration Log Files.

  6. Click Refresh in the Action field of any of the resource records while the migration plan is running to refresh the migration plan and get the latest status for all resource tasks.

  7. Click Log in the Log field while the migration plan is running to view the log details for a resource task