List of ODI Tools in ODI 12c

List of ODI Tools in ODI 12c

Oracle Data Integrator Tools by Category

This section lists Oracle Data Integrator tools by category.

Metadata

OdiReverseGetMetaData

OdiReverseManageShortcut

OdiReverseResetTable

OdiReverseSetMetaData

Oracle Data Integrator Objects

OdiDeleteScen

OdiExportAllScen

OdiExportEnvironmentInformation

OdiExportLog

OdiExportMaster

OdiExportObject

OdiExportScen

OdiExportWork

OdiGenerateAllScen

OdiImportObject

OdiImportScen

Utilities

OdiAnt

OdiBeep

OdiEnterpriseDataQuality

OdiKillAgent

OdiOSCommand

OdiPingAgent

OdiPurgeLog

OdiReinitializeSeq

OdiRemoveTemporaryObjects

OdiStartLoadPlan

OdiStartOwbJob

OdiStartScen

OdiUpdateAgentSchedule

Internet Related Tasks

OdiFtp

OdiFtpGet

OdiFtpPut

OdiInvokeWebService

OdiReadMail

OdiScpGet

OdiScpPut

OdiSftp

OdiSftpGet

OdiSftpPut

OdiSendMail

Files

OdiFileAppend

OdiFileCopy

OdiFileDelete

OdiFileMove

OdiFileWait

OdiMkDir

OdiOutFile

OdiSqlUnload

OdiUnZip

OdiZip

SAP

OdiSAPALEClient and OdiSAPALEClient3

OdiSAPALEServer and OdiSAPALEServer3

XML

OdiXMLConcat

OdiXMLSplit

Event Detection

OdiFileWait

OdiReadMail

OdiSleep

OdiWaitForChildSession

OdiWaitForData

OdiWaitForLoadPlans

OdiWaitForLogData

OdiWaitForTable

Changed Data Capture

OdiManageOggProcess

OdiRefreshJournalCount

OdiRetrieveJournalData

OdiWaitForData

OdiWaitForLogData

OdiWaitForTable

Alphabetical List of Oracle Data Integrator Tools

This section lists Oracle Data Integrator tools in alphabetical order.

OdiAnt

OdiBeep

OdiDeleteScen

OdiEnterpriseDataQuality

OdiExportAllScen

OdiExportEnvironmentInformation

OdiExportLog

OdiExportMaster

OdiExportObject

OdiExportScen

OdiExportWork

OdiFileAppend

OdiFileCopy

OdiFileDelete

OdiFileMove

OdiFileWait

OdiFtp

OdiFtpGet

OdiFtpPut

OdiGenerateAllScen

OdiImportObject

OdiImportScen

OdiInvokeWebService

OdiKillAgent

OdiManageOggProcess

OdiMkDir

OdiOSCommand

OdiOutFile

OdiPingAgent

OdiPurgeLog

OdiReadMail

OdiRefreshJournalCount

OdiReinitializeSeq

OdiRemoveTemporaryObjects

OdiRetrieveJournalData

OdiReverseGetMetaData

OdiReverseManageShortcut

OdiReverseResetTable

OdiReverseSetMetaData

OdiSAPALEClient and OdiSAPALEClient3

OdiSAPALEServer and OdiSAPALEServer3

OdiScpGet

OdiScpPut

OdiSendMail

OdiSftp

OdiSftpGet

OdiSftpPut

OdiSleep

OdiSqlUnload

OdiStartLoadPlan

OdiStartOwbJob

OdiStartScen

OdiUnZip

OdiUpdateAgentSchedule

OdiWaitForChildSession

OdiWaitForData

OdiWaitForLoadPlans

OdiWaitForLogData

OdiWaitForTable

OdiXMLConcat

OdiXMLSplit

OdiZip

What are list of new components added in ODI 12c in Component Palette.?

What are list of new components added in ODI 12c in Component Palette.?

The following are the available component in the component palette:

1)     Expression

2)     Aggregate

3)     Distinct

4)     Set

5)     Filter

6)     Join

7)     Lookup

8)     Sort

9)     Split 

10) Pivot  (with new patch set  17053768)

11) Un-Pivot (with new patch set  17053768)

12) Table Function  (with new patch set  17053768)

13)   Sub-query Filter  (with new patch set  17053768)

Please find the below article for applying new patch for above new components.

http://oditraining.blogspot.in/2014/06/added-pivot-unpivot-table-functions-and_6.html

ODI SNP & Temporary Tables list ?

ODI SNP & Temporary Tables. 

1)     RKM will store the metadata into below following tables.

1.     Cleans up the SNP_REV_xx tables from previous executions using the OdiReverseResetTable tool.

2.     Retrieves sub models, datastores, attributes, unique keys, foreign keys, conditions from the metadata provider to SNP_REV_SUB_MODEL, SNP_REV_TABLE, SNP_REV_COL, SNP_REV_KEY, SNP_REV_KEY_COL, SNP_REV_JOIN, SNP_REV_JOIN_COL, SNP_REV_COND tables.

2)     LKM Temporary Tables.

a.     C$ table will be created by LKM for load the data from Source table to C$ staging table.

3)     CKM Temporary Tables.

a.     E$ Table for store error records while checking the Dataquality at Mapping level

b.    SNP_CHECK_TAB is a common error table to maintain the high level error details like. Schema name, table name, Error , Error type.

4)     IKM Temporary Tables.

a.     I$ table using for to load the data for integration before going to target table

5)     JKM Temporary Tables.

a.     J$ table for CDC concept to store the PK value into J$ table

b.    T$ Trigger for CDC concept is enabled at source table for DML trigger

c.     V$ View  will display the data for both Source and J$ table join query

d.    V$ DView will be joined both Source and J$table for filter condition with subscriber

What are the different types IKM Knowledge Module?

What are the different types IKM Knowledge Module?

1)     Append: Insert records from the flow into the target. It is possible to optionally delete all records from the target before the insert. Existing records are not updated.

      Using options like  TRUNCATE or DELETE_ALL =ture

2)     Control Append: Same as above, but in addition the data flow is checked in the process.

3)     Incremental Update: Same as above. In addition, it is possible to update existing records with data from the flow.

4)     Slowly Changing Dimension: Integrate data into a table using Type 2 slowly changing dimensions (SCD).

Oracle Data Integrator Project Components in ODI 12c

Oracle Data Integrator Project Components in ODI 12c

The following components are stored into a project. They appear in the in the Project accordion in the Designer Navigator, under the project's node.

Folder

Folders are components that help organizing the work into a project. Folders contain packages, mappings, procedures, and subfolders.

Packages

A package is a workflow, made up of a sequence of steps organized into an execution diagram. Packages assemble and reference other components from a project such as mappings, procedure or variable.

Mappings

A mapping is a reusable dataflow. It is a set of declarative rules that describes the loading of one or several target datastores from one or more source datastores. See 

Procedure

A Procedure is a reusable component that groups a sequence of operations that do not fit in the mapping concept.

Examples of procedures:

1)     Wait and unzip a file

2)     Send a batch of files via FTP

3)     Receive emails

4)     Purge a database

Variable

A variable's value is stored in Oracle Data Integrator. This value may change during the execution.

Sequence

A sequence is a variable automatically incremented when used. Between two uses the value is persistent.

User Functions

User functions allow you to define customized functions or "function aliases," for which you will define technology-dependent implementations. They are usable in mappings and procedures.

Knowledge Modules

Oracle Data Integrator uses Knowledge Modules at several points of a project design. A Knowledge Module is a code template related to a given technology that provides a specific function (loading data, reverse-engineering, journalizing).

Markers

A component of a project may be flagged in order to reflect a methodology or organization. Flags are defined using markers. These markers are organized into groups, and can be applied to most objects in a project.

Scenarios

When a package, mapping, procedure, or variable component has been fully developed, it is compiled in a scenario. A scenario is the execution unit for production. Scenarios can be scheduled for automated execution. See 

ODI Topology Coponent List of Objects

Topology Navigator

Topology Navigator is used to manage the data describing the information system's physical and logical architecture. Through Topology Navigator you can manage the topology of your information system, the technologies and their data types, the data servers linked to these technologies and the schemas they contain, the contexts, the language and the agents, as well as the repositories. The site, machine, and data server descriptions will enable Oracle Data Integrator to execute the same mappings in different environments.
This section contains these objects:

1.       Physical Architecture

2.       Contexts

3.       Logical Architecture

4.       Agents

5.       Languages

6.       Repositories

Physical Architecture

The physical architecture defines the different elements of the information system, as well as their characteristics taken into account by Oracle Data Integrator. Each type of database (Oracle, DB2, etc.), file format (XML, Flat File), or application software is represented in Oracle Data Integrator by a technology.

Contexts

Contexts bring together components of the physical architecture (the real Architecture) of the information system with components of the Oracle Data Integrator logical architecture (the Architecture on which the user works).
For example, contexts may correspond to different execution environments (Development, Test and Production) or different execution locations (Boston Site, New-York Site, and so forth.) where similar physical resource exist.

Logical Architecture

The logical architecture allows a user to identify as a single Logical Schema a group of similar physical schemas - that is containing data stores that are structurally identical - but located in different physical locations. Logical Schemas, like their physical counterpart, are attached to a technology.

Languages

Languages defines the languages and language elements available when editing expressions at design-time. Languages provided by default in Oracle Data Integrator do not require any user change.

Repositories (Master & Work Repositories)

The topology contains information about the Oracle Data Integrator repositories. Repository definition, configuration and installation is covered in the Installation and Upgrade Guide for Oracle Data Integrator.

Differences between Packages, Scenarios, and Load Plans ?

Differences between Packages, Scenarios, and Load Plans


A Load Plan is the largest executable object in Oracle Data Integrator. It uses Scenarios in its steps. When an executable object is used in a Load Plan, it is automatically converted into a scenario. For example, a package is used in the form of a scenario in Load Plans. Note that Load Plans cannot be added to a Load Plan. However, it is possible to add a scenario in form of a Run Scenario step that starts another Load Plan using the OdiStartLoadPlan tool.

Load plans are not substitutes for packages or scenarios, but are used to organize at a higher level the execution of packages and scenarios.

Unlike packages, Load Plans provide native support for parallelism, restartability and exception handling. Load plans are moved to production as is, whereas packages are moved in the form of scenarios. Load Plans can be created in Production environments.
The Load Plan instances and Load Plan runs are similar to Sessions. The difference is that when a session is restarted, the existing session is overwritten by the new execution. The new Load Plan Run does not overwrite the existing Load Plan Run, it is added after the previous Load Plan Runs for this Load Plan Instance. Note that the Load Plan Instance cannot be modified at run-time.



Load Plan Structure


A Load Plan is made up of a sequence of several types of steps. Each step can contain several child steps. Depending on the step type, the steps can be executed conditionally, in parallel or sequentially. By default, a Load Plan contains an empty root serial step. This root step is mandatory and the step type cannot be changed.




Working with Variables in Load Plans


Project and Global Variables used in a Load Plan are declared as Load Plan Variables in the Load Plan editor. These variables are automatically available in all steps and their value passed to the Load Plan steps.

The value of the variables are passed to the Load Plan on startup as startup parameters. At a step level, you can overwrite the variable value (by setting it or forcing a refresh) for this step and its child steps.


Note: At startup, Load Plans do not take into account the default value of a variable, or the historized/latest value of a variable in the execution context. The value of the variable is either the one specified when starting the Load Plan, or the value set/refreshed within the Load Plan.