Beruflich Dokumente
Kultur Dokumente
Time to Complete
Approximately 1 hour.
Introduction
Repositories are schemas and tables in a database that hold information about ODI Designs, Topologies, and
Security. There is a one-to-many relationship between Master and Work repositories. An example of why you
might want to have multiple work repositories is for separating development and production designs. The
repository schemas and tables can be created either manually using ODI Studio or automatically using
Repository Creation Utility (RCU). RCU is the preferred method of maintaining the repositories. The database
storing the repository can be Oracle Database 12c or several other supported databases.
This is the first in a series of four OBEs in the Oracle Data Integrator 12c: Getting Started
(https://apex.oracle.com/pls/apex/f?
p=44785:24:15503233161396::::P24_CONTENT_ID,P24_PREV_PAGE:7952,24) series.
Scenario
Linda works as a database administrator for Example Enterprise Corp (http://www.example.com). In Example
Enterprise, Linda is responsible for performing database management and integration tasks on the various
resources within the organization. In particular, Linda is responsible for data loading, transformation, and
validation.
To begin working on her projects (such as exporting a flat file to a relational table), she needs to create the
new Master repository and Work repository. This is her first task. Following this, she will make a flat file to
relational table project. Following that, she will make an agent. These other tasks are covered in later OBEs.
A supported operating system (the OS shown here is 64-bit Oracle Enterprise Linux release 6.7 (Santiago),
other versions such as Windows are supported as well)
Oracle Database (the version shown here is Enterprise Edition 12.1.0.2.0, other versions are supported as
well)
Oracle Data Integrator 12c (the version shown here is 12.2.1)
The following is a list of OPTIONAL software:
Oracle WebLogic Server (WLS) 12c (other versions are supported as well)
Oracle SQL Developer 12c (included with Database 12c install)
If WLS is present, it must be in the same Middleware HOME directories as ODI.
Prerequisites
Before starting this tutorial, you should have:
Started Oracle Database services and components such as the Listener.
A Database user with DBA role privileges such as the SYS or SYSTEM account.
Installed the HR schema included in the Oracle Database. The Sample Schemas Installation Guide is part of
the Oracle Database documentation set, and is also available online at: http://otn.oracle.com
(http://otn.oracle.com).
Already installed, but not configured, ODI.
Mapped a plan for passwords. Best practices are MixedCase, at least eight characters in length, and contain
a number. Examples: MyPasswd99 , Welcome1 .
In the task instructions, field prompts will be bold, such as Hostname. Values you type in the fields or on
copmmand lines will be bold blue Courier font, such as localhost .
To do create the Master and Work repositories with Repository Creation Utility (RCU), perform the following
steps:
Installing ODI adds the RCU bits to the Middleware HOME. Navigate to the proper directory and launch RCU.
OS Prompt
[myuser@myhost~]$ cd$FMW_HOME/oracle_common/bin
[myuser@myhostbin]$ pwd
/u01/app/oracle/Middleware/Oracle_Home/oracle_common/bin
[myuser@myhostbin]$ ./rcu
You may find copies of RCU shell scripts elsewhere. This is the one you want.
The Welcome page is displayed. There is nothing to select.
Click
Next
to continue.
On the Create Repository page, select Create Repository and System Load and Product Load (which is the default). This will require DBA
privileges such as the user SYS or SYSTEM would have.
Click
Next
to continue.
1521 , Database Service Name such as orcl.example.com (note this is not the instance name), Database Username such as
sys , and the corresponding Password which will not display. The Role will change automatically as you type a Username.
Click
Next
to continue. You may see the following warning, depending on your database configuration.
If you are using Latin alphabets for languages such as English, click
Ignore
When the progress bar reaches 100% and all the lines have green checks, click
OK
to continue.
On the Select Components page, select Oracle Data Integrator. Selecting that one line item will automatically select several other
components as indicated by the black checks. Notice the DEV prefix on some of the schema names. You can change the default prefix, as will
be needed if you ever add additional repositories.
Click
Next
When the progress bar reaches 100% and all the lines have green checks, click
OK
to continue.
In a training environment, it is acceptable to use the same password for all schemas; but in a production environment, you would likely use
different passwords. Click
Next
to continue.
On the Custom Variables page, enter the same Password in four places, enter a Work Repository Type of
Name of
workrep .
Note that the Supervisor password is for ODI Studio, and the Repository password is for the database user. These eventually will be stored in
Oracle Wallet. Click
Next
to continue.
On the Map Tablespaces page, there is nothing to do, the defaults are fine. Note the prefix of
the tablespace names.
Click
Next
Click
OK
When the progress bar reaches 100% and all the lines have green checks, click
Click
Create
OK
to continue.
When the progress bar reaches 100% and all the lines have green checks, it will automatically go to the Completion Summary page.
On the Completion Summary page, you have the option to view the various log files.
Note that this phase on this machine took about 4 minutes to complete on a typical PC. Click
Close
to continue.
In summary, you have used RCU to create various schemas on an Oracle database to support ODI.
Remember the passwords, you will need them later.
Start RCU just the same way you did to create repositories, only this time you will drop repositories.
OS Prompt
[myuser@myhost~]$ cd/u01/app/oracle/Middleware/Oracle_Home/oracle_common/bin
[myuser@myhostbin]$ ./rcu
Click
Next
to continue.
On the Create Repository page, select Drop Repository. (The page name on the top banner and left navigation will change from "Create" to
"Drop" when you select Drop below. The number of steps will change as well.)
Click
Next
to continue.
orcl.example.com (note this is not the instance name), Username such as sys , and the corresponding
Password which will not display. The Role will change automatically as you type a Username.
Click
Next
When the progress bar reaches 100% and all the lines have green checks, click
OK
to continue.
On the Select Components page, use the with prefix pulldown to select the schemas to drop. The example shows selecting JUNK. Note the
prefixes of the components in the background reflect your choice.
Click
Next
When the progress bar reaches 100% and all the lines have green checks, click
OK
to continue.
When the progress bar reaches 100% and all the lines have green checks, it will automatically go to the Completion Summary page.
On the Completion Summary page, you have the option to view the various log files.
Click
Close
to continue.
In summary, you used RCU to remove unwanted schemas from the database based on prefixes. Generally
speaking, this is an unrecoverable action. It is recommended to backup any repository data just in case.
You can do this either from the database using utilities such as RMAN, or from ODI Studio.
Start your favorite SQL editor. You can use TOAD, SQL*Plus, or any similar tool. This example uses SQL Developer, a GUI which is included
with Oracle Database 12c.
How you start SQL Developer is installation dependent. You may have a desktop icon to start it.
Create a New Connection. Right-click on Connections, then click the + green plus.
There are multiple ways to create a connection, any one of them is valid.
localhost , the Port such as 1521 and the SID such as orcl
(note this is instance, not the service name.) Verify the appropriate Role; for example, sys requires SYSDBA. Click
Test
to continue.
If the test is successful (that is, if a connection can be established and the credentials are correct), it will reply, Status: Success in the lower
left corner.
Click Connect to continue. You can use this connection for the rest of the tutorial.
SELECT
Click the
green arrow in the top menu bar to display the table. Nothing to do here, just look. These were inserted by RCU.
FROMall_tablesWHERE
owner='DEV_ODI_REPO' in the Query Builder.
Click the
green arrow in the top menu bar to display the table count. Wow, over two hundred tables just for ODI. Nothing to do here, just
In summary, you have used SQL to verify that RCU built the repositories correctly.
To connect to a particular set of master and work repositories, perform the following steps:
OS Prompt
[myuser@myhost~]$ cd$ODI_HOME/studio
[myuser@myhoststudio]$ pwd
/u01/app/oracle/Middleware/Oracle_Home/odi/studio
[myuser@myhoststudio]$ ./odi.sh
OracleFusionDataIntegratorStudio12c
Copyright(c)1997,2013,Oracleand/oritsaffiliates.Allrightsreserved.
Midway through the progress bar, and only the very first time, Confirm Import Preferences dialog box will pop up and ask if you want to
import preferences from a previous installation. If there is no previous installation, there is nothing to select.
Click
No
There are other places on the menu bar to do the same thing.
On the Login panel, to add a new login, click the + green plus.
Strictly speaking, the yellow pencil (edit) and the red X (delete) should be greyed out since there is nothing to edit or delete yet.
Fill in all of the Connection information. This must match what you created using RCU and is case-sensitive.
Field Prompt:
Value:
Login Name:
DEV_ODI_REPO
ODI User:
SUPERVISOR
Password:
(notdisplayed)
Master User:
DEV_ODI_REPO
Master Password:
(notdisplayed)
Driver List:
Driver Name:
Url:
oracle.jdbc.OracleDriver
jdbc:oracle:thin:@
localhost:1521:orcl
<placeholders> )
Click
Test
OK .
Only on the very first time, New Wallet Password asks you to define a password and an expiration time. When using a wallet to store the ODI
credentials, ODI Studio will ask you for the Wallet password prior to logging in. You will not need to enter the ODI credentials again (User
password).
Click
OK
to continue. This stores the wallet information (and other preferences) in the hidden directory in your home directory:
~/.odi/oracledi/ewallet . You can view it with the GUI tool owm (Oracle Wallet Manager).
If you ever deinstall ODI, the wallet is not removed automatically.
From now on, the ODI Login page will be prepopulated with this information.
Click
OK
to continue.
If the connection was successful, you will have information under the three tabs in the left panel.
In summary, you have defined the connection for ODI to use the repository you created with RCU. That
information is stored in Oracle Wallet in your home directory.
sqlplus , or SQL Developer, or the SQL tool of your choice to create a new DB user.
OS Prompt
[myuser@myhost~]$ sqlplus/assysdba
SQL*Plus:Release12.1.0.2.0ProductiononFriSep2005:21:082013
Copyright(c)1982,2013,Oracle.Allrightsreserved.
Connectedto:
OracleDatabase12cEnterpriseEditionRelease12.1.0.2.064bitProduction
WiththePartitioning,OLAP,AdvancedAnalyticsandRealApplicationTestingoptions
SQL> createuserDEV_ODI_REPO3identifiedbyWelcome1
Usercreated.
SQL> grantdbatoDEV_ODI_REPO3
Grantsucceeded.
SQL> exit
DisconnectedfromOracleDatabase12cEnterpriseEditionRelease12.1.0.2.064bitProdu
WiththePartitioning,OLAP,AdvancedAnalyticsandRealApplicationTestingoptions
[myuser@myhost~]$
In real life, the DBA role may be a bit excessive, you would probably use a lower set of permissions.
You already have one work repository connected from RCU. To create another new work repository, in the left panel, click the Topology tab,
then expand
Repositories, then right-click Work Repositories, then click New Work Repository.
Field
Value:
Prompt:
Technology:
JDBC
list)
Driver:
JDBC Url:
jdbc:oracle:thin:@
localhost:1521:orcl
<placeholders> )
DEV_ODI_REPO3
If you use the same User again as previously used, for example
creates a new user in SQL*Plus as recommended, then this step in ODI creates a second repository and leaves the first intact.
Password:
(notdisplayed,but
matchestheonejustcreated
insqlplus)
Next
to continue.
The warning about not using localhost is a good suggestion, but it is okay to use it for training purposes. Click
On the Specify ODI Work Repository properties panel, enter the following information:
Field Prompt:
Value:
Name:
WORKREP3
Password:
(notdisplayed)
Yes
to continue.
Click
Finish
Yes
to continue.
On the Enter Wallet Password dialog box, enter a password (which will not display). Click
OK
to continue.
You have now created a new work repository which is in addition to the old work repository.
To verify that the new work repository is fully populated, you can click Open to see information about it.
Nothing to do here, just look. Note that the old name workrep remains on the left, the old work repository is still good, you now have two work
repositories.
In summary, the original work repository was fine, but this created a new work repository. Since it is a
replacement, it may have been necessary to back up (export) the previous one if you ever need it back.
In the Import Selection dialog box, select Import the Master Repository.
Click
OK
to continue.
In the Import a Master Repository dialog box, select Import From a Zip File. Either browse for the file using the
type the name of the zip file.
Click
OK
magnifying glass, or
Depending on the XML file size, this can take several minutes to complete.
An Import Report displays. Nothing to do here, just look.
Click
Close
to continue.
In summary, you can import a previously saved Master Repository from a zip file.
In the Import Selection dialog box, select Import the Work Repository.
Click
OK
to continue.
In the Import a Work Repository dialog box, select Import From a Zip File. Either browse for the file using the
type the name of the zip file.
magnifying glass, or
Click
OK
Depending on the XML file size, this can take several minutes to complete.
An Import Report displays. Nothing to do here, just look.
Click
Close
to continue.
In summary, you can import a previously saved Work Repository from a zip file.
Click
OK
In summary, one way to view the active connection information is from the main menu under ODI.
Click
OK
Test
to close the dialog box. Note that even though the test appeared to be completely successful, there may still be problems.
Occasionally messages will display in the terminal session used to start ODI Studio (it may be behind the active Studio window). If you see
these, you may be instructed to do something or contact someone.
In summary, there are several ways to see, edit, and test the connection information.
Resources
The following are conceptual or procedural Help topics relevant to the topic of this tutorial:
Online documentation, viewlets, samples, and OLN URLs on OTN:
www.oracle.com/goto/odi (http://www.oracle.com/goto/odi)
Credits
Lead Curriculum Developer: Elio Bonazzi
Other Contributors: Viktor Tchemodanov, Alex Kotopoulis, Julien Testut
About Oracle (http://www.oracle.com/corporate/index.html)
Legal Notices (http://www.oracle.com/us/legal/index.html)
Contact Us (http://www.oracle.com/us/corporate/contact/index.html)
Terms of Use (http://www.oracle.com/us/legal/terms/index.html)