Oracle® Fusion Middleware

2.1 Components of the Oracle Data Quality 11g Release 1 Installation

If you are upgrading your Oracle Data Quality products from 10g Release 3 to 11g Release 1, there are some significant changes you should be aware of. This section describes those changes.

The Oracle Data Profiling and Data Quality 10g Release 3 (10.1.3) default installation provided the following components:

• Oracle Data Integrator

• Oracle Data Profiling

• Oracle Data Quality for Data Integrator

Oracle Fusion Middleware 11g provides updates to all these components, but not in a single installation. In Oracle Fusion Middleware 11g, your Oracle Data Profiling and Oracle Data Quality components are packaged and installed separately, but they still provide the same resources and services.

Oracle Data Profiling and Oracle Data Quality for Oracle Data Integrator 11g Release 1 (11.1.1) provides the following components:

• Oracle Data Profiling and Data Quality Client User Interface

  The Oracle Data Profiling and Oracle Data Quality user interface is available for Windows 32-bit operating systems only. This client can be configured to connect to a Metabase Server installed on a separate machine.

• Oracle Data Profiling and Quality Server

  The Oracle Data Profiling and Quality server installation includes the following components:

  • Metabase Server

    The Metabase Server contains the profiling data and metadata.

  • Data Quality Server (Windows 32-bit operating system only)

    The Data Quality Server is the run-time component for Oracle Data Quality processes.

  • ODBC Server (Windows 32-bit operating system only)

    Oracle Data Quality ODBC Adapter is used to connect ODBC data sources. This optional component can be installed on Windows platforms only.

3.1 Preparing to Upgrade

Before you begin the upgrade process, review the following sections to ensure that you have performed all of the required pre-upgrade tasks:

• Task 1: Understand the Supported Upgrade Starting Points

• Task 2: Backup the Existing Repository

• Task 3: Install Oracle Data Profiling and Oracle Data Quality for Data Integrator

• Task 4: Copy the Existing Repository to the Oracle Data Quality Server

• Task 5: Remove User-Defined Metabases and Users

3.2 Oracle Data Quality Upgrade Instructions

The following steps are used to upgrade Oracle Data Quality repositories.

1. Log on to the metabase server with an administrator account.

   Oracle recommends that you do not use a remote server to migrate your existing repository.

2. Open a command line shell.

3. From the command line, change directories to ORACLE_HOME/oracledq/metabase_server/bin.

4. At the prompt, type one of the following commands on a single line and then press Enter.

   • On UNIX operating systems:

     ./mtb_admin -user <Metabase Administrator User Name> -password <Metabase
     Administrator User Password> -level INFO -migrate repository "<Existing
     Repository Path>" ddl upgrade.ddl
     

   • On Windows operating systems:

     mtb_admin -user <Metabase Administrator User Name> -password <Metabase
     Administrator User Password> -level INFO -migrate repository "<Existing
     Repository Path>" ddl upgrade.ddl
     

   In the commands above:

   • <Metabase Administrator User Name> corresponds to the metabase Admin user name (for example madmin)

   • <Metabase Administrator User Password> corresponds to the metabase Admin user password

   • <Existing Repository Path> corresponds to the /metabase sub-directory of the directory into which the repository was copied.

   The migration command processes the entities in the metabase, and reports its progress. For example:

   …
   Converting entity 30 table “mask”
   Converting entity 30 table “metaphone”
   Converting entity 30 table “pattern”
   …
   

The time required for the migration is comparable to the time it took to originally load the data into the original metabase(s). Your existing repository is left untouched after the migration. When the migration ends, it displays information and recommendations. For example:

ODBC loader connection “odbc” must have its PORT updated
Don't forget to migrate entity sources using the "updateentitysource",
“updateconnection” or "updateallconnections" commands
Press any key to continue. . .

If you received a message at the end of your migration to update a loader connection port (for example ODBC loader connection “odbc” must have its PORT updated), connect to the metabase administrator and edit the loader connection to update the connection port.

To migrate entity sources, see Task 1: Update Metabase Connections.

4.1 Task 1: Update Metabase Connections

The following commands allow you to update your loader connections after migrating the repository:

• updateconnection - updates the details of a specific connection

• updateallconnections - updates the details of all migrated connections

Oracle recommends using the updateconnection command to update your migrated loader connections.

To update the metabase connections:

1. Start the Metabase Server Administrator Prompt

   • On UNIX operating systems:

     ./mtb_admin
     

   • On Windows operating systems:

     Select Programs > Oracle > Oracle Data Profiling and Quality > Metabase Server >Administrator Command Prompt from the Start menu.

2. When prompted, supply your username, password, and metabase name.

   Use the _control metabase name.

3. Enter one of the following commands:

   • To update a specific migrated connection in all the metabases:

     updateconnection <connection name>
     

   • To update all migrated connections in all the metabases.

     updateallconnections
     

4. Respond to the system prompts by typing a new value and pressing Enter. To keep the current value, press Enter at the prompt.

   After you respond to all the prompts, the command locates the specified connection in all the metabases and updates them with the new information.

   Example of a connection update:

   1. Start the Metabase Server Administrator and log on to the _control metabase:

      /.mtb_admin -user madmin -password ***** -metabase _control
      

   2. At the _control prompt, enter the updateconnection command and press Enter:

      updateconnection myconnection
      

      The following prompt appears:

      Please enter the connection description. Just enter for the original“this is my connection”>
      

   3. Press Enter to use the same description, or type a new description and then press Enter.

      The following prompt appears:

      Please enter the path to data files. Just enter for the original“/data/data”>
      

   4. Press Enter to use the same path, or type a new path and then press Enter. The following prompt appears:

      Please enter the path to the schema files. Just enter for the original“/data/schemas”>
      

   5. Press Enter to use the same path, or type a new path and then press Enter. The following message appears:

      Successfully updated loader connection
      Updating entities in metabase "demo"
      username>
      

   6. Respond to the prompts for your username and password. Progress messages appear as the command updates the connections named myconnection in each metabase. For example:

      Successfully updated entity 11
      Successfully updated entity 12
      Successfully updated entity 13
      Successfully updated entity 14
      Updating entities in metabase "oracledq"
      Successfully updated entity 1
      _control:
      

4.2 Task 2: Validate the Upgrade Operation

Start Metabase Manager and verify that your metabases and loader connections are available in the Control Admin pane.