Drag ODISqlUnload utility from All or Files folder into package.

Go in General tab:

Sql query has to be executed on data server.

The query must be a SELECT statement or a call to a stored procedure returning a valid record set.

Target file location will be given there

JDBC driver and jdbc url have to be given

User and password

File format- delimited

Date format

SQL query
Drag ODISendmail utility from All or Internet folder

Go in General tab:

Mention the mail server

From and To

Subject

In attachment part, location will be same as Target file location of ODIsqlunload utility.

Message body will also be written here.

Open load plan go to exception tab on left side add exception and drag the
‘FAILURE_EMAIL_WITH_LOG_FILE’ scenario as below.
For Working with Connection issues:

Test the agents by going into topology and check that whether agent is running from studio or not.

Checking agent is up or not.

To check whether source and target database are connected or not check in model datastore by right
clicking to view data.

You can check agent is connected to database or not by testing the data server with agent.

Loading from file to table

Go in topology

Create the dataserver filegeneric

Give user and password for the dataserver

Then create physical schema

Give the name

And in schema and work schema directory write the location of source file to extract

Then create the logical schema

Pull down the correct physical schema in it with the given context.

Create the model folder

Create the model

Select the tech and the given logical schema in it.

Then create the datastore

Give the name of the datastore

Then in the resource name click on the magnifying glass to browse the source text file and open it.

Then go in files tab:

Select file format fixed

Select header as 1

Then record separator as MS-DOS.

Go in Attributes tab select reverse engineering and reverse the source file

For target table again we need to go in topology

Create the dataserver using jdbc driver url

Test the server using local agent.

Physical schema

Logical schema
Then create new model select logical schema

Then click reverse engineering

Select the context and agent

You can do selective reverse engineering as well by giving the table or view name in masking.

Then import KM if not

Then create new mapping

Drag the source file and target table

Connect it then it will ask for auto map.

You can do the auto map if column name is same in source and target.

If not you can edit the column mapping by clicking on Target table in logical tab in expression editor.

Then select the correct KM in physical tab.

Context

Agent

Agents are java components.

Agents are not data transformation server. They do not perform any data transformation but instead
only orchestrate integration process. They delegate data transformation to data servers.
Variable
ODI 12c features
Creating Procedures
Generating a scenario:
Scheduling a scenario:
Monitoring
Error records
Errors of ODI

Syntax error

Column length of source is greater than target.

Whether some column, joins or filter is executing on source or target also creates error.
Sequence number not allowed here error