This chapter explains how to migrate to Oracle Data Quality 11g from Oracle Data Quality 10g. Specifically, this chapter describes the following steps required to upgrade Oracle Data Quality products:
Before you begin the upgrade process, review the following sections to ensure that you have performed all of the required pre-upgrade tasks:
Any Oracle Data Quality repository, residing on a platform supported under the Oracle Data Profiling and Quality version 10.1.3.5.0 hardware requirements, can be migrated to the Oracle Data Quality 11g version as long as the following conditions are met:
The existing repository must reside on the same server as Oracle Data Quality 11g
The existing repository must be compatible with the Oracle Data Quality 11g server.
Oracle recommends that you create a backup copy of the entire ORACLE_HOME/oracledq/metabase_data directory before you upgrade.
For installation steps, refer to the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.
If the existing repository is not installed on the same server as Oracle Data Quality installation, copy the entire repository directory to the new Oracle Data Quality 11g installation server (this includes all E<n> directories). Make sure that the two servers are running the same operating system.
For Example:
If you have an Oracle Data Quality 10.1.3.5 repository residing in the ORACLE_HOME/oracledq/metabase_data directory on a server named oracle1 and your Oracle Data Quality 11g installation is on a server named oracle2, you need to copy the entire repository directory ORACLE_HOME/oracledq/metabase_data (including subdirectories) from oracle1 to a temporary location on oracle2.
When you migrate an existing repository to an Oracle Data Quality 11g server, everything is migrated except for bookmarks.
The target repository must not contain any user-defined metabases, users, or loader connections. (Verify that the Oracle Data Quality 11g repository only contains the _control metabase.) Although the migration process alerts you if any of these items exist, Oracle recommends that you check the repository before beginning the migration process.
Caution:
Only perform these steps on the Oracle Data Quality 11g Repositories.Log on to the ODP/ODQ Metabase Manager as the metabase administrator (for example, madmin).
From the Explorer pane, expand the Control Admin folder.
From the Explorer pane, double-click Metabases.
The List View pane displays a list of all metabases defined in the repository. If there are metabases other than the _control metabase listed, you must delete them before migrating your metabases.
Select the first user-defined metabase, right-click, and select Delete...
Repeat step 4 until all metabases (except _control) are deleted.
From the Explorer pane, double-click Users.
The List View displays a list of all users defined in the repository.
In the List View, select all users except the metabase administrator.
Right-click and select Delete...
From the Explorer pane, double-click Loader Connections.
The List View displays a list of all loader connections defined in the repository.
In the List View, highlight all loader connections.
Right-click and select Delete...
The following steps are used to upgrade Oracle Data Quality repositories.
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.
Open a command line shell.
From the command line, change directories to ORACLE_HOME/oracledq/metabase_server/bin.
At the prompt, type on 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 Section 8.1, "Update Metabase Connections".