1. Data Selection Tool How-to Guide
  2. Migrating Network Templates

6 Migrating Network Templates

This chapter describes how to migrate information with Oracle Communications MetaSolv Solution Data Selection Tool (DST) Network Templates module.

About Network Templates Migration

The DST Network Templates module migrates the network templates and requires the following information to be set up in the source database and the target database by the database administrator who has SYSDBA privileges.

To set up the database for migrating templates:

  1. Create Database links using the following statements:

    CREATE DATABASE LINK SRC_DB_LINK CONNECT TO ASAP IDENTIFIED BY "ASAP_Password" using '(DESCRIPTION= Description (CONNECT_DATA=(SERVICE_NAME=Service_name)))'

    where

    • ASAP_Password is the password for the ASAP user.
    • Description is the value that you get from the following statement:

      select value from v$listener_network where type = 'LOCAL LISTENER';

    • Service_name is the value that you get from the following statement:

      select value from v$listener_network where type = 'SERVICE NAME';

  2. Run the pkgdstnst.sql using the ASAP user from the path/procs/ directory where path is the temporary folder where you extracted the contents of the DST.zip file. For example, c:/DST/procs.

  3. Grant the following database permissions to all the users who use the Network Templates module in the Data Selection Tool:

    Connect to the source database and the target database as database administrator with SYSDBA privileges.

    GRANT SELECT ON V_$LISTENER_NETWORK TO user;

    GRANT CREATE DATABASE LINK TO user;

    GRANT SELECT ANY TABLE TO user;

    GRANT EXECUTE, DEBUG ON ASAP.PKG_NST_MIGR TO user;

    where user is the user who will migrate the network templates in DST.

The DST Network Templates module migrates the following information related to the selected network templates:
  • Network Templates
  • Embedded Network Templates
  • Component Types
  • Network Element Types for the Component Types
  • Connection Specifications that exist in the source database and the target database
  • Custom Attributes and their valid values that exist in the source database and the target database
  • Service Applications that are defined in the source database and the target database

The DST Network Templates module does not migrate the following information:

  • Connection Specifications that do not exist in the target database
  • Custom Attributes with their valid values that do not exist in the target database and are associated with Component Types and Network Templates
  • Service Applications that do not exist in the target database
  • Custom Attributes and their valid values for the Connection Specifications

Migrating Network Templates

To migrate network templates:

  1. Click the Net Templ button.

    Note:

    If the Source list is empty, your source database does not contain any network templates.

  2. Click the Targ Logon button to select the target database. The target database is the one you want to copy network templates to.

    The Environment Login window is displayed.

  3. In the Userid field, enter your user name.

  4. In the Password field, enter your password.

  5. In the Database field, enter the database server name.

  6. Click OK.

    Note:

    Your database access is limited to accessible databases in your .TNS names files and your .INI files.
    After you connect to your target database, the Target list is populated with the network templates in the target database.

    Note:

    If you click the Pick Templ... button before you choose a target database, an error message is displayed. Click OK and then click the Targ Logon button.

  7. Click the Pick Templ... button.

    The Network Templates Query window is displayed that allows you to select the network templates you want to migrate.

  8. Enter your search criteria and click Retrieve.

    The list of network templates is displayed on the Results tab.

  9. Select the network templates you want to migrate and click Migr Temp....

    The Migrating Network Templates progress meter displays, showing you the progress of migrating the selected templates.

  10. After the network templates migration process is complete, review the migration log to ensure that the selected network templates are migrated successfully.

    Note:

    If you receive ORA-02019 : connection description for remote database not found in the migration log, consult your Database Administrator that the Database links are created successfully.
    The following network templates are displayed with the Cancelled status in the Migration Log:
    • The network templates that already exist in the target database.
    • The embedded network template(s) that already exist in the target database with a different template type.
    • The connection specifications in the selected network template or any of its embedded network templates that do not exist in the target database. To successfully migrate the network template, log in to MetaSolv Solution of the target database and create the connection specifications.
    • The connection specifications in the selected network template or any of its embedded network templates that are associated with service applications and those service applications that do not exist in the target database. To successfully migrate the network template, log in to MetaSolv Solution of the target database and create the service applications.

  11. To validate that the network templates migrated properly to the target database, click the Net Templ... button on the main toolbar, and then click the Targ Logon button to refresh the information that is displayed for the target database.

Post-Migration Tasks

After the migration process is completed, you must do the following post-migration tasks:

  • In MetaSolv Solution application, in Network Templates window, ensure that :
    • The correct image is associated with the component types, if the migrated network templates has component types that already exist in the target database.
    • The appropriate custom attributes are associated with the network templates and component types. You must manually validate and associate the custom attributes with the connection specification.
  • In MetaSolv Solution Utilities,
    • Ensure that the custom attribute rules and the layout are defined appropriately. The layout details includes Display line number, Display Column number, and Label Placement.
    • If there is a warning message in the migration log, create and associate the custom attributes to the network templates or the component types. A warning message is logged when any of the custom attributes associated with the selected network templates or component types do not exist in the target database. The corresponding network templates or the component types are migrated without the custom attributes.