Skip Headers
Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator
11g Release 1 (11.1.1)

Part Number E12643-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
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

3 Administering the Oracle Data Integrator Repositories

This chapter describes how to create and administer Oracle Data Integrator repositories. An overview of the repositories used in Oracle Data Integrator is provided.

This chapter includes the following sections:

3.1 Introduction to Oracle Data Integrator Repositories

There are two types of repositories in Oracle Data Integrator:

The standard method for creating repositories is using Repository Creation Utility (RCU). RCU automatically manages storage space as well as repository creation. However, if you want to create the repositories manually, it is possible to manually create and configure the repositories.

The steps needed to create and configure repositories are detailed in the following sections:

Note:

Oracle recommends that you regularly perform the following maintenance operations: purge the execution logs in order to reduce the work repository size, and back up the Oracle Data Integrator repositories on the database.

Advanced actions for administering repositories are detailed in Section 3.8, "Advanced Actions for Administering Repositories".

3.2 Creating Repository Storage Spaces

Oracle Data Integrator repositories can be installed on database engines supported by Oracle Fusion Middleware 11g. For the latest list of supported databases versions as well as the requirements for each database, see:

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

For each database that will contain a repository, a storage space must be created.

Caution:

For reasons of maintenance and back-up, we strongly recommend that repositories be stored in a different space from where your application data is kept (for example in a different schema for an Oracle database, or in a different database for Sybase or Microsoft SQL Server).

Your master repository can be stored in the same schema as one of your work repositories. However, you cannot create two different work repositories in the same schema.

The examples in the following table are supplied as a guide:

Technology Steps to follow
Oracle Create a schema odim to host the Master repository and a schema odiw to host the work repository.

The schemas are created by the following SQL commands:

SQL> create user MY_SCHEMA identified by MY_PASS
       default tablespace MY_TBS 
       temporary tablespace MY_TEMP; 
SQL> grant connect, resource to MY_SCHEMA;
SQL> grant execute on dbms_lock to MY_SCHEMA;

Where:

MY_SCHEMA corresponds to the name of the schema you want to create.

MY_PASS corresponds to the password you have given it <MY_TBS> the Oracle tablespace where the data will be stored

MY_TEMP temporary default tablespace

Microsoft SQL Server or Sybase ASE Create a database db_odim to host the master repository and a database db_odiw to host the work repository. Create two logins odim and odiw which have these databases by default.

Use Enterprise Manager to create the two databases db_odim and db_odiw.

Use Query Analyzer or I-SQL to launch the following commands:

CREATE LOGIN mylogin
     WITH PASSWORD = 'mypass',
     DEFAULT_DATABASE = defaultbase,
     DEFAULT_LANGUAGE = us_english;
USE defaultbase;
CREATE USER dbo FOR LOGIN mylogin;
GO

Where:

mylogin corresponds to odim or odiw.

mypass corresponds to a password for these logins.

defaultbase corresponds to db_odim and db_odiw respectively.

Note: It is recommended to configure the Microsoft SQL Server databases that store the repository information with a case-sensitive collation. This enables reverse-engineering and creating multiple objects with the same name but a different case (for example: tablename and TableNAme).

DB2/400 Create a library odim to host the Master repository and a schema odiw to host the work repository. Create two users odim and odiw who have these libraries by default.

Note: The libraries must be created in the form of SQL collections.

DB2/UDB Pre-requisites:
  • Master and work repository users must have access to tablespaces with minimum 16k pagesize

  • The database must have a temporary tablespace with minimum 16 k

For example:

CREATE  LARGE  TABLESPACE ODI16 PAGESIZE 16 K  MANAGED BY AUTOMATIC STORAGE ;
GRANT USE OF TABLESPACE ODI16 TO USER ODIREPOS; 

3.3 Creating the Master Repository

Creating the master repository creates an empty repository structure and seeds metadata (for example, technology definitions, or built-in security profiles) into this repository structure.

To create the master repository:

  1. Open the New Gallery by choosing File > New.

  2. In the New Gallery, in the Categories tree, select ODI.

  3. Select from the Items list the Master Repository Creation Wizard.

  4. Click OK.

    The Master Repository Creation wizard opens.

  5. Specify the Database Connection parameters as follows:

    • Technology: From the list, select the technology that will host your master repository. Default is Oracle.

    • JDBC Driver: The driver used to access the technology, that will host the repository.

    • JDBC URL: The URL used to establish the JDBC connection to the database.

      Note that the parameters JDBC Driver and URL are synchronized and the default values are technology dependant.

    • User: The user ID / login of the owner of the tables (for example, odim).

    • Password: This user's password.

    • DBA User: The database administrator's username

    • DBA Password: This user's password

  6. Specify the Repository Configuration parameters as follows:

    • ID: A specific ID for the new repository, rather than the default 0.

      Note:

      It is strongly recommended that this ID is unique and not used for any other master repository, as it affects imports and exports between repositories
  7. Click Test Connection to test the connection to your master repository.

    The Information dialog opens and informs you whether the connection has been established. If the connection fails, fix the connection to your master repository before moving to next step.

  8. Click Next.

  9. Do one of the following:

    • Select Use ODI Authentication to manage users using ODI's internal security system and enter the following supervisor login information:

      Properties Description
      Supervisor User User name of the ODI supervisor.
      Supervisor Password This user's password
      Confirm Password This user's password

    • Select Use External Authentication to use an external enterprise identity store, such as Oracle Internet Directory, to manage user authentication and enter the following supervisor login information:

      Properties Description
      Supervisor User User name of the ODI supervisor
      Supervisor Password This user's password

      Note:

      In order to use the external authentication option, ODI Studio has to be configured for external authentication. See Section 24.3.2, "Setting Up External Authentication" for more information and restart ODI Studio.
  10. Click Next.

  11. Specify the password storage details:

    • Select Internal Password Storage if you want to store passwords in the Oracle Data Integrator master repository

    • Select External Password Storage if you want use JPS Credential Store Framework (CSF) to store the data server and context passwords in a remote credential store. Indicate the MBean Server Parameters to access the credential store. Refer to Chapter 24, "Managing the Security in Oracle Data Integrator" for more information.

  12. In the Master Repository Creation Wizard click Finish to validate your entries.

Oracle Data Integrator begins creating your master repository. You can follow the procedure on your Messages – Log. To test your master repository, refer to the Section 3.4, "Connecting to the Master Repository".

3.4 Connecting to the Master Repository

To connect to the Master repository:

  1. Open the New Gallery by choosing File > New.

  2. In the New Gallery, in the Categories tree, select ODI.

  3. Select from the Items list Create a New ODI Repository Login.

  4. Click OK.

    The Repository Connection Information dialog appears.

  5. Specify the Oracle Data Integrator connection details as follows:

    • Login name: A generic alias (for example: Repository)

    • User: The ODI supervisor user name you have defined when creating the master repository or an ODI user name you have defined in the Security Navigator after having created the master repository.

    • Password: The ODI supervisor password you have defined when creating the master repository or an ODI user password you have defined in the Security Navigator after having created the master repository.

  6. Specify the Database Connection (Master Repository) details as follows:

    • User: Database user ID/login of the schema (database, library) that contains the ODI master repository

    • Password: This user's password

    • Driver List: Select the driver required to connect to the DBMS supporting the master repository you have just created from the dropdown list.

    • Driver Name: The complete driver name

    • JDBC URL: The URL used to establish the JDBC connection to the database hosting the repository

      Note that the parameters JDBC Driver and URL are synchronized and the default values are technology dependant.

  7. Select Master Repository Only.

  8. Click Test to check that the connection is working.

  9. Click OK to validate your entries.

3.5 Creating a Work Repository

Several work repositories can be designated with several master repositories if necessary. However, a work repository can be linked with only one master repository for version management purposes.

To create a new work repository:

  1. In the Topology Navigator, go to the Repositories panel.

  2. Right-click the Work Repositories node and select New Work Repository.

    The Create Work Repository Wizard opens.

  3. Specify the Oracle Data Integrator work repository connection details as follows:

    • Technology: Choose the technology of the server to host your work repository. Default is Oracle.

    • JDBC Driver: The driver used to access the technology, that will host the repository.

    • JDBC URL: The complete path of the data server to host the work repository.

      Note that the parameters JDBC Driver and URL are synchronized and the default values are technology dependant.

      It is recommended to use the full machine name instead of localhost in the JDBC URL to avoid connection issues. For example for remote clients, the client (ODI Studio or SDK) is on a different machine than the work repository and localhost points to the current client machine instead of the one hosting the work repository.

    • User: User ID / login of the owner of the tables you are going to create and host of the work repository.

    • Password: This user's password. This password is requested for attaching this work repository to a different master.

  4. Click Test Connection to verify that the connection is working.

  5. Click Next.

    Oracle Data Integrator verifies whether a work repository already exists on the connection specified in step 3:

    • If an existing work repository is detected on this connection, the next steps will consist in attaching the work repository to the master repository. Refer to "Specify the Password of the Oracle Data Integrator work repository to attach." for further instructions.

    • If no work repository is detected on this connection, a new work repository is created. Continue with the creation of a new work repository and provide the work repository details in step 6.

  6. Specify the Oracle Data Integrator work repository properties:

    • ID: A specific ID for the new repository, rather than the default 0.

      Note:

      It is strongly recommended that this ID is unique and not used for any other work repository, as it affects imports and exports between repositories
    • Name: Give a unique name to your work repository (for example: DEVWORKREP1).

    • Password: Enter the password for the work repository.

    • Type: Select the type for the work repository:

      • Development: This type of repository allows management of design-time objects such as data models and projects (including interfaces, procedures, etc). A development repository includes also the run-time objects (scenarios and sessions). This type of repository is suitable for development environments.

      • Execution: This type of repository only includes run-time objects (scenarios, schedules and sessions). It allows launching and monitoring of data integration jobs in Operator Navigator. Such a repository cannot contain any design-time artifacts. Designer Navigator cannot be used with it. An execution repository is suitable for production environments.

  7. Click Finish.

  8. The Create Work Repository login dialog opens. If you want to create a login for the work repository, click Yes and you will be asked to enter the Login Name in a new dialog. If you do not want to create a work repository login, click No.

  9. Click Save in the toolbar.

For more information, refer to Section 3.6, "Connecting to a Work Repository".

3.6 Connecting to a Work Repository

To connect to an existing work repository and launch Designer Navigator:

  1. Open the New Gallery by choosing File > New.

  2. In the New Gallery, in the Categories tree, select ODI.

  3. Select from the Items list Create a New ODI Repository Login.

  4. Click OK.

    The Repository Connection Information dialog opens.

  5. Specify the Oracle Data Integrator connection details as follows:

    • Login name: A generic alias (for example: Repository)

    • User: The ODI supervisor user name you have defined when creating the master repository or an ODI user name you have defined in the Security Navigator after having created the master repository.

    • Password: The ODI supervisor password you have defined when creating the master repository or an ODI user password you have defined in the Security Navigator after having created the master repository.

  6. Specify the Database Connection (Master Repository) details as follows:

    • User: Database user ID/login of the schema (database, library) that contains the ODI master repository

    • Password: This user's password

    • Driver List: Select the driver required to connect to the DBMS supporting the master repository you have just created from the dropdown list.

    • Driver Name: The complete driver name

    • URL: The url used to establish the JDBC connection to the database hosting the repository

  7. Click on Test Connection to check the connection is working.

  8. Select Work Repository and specify the work repository details as follows:

    • Work repository name: The name you gave your work repository in the previous step (WorkRep1 in the example). You can display the list of work repositories available in your master repository by clicking on the button to the right of this field.

  9. Click OK to validate your entries.

3.7 Changing the Work Repository Password

To change the work repository password:

  1. In the Repositories tree of Topology Navigator expand the Work Repositories node.

  2. Double-click the work repository. The Work Repository Editor opens.

  3. On the Definition tab of the Work Repository Editor click Change password.

  4. Enter the current password and the new one.

  5. Click OK.

3.8 Advanced Actions for Administering Repositories

Advanced actions for administering repositories do not concern the creation process of repositories. The actions described in this section deal with advanced actions performed on already existing repositories. Once the repositories are created you may want to switch the password storage or you may need to recover the password storage after a credential store crash. Actions dealing with password handling are covered in Section 24.3.1, "Setting Up External Password Storage". The export and import of master and work repositories is covered in Chapter 20, "Exporting/Importing".

This section contains the following topics:

3.8.1 Attaching and Deleting a Work Repository

Attaching a work repository consists of linking an existing work repository to the current master repository. This existing work repository already exists in the database and has been previously detached from this or another master repository.

Deleting a work repository deletes its link to the master repository. This is an opposite operation to attaching. This operation does not destroy the work repository content.

Attaching a Work Repository

To attach a work repository to a master repository:

  1. In the Topology Navigator, go to the Repositories panel.

  2. Right-click the Work Repositories node and select New Work Repository.

    The Create Work Repository Wizard opens.

  3. Specify the Oracle Data Integrator work repository connection details as follows:

    • Technology: From the list, select the technology that will host your work repository. Default is Oracle.

    • JDBC Driver: The driver used to access the technology, that will host the repository.

    • JDBC URL: The complete path of the data server to host the work repository.

      Note that the parameters JDBC Driver and URL are synchronized and the default values are technology dependant

    • User: User ID / login of the owner of the tables you are going to create and host of the work repository.

    • Password: This user's password.

  4. Click Test Connection to check the connection is working.

  5. Click Next.

  6. Specify the Password of the Oracle Data Integrator work repository to attach.

  7. Click Next.

  8. Specify the Name of the Oracle Data Integrator work repository to attach.

  9. Click Finish.

Deleting a Work Repository

To delete the link to the master repository:

  1. In the Topology Navigator, go to the Repositories panel.

  2. Expand the Work Repositories node and right-click the work repository you want to delete.

  3. Select Delete.

  4. In the Confirmation dialog click Yes.

  5. The work repository is detached from the master repository and is deleted from the Repositories panel in Topology Navigator.

3.8.2 Erasing a Work Repository

Deleting a work repository is equivalent to detaching a work repository from the master repository. For more information, refer to Section 3.8.1, "Attaching and Deleting a Work Repository".

Erasing a work repository consists of deleting the work repository from the database.

WARNING:

Erasing your work repository is an irreversible operation. All information stored in the work repository will be definitively deleted, including the metadata of your models, projects and run-time information such as scenarios, schedules, and logs.

Erasing a Work Repository

To erase a work repository from the database:

  1. In the Topology Navigator, go to the Repositories panel.

  2. Expand the Work Repositories node and right-click the work repository you want to delete.

  3. Select Erase from Database.

  4. In the Confirmation dialog click Yes, if you want to definitively erase the work repository from the database.

  5. The work repository is erased from the database and is deleted from the Repositories panel in Topology Navigator.

3.8.3 Renumbering Repositories

Renumbering a repository consists of changing the repository ID and the internal ID of the objects stored in the repository.

Renumbering a repository is advised when two repositories have been created with the same ID. Renumbering one of these repositories allows object import/export between these repositories without object conflicts.

WARNING:

Renumbering a repository is an administrative operation that requires you to perform a backup of the repository that will b renumbered on the database.

Renumbering a Work Repository

To renumber a work repository:

  1. In the Topology Navigator, go to the Repositories panel.

  2. Expand the Work Repositories node and right-click the work repository you want to renumber.

  3. Select Renumber...

  4. In the Renumbering the Repository - Step 1 dialog click Yes.

  5. In the Renumbering the Repository - Step 2 dialog click OK.

  6. In the Renumbering the Repository - Step 3 dialog enter a new and unique ID for the work repository and click OK.

  7. In the Renumbering the Repository - Step 4 dialog click Yes.

  8. The work repository and all the objects attached to it are renumbered.

Renumbering a Master Repository

  1. In the Topology Navigator, go to the Repositories panel.

  2. Expand the Master Repositories node and right-click the master repository you want to renumber.

  3. Select Renumber...

  4. In the Renumbering the Repository - Step 1 dialog click Yes.

  5. In the Renumbering the Repository - Step 2 dialog enter a new and unique ID for the master repository and click OK.

  6. The master repository and all the details stored in it such as topology, security, and version management details are renumbered.

3.8.4 Tuning the Repository

Concurrent connections to the repository database may be controlled and limited by the database engine where the repository is stored. On Oracle the property limiting the number of connections is max_processes. When running a large number of parallel executions, you may need to tune the database to increase the maximum number of connections allowed to the repository database.

The number of connections required depends on the number of sessions running the connection:

  • Each session execution requires two database connections (one to the master, one to the work repository) for the duration of execution, and also a third database connection is required for a security check for a very short period when the session begins.

  • For non-Oracle databases, each Load Plan step consumes an additional connection as a lock while the Load Plan is being executed.