Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Data Profiling and Oracle Data Quality for ODI
11g Release 11.1.1

Part Number E16587-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Installing Oracle Data Profiling and Oracle Data Quality

This chapter describes how to install and configure Oracle Data Integrator. Post-installation configuration parameters are also provided.

The following topics are covered:

2.1 Preparing to Install

Review the information in this section before you begin:

2.1.1 Review System Requirements and Certification

Before installing any Oracle Data Quality products, you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements. Both of these documents are available on Oracle Technology Network (OTN).

The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

The certification document covers supported installation types, platforms, operating systems, databases, and third-party products:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

2.1.2 Define User Accounts

Oracle Data Quality products rely on multiple users to perform certain procedures (as defined in Table 2-1). You create the Oracle Data Quality users during and after the installation procedure. You define the UNIX operating system users before you install Oracle Data Profiling and Oracle Data Quality for Oracle Data Integrator.

Table 2-1 Required User Accounts

User Description

root (for UNIX operating systems)

Or:

winadmin (for Windows operating systems)

Some procedures must be performed by an operating system user with root or super user access. When you enter a root password during the software installation, xinetd.conf (for UNIX operating systems) or inetd.conf (for Windows operating systems) is updated to allow the correct processes to be called between the UNIX system and Oracle Data Quality software.

See your operating system documentation for more information on these user types.

Oracle Data Quality Application Administrator

An operating system user who installs the Oracle Data Quality Server application and administers the Oracle Data Quality Scheduler and License Manager. (This user is required when installing on either Windows operating systems or UNIX operating systems.)

For information on creating this user, see Section 2.1.2.1, "Define an Oracle Data Quality Application Administrator".

Oracle Data Quality Loader User

User who will access data import directories (located on the Oracle Data Quality server) through a login screen in the Oracle Data Quality User Interface. This user is not required if you plan to directly access data from relational sources (Oracle, IBM DB2, ODBC). You will, however, need a user id that gives you access to each specific database.

NOTE: This user is only required if you plan to load data from flat file sources (delimited, COBOL, Oracle Data Quality sources).

For more information on creating this user, see Section 2.1.2.2, "Define Oracle Data Quality Loader Users".

Metabase Administrator

Oracle Data Quality user account that creates and maintains Oracle Data Quality repositories, and defines metabases, Oracle Data Quality users, and data connections. This user is also known as the Oracle Data Quality Repository User.

NOTE: The metabase administrator is created during Oracle Data Quality installation.

Oracle Data Quality User

Oracle Data Quality user account that accesses Oracle Data Quality metabases through the Oracle Data Quality User Interface

NOTE: Oracle Data Quality users are created by the metabase administrator after installation.


2.1.2.1 Define an Oracle Data Quality Application Administrator

You must create an Oracle Data Quality Application Administrator and, if you are using sudo, you must also grant sudo rights before installing Oracle Date Quality products. This administrator installs the server application and administers the Scheduler and License Manager on the Oracle Data Quality server.

To create an Application Administrator on UNIX Operating Systems:

  1. As the UNIX root user, create an Oracle Data Quality administrator user account to perform Oracle Data Quality administrative activities.

    There are no naming restrictions for the Oracle Data Quality administrator name, but the recommendation is that the user account be named odqadmin.

  2. Do one of the following:

    • If you are not leveraging the security provided through sudo, make sure that the Oracle Data Quality administrator has read access to any data import directories that you define. Proceed to "Define Oracle Data Quality Loader Users".

    • If you are leveraging the security features of sudo, proceed to the next step.

  3. As the UNIX root user, type the command: visudo. This brings up the file named sudoers for editing.

    NOTE: You must always edit this file through the visudo command.

  4. In the Defaults specification section, add the following entries:

    Defaults:<user_id> targetpw
    Defaults:<user_id> passwd_tries=1
    Defaults:<user_id> timestamp_timeout=0
    
  5. In the User Privilege specification section, add:

    <user_id> ALL=(ALL) ALL
    
  6. Save the file and exit.

  7. Verify that sudo is correctly configured.

    1. Log in as the newly created Oracle Data Quality administrator. For example, type:

      sudo -u odqadmin id
      
    2. When prompted, enter the password for the user.

    3. Type the command: id

      The operating system should return the UNIX user id. If not, contact your system administrator.

To create an Application Administrator on Windows Operating Systems:

  1. As the Windows Server Administrator, create a Windows user account for the Oracle Data Quality Administrator.

    There are no naming restrictions for the Oracle Data Quality administrator name, but the recommendation is that the user account be named odqadmin.

  2. Add the Oracle Data Quality Administrator user odqadmin to the group Administrators.

  3. From the Windows Control Panel, open Administrative Tools, Local Security Policy and expand the Security Settings > Local Policies folder.

  4. Add the Oracle Data Quality Application Administrator user odqadmin to the following options:

    • Log on as a Service

    • Act as part of the operating system

2.1.2.2 Define Oracle Data Quality Loader Users

Define an Oracle Data Quality Loader User account on the UNIX server if you plan to import data from flat files. When you import flat file data into Oracle Data Quality, you access the file location on the server through a UNIX user id.

For example, if you are importing flat files described by COBOL copybooks that are residing on the Oracle Data Quality server in the directory /data, then you require an Oracle Data Quality Loader User (UNIX user id) who can log on to the Oracle Data Quality server and read the files from /data.

Note:

If you intend to import data directly from a relational source, you do not need to perform these steps since a UNIX userid is not required. The only user required is for RDBMS login access
  1. Define a new user account or select an existing user account to act as an Oracle Data Quality Loader User.

    NOTE: For Windows operating systems, determine whether you will create a single user account that the team will share or if each user will have their own user account.

  2. Give the account read access to the data import directory that you plan to use when you create a Loader Connection.

    NOTE: For Windows operating systems, add each user account (that will access the flat file data) to the appropriate Windows user group for each secured location. User accounts not contained in the Windows group will not be able to import flat file data for that loader connection.

2.1.3 Identify Available Ports

During installation you must provide at least 2 port numbers that are accessible from the client to the server and are not blocked. These port numbers are used for the following services:

  • The Oracle Data Quality Scheduler requires a port called Scheduler Port.

  • The Oracle Data Profiling and Quality Metabase Repository requires a port called Repository Port.

Note:

If you are planning to use ODBC datasources from a Windows-based server, you will need to reserve a third port for the Oracle Data Quality ODBC Adapter.

To identify ports that have applications listening on them, type the netstat -an command. Select two available ports and make note of them for the setup procedure.

Note:

The port numbers should be greater than 1000 and not exceed 65535, and for easy reference, should be consecutive numbers. (For example, 7600 for the Repository Port and 7601 for the Scheduler Port.)

2.2 Installing Oracle Data Quality Products

This section contains information and instructions for installing Oracle Data Integrator:

2.2.1 Starting the Installer

To start the installer, insert the Oracle Data Quality installation disk or navigate to /Disk1 in the ODQ installation directory (where you saved the ODQ .zip or .jar file) and run the following command:

  • On UNIX operating systems:

    ./runInstaller
    
  • On Windows operating systems:

    setup.exe
    

Refer to the Oracle Fusion Middleware Certification document to see the JDKs supported for your system: http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

2.2.2 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):

  • Linux operating systems: /etc/oraInst.loc

  • HP-UX and Solaris operating systems: /var/opt/oracle/oraInst.loc

  • Windows operating systems: \Program Files\Oracle\Inventory\logs

2.2.3 Installing on UNIX Operating Systems

The Oracle Data Profiling and Quality installation for UNIX operating systems includes the following components:

  • Oracle Data Quality for Data Integrator

  • Metabase Server

  • Metabase Definitions

Table 2-2 describes the screens included in a UNIX operating system installation. For more information, see Appendix B, "Oracle Data Profiling and Data Quality Installation Screens".

Table 2-2 UNIX Operating System Installation Flow

No. Screen When Does This Screen Appear? Description and Action Required

1

Welcome

Always

Click Next to continue.

2

Prerequisite Checks

Always

This screen analyzes the host computer to ensure that specific operating system prerequisites have been met.

If any of the prerequisite checks fail, then a short error message appears in the bottom portion of the screen. Fix the error and click Retry to try again. If you want to ignore the error or warning messages and continue with the installation, click Continue.

Click Abort to stop prerequisite checking for all components.

3

Specify Installation Location

Always

In the Location field, enter the Oracle home (referred to in this guide as ODQ_HOME) where your products will be installed.

Click Next to continue.

4

Metabase Server Details

Always

This screen configures the Metabase Server.

Provide the required information and click Next to continue.

5

Installation Summary

Always

Review the summary and click Install to continue.

6

Configuration Progress

Always

The installer automatically executes each configuration assistant in sequence, displaying the progress in the Status column.

No action is required on this screen.

7

Installation Completed

Always

If you want to save this configuration to a text file, click Save. This file can be used later if you choose to perform the same installation from the command line.

Click Finish to close the installer.


2.2.4 Installing on Windows Operating Systems

Table 2-3 describes the screens included in a Windows operating system installation. For more information, see Appendix B, "Oracle Data Profiling and Data Quality Installation Screens".

Table 2-3 Windows Operating System Installation Flow

No. Screen When Does This Screen Appear? Description and Action Required

1

Welcome

Always

Click Next to continue.

2

Select Components Screen (Windows Operating Systems Only)

Always

Select the components you want to install. The options are:

  • 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 a Metabase Server, Data Quality Server (Windows 32-bit operating system only), and an ODBC Server (Windows 32-bit operating system only).

Click Next to continue.

3

Prerequisite Checks

Always

Click Next to continue.

4

Specify Installation Location

Always

Specify the absolute path to your Oracle home (referred to in this guide as ODQ_HOME).

Click Next to continue.

5

Metabase Server Details

Always

This screen configures the Metabase Server.

Provide the required information and click Next to continue.

6

Metabase Client Details (Windows Operating Systems Only)

Only if you selected Metabase Client on the Select Components Screen (Windows Operating Systems Only) screen.

This screen configures the client to connect to the Metabase and ODBC Servers.

Provide the required information and click Next to continue.

7

Installation Summary

Always

Review the summary and click Install to continue.

8

Configuration Progress

Always

The installer automatically executes each configuration assistant in sequence, displaying the progress in the Status column. No action is required on this screen.

9

Installation Completed

 

If you want to save this configuration to a text file, click Save. This file can be used later if you choose to perform the same installation from the command line.

Click Finish to close the installer.


2.3 Installing Additional Postal Tables

The postal tables are a critical part of the data quality process because they provide the postal information that is used to validate and improve the name and address data in your records. This section describes how to install postal and census directories for for an Oracle Data Quality Server.

2.3.1 Postal Table Naming Conventions

The postal tables and census/DPV directories are delivered in a compressed format. The file extensions are .zip (for Windows operating systems) and .tar (for UNIX operating systems).

Table 2-4 describe the file naming conventions that are used:

Table 2-4 Naming Conventions

Table or Directory Name Naming Convention Used

General and Asian Postal Tables

XXMMMq.ext, where XX is the 2-letter country code, MMM is the abbreviation for the month the postal table was issued, and ext is either zip or tar.

For example:

AUJULq.zip is the Australian postal table for July.

Global Postal Tables

NOTE: Global Postal Tables are a subset of international postal tables that are invoked from within Oracle Data Quality. Global Postal Tables are distinct because they require an additional service. The postal tables in this subset are: Austria, Brazil, Czech Republic, Denmark, Finland, Greece, Hungary, Ireland, Mexico, New Zealand, Norway, Poland, and Sweden.

XXXMMMYY.ext, where XXX is the 3-letter country code, MMMYY represents the abbreviation for the month and year the postal table was issued, and ext is either zip or tar.

For example:

DENJAN09.zip is the Denmark postal table for January 2009.

Census Directories

NOTE: Census data is available only for the United States.

USCMMMq.ext - This is the name of the United States census directory that includes the Interpolated Rooftop files. MMM is the abbreviation for the month the directory was issued and ext is either zip or tar.

USXMMMq.ext - This is the name of the United States census directory that includes the ZIP+4 Centroid files. MMM is the abbreviation for the month the directory was issued and ext is either zip or tar.

USPMMMq.ext - This is the name of the file that contains only the Interpolated Plus directory, where MMM is the abbreviation for the month the directory was issued and ext is either zip or tar.

DPV Directory

DPVMMMq.ext - This is the name of the US Delivery Point Validation directory, where MMM is the abbreviation for the month the directory was issued and ext is either zip or tar.

LACS DirectoryLink

USLMMMq.ext. This is the name of the United States LACSLink directory, and ext is either zip or tar.

SuiteLinkDirectory

USLMMMq.ext - This is the name of the United States SuiteLink directory, where MMM is the abbreviation for the month the directory was issued and ext is either zip or tar.

NOTE:

  • Delivery Point Validation is a U.S. Postal Service technology that helps validate the accuracy of existing address information and identify inaccurate, incomplete, or erroneous addresses.

  • The license agreements with the U.S. Postal Service limit the shipment and transfer of DPV and LACSLink directories to the United States and its territories only. Customers who purchase these directories must adhere to the same restriction.

  • SuiteLink is a product of the U.S. Postal Service that improves business address information by adding suite numbers to qualified records. Only business records that have been identified through CASS processing as having a high-rise default are candidates for SuiteLink processing.


2.3.2 Postal Code Installation Locations

By default, postal-related files and directories are installed to the following locations:

  • General Postal Tables (including DPV, LACSLink and SuiteLink tables)

    On UNIX operating systems:ODQ_HOME/oracledq/12/tables/postal_tables

    On Windows operating systems: \ODQ_HOME\oracledq\tables\*

  • Global Postal Tables and Latitude/Longitude Tables

    On UNIX operating systems:ODQ_HOME/oracledq/12/tables/postal_tables

    On Windows operating systems: \ODQ_HOME\oracledq\tables\*

  • Asian Postal Tables (China, Japan, Korea, Taiwan)

    On UNIX operating systems:ODQ_HOME/oracledq/12/tables/postal_tables

    On Windows operating systems: \ODQ_HOME\oracledq\tables\*

  • Census

    On UNIX operating systems:ODQ_HOME/oracledq/12/tables/postal_tables

    On Windows operating systems: \ODQ_HOME\oracledq\tables\*

If you want to use a different location for the postal tables, follow the procedures Section 2.3.3, "Alternative Postal Code Installation Locations".

2.3.3 Alternative Postal Code Installation Locations

Oracle recommends that you install the postal tables in the default directories (as defined in Section 2.3.2). If you prefer to use an alternative directory, you must define the alternative locations before installing the postal tables.

To specify an alternative location for the postal tables:

  1. Shut down Oracle Data Quality products, including all Oracle Data Quality clients.

  2. Close the Oracle Data Quality Scheduler service.

  3. Start the Metabase Server application.

    • On Windows operating systems:

      Programs > Oracle Data Quality Software > Metabase

    • On UNIX operating systems:

      ./mtb_admin

  4. When prompted, log on as the metabase administrator (madmin).

    Use the _control metabase name to apply the alternative location to all metabases.

  5. Ensure that changes have not already been made to the postal directory installation locations by typing the following commands, individually.

    define postal_directory
    define apac_postal_directory
    define census_directory
    define ga_directory
    

    The commands should return the following failure message: “No setting with name nnn_directory found in table default_settings.” For example, “No setting with name 'census_directory' found in table 'default settings'.”

    NOTE: If a value is returned, you need to remove the current setting before defining a new one. See Removing a Postal Directory Definition for more information.

  6. Create the alternative installation directory for non-Asian postal tables, census tables, global postal tables, and/or Asian postal tables.

  7. Move any installed xxCITY files from the default installation directory to the new, alternative directory.

    These files were copied to the default postal directories when TS Quality project templates were installed. They must be in the same location as the postal tables.

  8. Remove the default directories (or leave them empty).

  9. At the mtb_admin prompt, type:

    expert
    
  10. Define the alternative locations by issuing one or more of the following commands:

    • For non-Asian postal tables:

      define postal_directory [file join {d:\newpostal}]
      
    • For Asian postal tables:

      define apac_postal_directory [file join {d:\newpostal}]
      
    • For census tables:

      define census_directory [file join {d:\newpostal}]
      
    • For global postal tables:

      define ga_directory [file join {d:\newpostal}]
      

      where d:\newpostal is the path of the alternative location.

  11. Type exit to close the command prompt window.

  12. For global postal tables and latitude/longitude tables, there is an additional step.

    1. With a text editor, open the global postal table gaserver.ini file, which is located in the ODQ_HOME/oracledq/12/Software/bin directory).

    2. Set the CountryDataDirectory entry to point to the alternative location of the global postal table datastore \rdata directory.

    3. Set the KnowledgeBaseDirectory entry to point to the location of the global postal table datastore \kbase directory.

    4. Locate the LicenseDirectory entry and point it to the global postal table license directory. Figure 2-1 shows an example of a modified gaserver.ini file.

      Figure 2-1 Modified gaserver.ini File

      Surrounding text describes Figure 2-1 .
    5. Save and close the file.

    6. Copy the file you modified and paste it in the ODQ_HOME/oracledq/12/Software/bin/latlong directory, overwriting the existing file.

      NOTE: Both versions of the gaserver.ini file must point to the same locations.

  13. Restart Oracle Data Quality and the Scheduler.

2.3.4 Removing a Postal Directory Definition

To remove a postal directory definition:

  1. Shut down Oracle Data Quality products, including all Oracle Data Quality clients.

  2. Close the Oracle Data Quality Scheduler service.

  3. Start the Metabase Server application.

    • On UNIX operating systems:

      ./mtb_admin

    • On Windows operating systems:

      Programs > Oracle Data Quality Software > Metabase Server > Administrator Command Prompt from the Start menu.

  4. When prompted, log on as the metabase administrator (madmin) to the _control metabase.

  5. Issue the appropriate command:

    undefine postal_directory
    undefine apac_postal_directory
    undefine census_directory
    undefine ga_directory
    

2.3.5 Postal Code Installation Procedures

The basic installation procedure is the same for all postal tables categories. However, there is an extra step involved in setting up a Global Postal Table.

To install postal directory files:

  1. Download the Postal Table file and copy it to the postal install directory. This file is located on the installation CD/DVD or was installed on your machine from an FTP session. See Postal Table Naming Conventions for a description of the file name formats.

  2. Decompress the .tar or .zip file using the appropriate command (WinZip or tar). The expanded files are placed into the current directory.

    NOTE: Oracle Data Quality Software compresses some postal tables because of their size. Review the list of files for any that have a .Z extension, which indicates compression. If necessary, uncompress files by entering the following command:

    uncompress *.Z
    
  3. If you purchased one of the Global Postal Tables, complete the procedure “To set up the Global postal service in Windows” or “To set up a Global postal service in UNIX.” (The following countries use a Global Postal Table: Austria, Brazil, Czech Republic, Denmark, Finland, Greece, Hungary, Ireland, Mexico, New Zealand, Norway, Poland, and Sweden.)

2.3.6 Setting Up a Global Postal Service on UNIX Operating Systems

Use the following steps to set up a global postal service on UNIX operating systems.

  1. Complete the installation of the Global Postal Tables as described in Section 2.3.5.

  2. Change to the directory that contains the file gactl.

    • For AIX operating systems, this file can be found in the directory:

      ODQ_HOME/oracledq/12/Software/GA_server

    • For all other UNIX operating systems, this file can be found in the directory:

      ODQ_HOME/oracledq/12/Software/bin

  3. Enter the following command:

    gactl start
    

    NOTE: If you need to install a new Global Postal Table, you must stop the service, install the new table, then restart the service.

    To stop the service, issue the following command:

    gactl stop
    

2.3.7 Setting up a Global Postal Service on Windows Operating Systems

To set up the Global postal service in Windows operating systems:

  1. Complete the installation of the Global Postal Tables.

  2. From the Start menu, select Programs > Oracle Data Quality products > Global Postal Matcher > Create Service.

  3. (Optional) If you have defined a network drive as the alternate location for the GA postal tables, as described in Section 2.3.3, you must modify the Global Address Service properties.

    1. Go to the Windows Services page (Start > Settings > Control Panel > Administrative Tools > Services).

    2. Locate the Global Address Server entry and right-click.

    3. Select Properties and then click the Log On tab.

    4. Select the This Account option and enter your domain name and user name in the first field (for example, domain_name\jsmith).

    5. In the Password and Confirm Password fields, enter the password associated with your user id and click OK.

  4. From the Start menu, select Programs > Oracle Data Quality products > Global Postal Matcher > Start Service.

  5. From the Start menu, select Settings > Control Panel > Administrative Tools > Services and confirm that the Global service is running.

    NOTE: If you need to install a new Global Postal Table, you must stop the service, install the new table, then restart the service.

2.4 Post-Installation Configuration Tasks

Depending on your installation type, you may need to manually configure some of the Oracle Data Quality components. Review the following sections to determine if additional configuration tasks are required:

2.4.1 Start the Oracle Data Quality Scheduler

If you installed the Oracle Data Profiling and Quality server, you must start the Oracle Data Quality Scheduler before you begin. The Oracle Universal Installer will start the Scheduler as part of the installation process, but you may need to start it again.

To start the Oracle Data Quality Scheduler:

  1. Make sure that you are logged on to the Oracle Data Profiling and Quality server as the Oracle Data Quality server administrator as defined on the Metabase Server Details screen during the installation.

  2. Navigate to the following directory:

    <ODQ_HOME/oracledq/metabase_server/metabase/bin
    
  3. Type the command:

    ./scheduler -start
    

For more information on using the Scheduler, see the online help for Metabase Administrators.

2.4.2 Configure Environment Variables for UNIX Operating Systems

On UNIX platforms add the following environment variables for the user who has installed Oracle Data Integrator:

  • Oracle_QUALITY=ODQ_HOME/oracledq/12/Software

  • LD_LIBRARY_PATH=ODQ_HOME/oracledq/12/Software/bin

2.4.3 Configure inetd.conf File

Oracle Data Quality products work with inetd, a daemon process that handles network services operating on a UNIX operating system. Upon execution, inetd reads its configuration information from a configuration file which, by default, is /etc/inetd.conf.

If you installed the Metabase Server, the Oracle Universal Installer automatically updated the inetd.conf file. For Linux, HP, and AIX systems, no further action is required.

If you do update the inetd.conf file for any reason, be sure to recycle it.

On Solaris 10 and later systems, inetd reads configuration information from a different location. If you have installed Oracle Data Profiling and Quality components on a Solaris 10 system, log on as the root user and issue the following command at the command prompt:

inetconv -f -o /var /tmp

This command converts the data quality entry in the inetd.conf file to the format required by Solaris 10.