Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Step 3. Import Metadata from the Database

Step 3. Import Metadata from the Database

To import table metadata, define a connection to the database in Enterprise Data Manager.
  1. In Enterprise Data Manager, select
    View
    Constraints
    .
    The constraints entity tree appears.
    The entity tree is organized in a hierarchy. The folder icon represents an application. In the tree, applications contain application versions, schemas, and tables. The following image shows the constraints entity tree:
    The Custom Apps Only application contains a Custom Product Family Version application version, an AIRLINE_LOYALTY schema, and TICKET tables.
  2. To expand the entity tree, double-click an application.
  3. Application versions are directly below the applications in the entity tree. Select an application version and click
    File
    Import Metadata from Database
    .
    The
    Connect to Import Metadata from Database
    window opens.
    The following image shows the connection parameters:
    The Connect to Import Metadata from Database window contains Connection Name, Database Type, Database Host, Database Port, Service Name, User Name, and Password parameters.
  4. In the
    Connect to Import Metadata from Database
    window, you can use the Connection Name parameter to select a connection that you previously defined, or you can create a connection. Configure the following parameters to create a connection:
    Database Type
    The type of database that you want to connect to.
    Database Host
    The name of the machine that hosts the source data.
    Database Port
    The port number that the source database uses.
    Service Name
    Unique identifier or system identifier for the source database server.
    User Name
    The name of the user that connects to the source database. The user is the owner of the schema that you want to run the profile on. The user must own the tables that you want to run the profile and must have privileges to select table catalogs.
    For Oracle and IBM DB2, the user name is the same as the schema name.
    Password
    The password for the database user name.
  5. Click
    OK
    .
    The
    Import Metadata from Database Wizard
    opens.
  6. Select the schemas that you want to import metadata from. Double-click a schema to move it to the
    Selected
    box.
  7. Click
    Next
    .
  8. Choose one of the following options:
    • Submit Import Metadata as a Background Job
      . Runs the job in the background. If you run the job in the background, you can continue to perform other tasks. Run the job in the background if you have a large volume of metadata to import and to avoid memory errors.
      You must run the job in the background to import metadata from SAP applications.
    • Continue Import Metadata through EDM
      . Runs the job in the foreground. If you run the job in the foreground, you must wait until the job completes to perform another task. Additionally, if you run the job in the foreground and you have a large volume of metadata to import, you might receive memory errors. You might want to run the job in the foreground if you have a low volume of metadata to import.
  9. Click
    Next
    .
  10. Select
    Update Metadata for Existing Tables
    .
  11. Click
    Finish
    .
    A message window appears that confirms that the job was successfully submitted.
  12. Click
    OK
    to close the message window.
  13. To view the status of the job, select
    Jobs
    Monitor Jobs
    in Data Archive. When the job is complete, the job status is Completed.