Open the model, go to the Journalizing tab, and modify the order there.

Right-click Datastore, select Changed Data Capture, and then select Order.

Open the model, go to the Journalized tables tab, and modify the order there.

Open the data stores, go to the Journalizing tab, and modify the order there.

ODI topology does not allow defining more than one physical schema for a data server; the associated logical schema would be ambiguous.

It is possible to define more than one physical schema associated to the same data server, but it is mandatory to specify a different user to log in.

It is possible to define more than one physical schema associated to the same data server, but you must flag the default physical schema.

It is possible but it is better to avoid doing so because it is more difficult to define a logical schema this way.

This option is inherited from reverse engineering.

This option is always available.

You can never make this choice.

This option may be available only if the underlying technology supports it.

extracting source data to flat files

triggers

Oracle GoldenGate

before-and-after database image comparison

conditions

foreign keys

primary keys

alternate keys

not null

Use a dedicated schema such as ODI_STAGING.

Use TEMP.

Use the same schema as the Data Schema.

Use SYSTEM.

Open the Task in Operator, go to Code, click Edit, use Pre-execution Code to edit the code, andsave it.

It is not possible to modify the code once it has been generated.

Open the Step in Operator, edit the code, and save it.

Open the Task in Operator, go to Code, click Query/Execution Plan to edit the code, and save it.

Go to the Physical tab, select theFixedDesign check boxof the Physical Mapping Design.

Go to the Physical tab, select the Is Frozen check box of the Physical Mapping Design.

Go to the Physical tab, select the Read-only check box of the Physical Mapping Design.

Go to the Physical tab, deselect theModify check boxof the Physical Mapping Design.

Create a custom KM to handle this by using ODI variables defined at the Topology level to createunique temporary object names.

Use variables in the Logical Design of the Mapping to create unique temporary object names.

Create a custom Knowledge Module (KM) to handle this by using ODI variables to create uniquetemporary object names.

Select the Use Unique Temporary Object Names check box at the Physical Design level.

Run Exception and Restart

Run Exception and Continue

Run Exception and Ignore

Run Exception and Fail

Run Exception and Raise

by using Opatch

by using ODI Studio

by using the import/export utilities

by using Upgrade Assistant

They contain project and security information.

They contain data models and execution information.

They contain data and security information

They contain data models and project information.
Answer:

Create one Logical Schema per Physical Schema.

Create one Logical Schema per Physical Schema that stores the same type of data.

Create one Logical Schema per Data Server.

Create one Logical Schema per Context.

Add anOdiSendMailstep to My Package and link the My Third Package step to it by using a greenOK arrow.

Add anOdiSendMailstep to My Package and link the My Last Package step to it by using a red KOarrow.

Add anOdiReadMailstep to My Package and link the My Third Package step to it by using a red KOarrow.

Add anOdiSendMailstep to My Package and link the My Third Package step to it by using a red KOarrow.

Duplicate theIntegration Knowledge Module, add an optionCUSTOM_TEMPLATE, and set it withinthe Mapping.

Duplicate the Check Knowledge Module, add an optionCUSTOM_TEMPLATE, and set it within theMapping.

In the Physical tab of a Mapping, click one of the source data stores, select the Extract Options, andenter the SQL statement in theCUSTOM_TEMPLATEfield.

Duplicate the Loading Knowledge module, add an optionCUSTOM_TEMPLATE, and set it within theMapping

Add data stores to the package, set Datastores steps to Journalizing Datastore, and select theExtend Window and Lock Subscriber check boxes.

Add data stores to the package, set Datastores steps to Journalizing Datastore, and select theUnlock Subscriber and Purge Journal check boxes.

Add a model to the package, set the Model step to Journalizing Model, and select the ExtendWindow and Lock Subscriber check boxes.

Add a sub model to the package, set the Sub-model step to Journalizing Sub-model, and select theExtend Window and Lock Subscriber check boxes.

They contain data model and security information.

They contain security and topology information.

They contain project and topology information.

They contain project and security information.

Evaluate Variable

Set Variable

Declare Variable

Refresh Variable

They can have generic input and output signatures.

They contain both a Logical and Physical Mapping design.

They can be used within regular Mappings.

They can be executed directly.

They can be shared across projects.

Add a parallel step, add three serial steps underneath it, then addAto the first parallel step, B to the second one, and C to the last one.

Create a scenario from the variable and add the scenario to the load plan to create a case step

Add a parallel step, add two parallel steps underneath it, then add A and B tooneparallel step, and C to the other.

Add a parallel step, add two serial steps underneath it, then add A and B to one serial step, and C to the other.

ODI uses its own transformation engine to process data in a Hadoop cluster.

ODI performs data transformations inside a Hadoop cluster.

ODI must perform data transformations outside Hadoop in an Oracle database.

ODI allows moving data in and out of a Hadoop cluster.

Only an Integration KnowledgeModule single-technology is required.

Only an Integration Knowledge Module multitechnology is required.

A loading Knowledge Module multitechnology and an IntegrationKnowledgeModulesingletechnology are required.

Both a Loading Knowledge Module multitechnology and an Integration Knowledge Module multitechnology are required.

Create a single Mapping with two Physical Designs: one for the initial load and one for the incremental updates.

Create a single Mapping with a single Physical Design and modify it appropriately when an initial load is required or when an incremental update is required.

Create two Mappings: one for the initial load and one for the incremental updates. Duplicate the transformation logic.

Create a single Mapping and use variables in the Logical Design to do an initial load when required or an incremental update otherwise.

ERR$

ERROR$

ODI_ERR$

E$

You must consolidate your own local metadata repositories. The local metadata must be transmitted via ftp and synchronized with a dedicated proprietary engine, creating a common metadata model for all the developers.

You must consolidate your own local metadata repositories. You have to invoke a dedicated web service to synchronize the metadata by using Oracle Service Bus

You need not consolidate your own local metadata repositories, because the ODI proprietary metadata server allows all developers to share the common metadata of a specific project.

You need not consolidate yourown local metadata repositories, because ODI uses a centralized relational metadata repository that all the developers share.

Regenerate the existing scenario.

Nothing, the existing scenario will automaticallybe updated.

Generate a new scenario and create a new schedule.

Generate a new scenario and attach the previous scenario's schedule to it.

Create a procedure and add two tasks. The first one must have a Command on Source that reads
the email addresses from the database table and stores them in a bind variable, and the second must
have a Command on Target that usesOdiSendMailto send the email by using the bind variable
defined in the first task.

Createa Knowledge Module. Add a task with a Command on Source that reads the email addresses
from the database table and stores them in a bind variable, and a Command on Target that
usesOdiSendMailto send the email using the bind variable defined in the Command on Source.

Create a counter variable that gets the total number of email addresses stored in the database
table. Next, create another variable that selects the email addresses from the database table. Then,
create a loop in the packages by using the variables and anOdiSendMailstep.

Create a procedure. Add a task with a Command on Source that reads the email addresses from
the database table and stores them in a bind variable, and a Commandon Targetthat
usesOdiSendMailto send the email using the bind variable defined in the Command on Source.

It is only possible to see code at the Session level.

It is only possible to view code at the Task level.

Depending on the audit level declared when running the execution, some of the generated code at the step level can be viewed.

All generated code can be viewed together at the step level, with a complete list of executed code.

It is possible to set the execution location on source, staging area, or target.

All transformations are executed on the staging area.

Only the source and target servers can be used to execute expressions.

All expressions are executed on the source area

UseOdiPingAgentin a package to ping AGT agent.

In Topology, test the connections to servers A and B by using the AGT agent.

In Topology, test the connections to the AGT agent.

In Topology, test the connections to servers A and B by using Local (No Agent).

Data transformation must be distributed across several scalable nodes.

It is mandatory to have an intermediate server.

It is better to load data directly from sources into a data warehouse server.

It is mandatory to collect data directly from sources to a data warehouse server by using real time replication processes.

In the ODI Interface palette, choose the more convenient graphic objects to link the involved servers.

You need not draw directly in the data flow all the details about how the different servers involved are connected. ODI automatically designs the flow and how servers are connected.

You need not draw directly in the data flow all the details about how the different servers involved are connected. The code will be the black box generated directly by ODI.

You must draw directly in the data flow all the details about how the different servers involved are connected, and also specify with variables the passwords for connecting to the data contained in the servers.

Consistent set journalizing runs faster than simple journalizing.

Consistent set journalizing always uses Oracle GoldenGate.

Consistent set journalizing treats each data store individually.

Consistent set journalizing provides a guarantee of consistency of the captured changes.

The intermediate integration table prefixed with I$is required to determine which records must be inserted.

If Flow Control is not necessary, an I$ table is not created.

The intermediate integration table prefixed with I$ is createdbecause the flow control is mandatory when doing an initial load.

Neither the LKM northe IKM create intermediate tables. Most of their work is performed in the ODI Agent memory.

Create new submodels and drag data stores individually to each submodel.

Use automatic distribution feature at the models level to automatically create the submodels and move the data stores based on their names.

Create new submodels and leverage the automatic distribution feature at the submodels level to
automatically move the data stores based on their names.

Create new models, drag the data stores individually to each model and then drag the models to
the parent model to create submodels.

numeric

alphanumeric

date

text

Create a variable, useodiRef.getPrevStepLog ()in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Create a variable, useodiRef.getPrevInfo ()in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Create a variable, useodiRef.getStep ()in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

Create a variable, useodiRef.getPrevStepStatus ()in the SQL query in its Refreshing tab, and add a variable as a Refresh Variable step into the package.

on the Coherence Server

on the Administration Server

on the Node Manager

on the Managed Server

Add a sub-model to a package, set the Sub-model step to Journalizing Sub-model, and select the

Extend Window and Lock Subscriber check boxes.

Add anOdiSendMailstep to a knowledge module.

Duplicate theOdiSendMailstepinto multiple packages.

Create a procedure with a step that usesOdiSendMailand add this procedure

./agent.sh -NAME=OracleDIAgent1 -PORT=20910

./agent.sh -NAME=OracleDIAgent1

./startComponent.sh OracleDIAgent1

./startComponent.sh OracleDIAgent1 -PORT=20910

ODI Console allows administrators to edit users' information.

Enterprise Manager Cloud Control provides access to ODI data servers' settings.

ODI sessions can be monitored in Enterprise Manager Cloud Control.

ODI Console provides access to project and mapping details.

All distinct entries are processed.

Only the latest entry is processed based on theJRN_DATEfield.

Only the first entry is processed based on theJRN_DATEfield.

A PK violation occurs due to the duplicated entries and the entries are inserted in the E$ table.

by using Upgrade Assistant

by using ODI Studio

by using Domain Creation Assistant

by using Configuration Wizard

A. Use Consistent CDC, do not perform a purge of the journal data when the first Mapping gets executed, and manually change theJRN_SUBSCRIBERcolumn in the correspondingJ$table to keep the changed data present for the second Mapping.

Create a third mapping to copy the changed data to a staging table, which is used as the source ofthe second Mapping

Duplicate the source data store for each Mapping.

Create two distinct subscribers for each Mapping.

odiMasterRepository

MasterRepository

odimasterrepository

ODIMasterRepository

Add a case step and drag the variable into the case step.

Create a scenario from the variable and add the scenario to the load plan to create a case step.

Add a case step in the load plan and select a variable in the wizard.

Drag the variable into the load plan and define a case step.

Oracle BPEL Process Manager

Oracle GoldenGate

ODI Console

Oracle WebLogic Server

The Knowledge Module must be customized because business rules and the physical
implementation are strictly interlayed in ODI.

The Knowledge Module must be customized only for aggregation functions.

The Knowledge Module need not be customized because aggregation code is generated automatically by ODI according to the Mapping logic.

The Knowledge Module need not be customized, but a variable must be used in the aggregate expression to generate the correct sum.

Restart from new session.

Restart from failure.

Restart from failed children.

Restart all children.

OdiWaitForData

OdiWaitForCDCData

OdiWaitForLogData

OdiWaitForTable

restart from failed tasks

exception handling

native support for parallelism

support for Open Tools

restart of an agent

Their definition is imported with areverse-engineering process directly from databases and other sources, but you must manually define all keys and constraints existing on the database.

Their definition is imported with a reverse-engineering process directly from databases and other sources.

Forevery load the definition of the tables used, their columns and constraints must be manually built.

An external engine must be run to describe what metadata is needed for a Mapping.

Start a Mapping in Debug mode and use breakpoints and the Get Data feature to query the datacontained in the Staging tables.

Modify a Knowledge Module to dump the Staging tables' data into log files for review.

Use variables in a Package to query the Staging tables and evaluate the variable values.

Reverse engineer the Staging tables in a Model and review the data contained in it.

Select the Secure Value check box.

Select the Hide Value check box.

Set the Keep History field to No History.

Leave the Default Value field empty.

ODI Runtime Agent

ODI Standalone Agent

ODI JEE Agent

ODI Colocated Standalone Agent

They update or modify code to be executed, check security, select database servers, and updatelog files after execution.

They schedule scenarios to be executed, check security, constraints and update log files afterexecution.

They retrieve code from the execution repository and request database servers, operatingsystems,or scripting engines for execution.

They schedule code from the execution repository and update log files after execution.

Link the last step of the package to its first step to create an infinite loop.

Create a scenario from the package, add the scenario as the last step in the package, run it asynchronously, and then save and regenerate this scenario.

Create a scenario from the package, add the scenario as the last step in the package, run it asynchronously, and then save.

Drag the package to the last step in the package, run it asynchronously, and then save.

The execution should be done only on the development data environment, as long as the other environment is a mirrored copy.

Only the production environment can be used.

All environments linked to a logical schema can be used to reverse-engineer table structures.

Only a Java engine intermediate environment can be processed.

It enables developers to execute most ODI operations through a Java program.

It can be used to embed ODI processes into another product.

It is used to load data between Teradata and Oracle.

It must be used by ETL developers to develop ODI processes.

by using a custom Groovy script

by using a variable

by using the Timeout field

by using a Timeout knowledge module

transform only

load and transform

extract and load

extract and transform

Add a new subscriber and edit the default Journalizing filter in your Mappings.

Drop the journal, add a new subscriber, start the journal, and edit the defaultJournalizing filter in your Mappings.

Drop the journal, remove existing subscribers, add a new subscriber, start the journal, and edit the default Journalizing filter in your Mappings.

Add a new subscriber, start the journal, and remove the default Journalizing filter in your Mappings.

Oracle GoldenGate primarily performs aggregations for ODI.

GoldenGate and ODI are used together primarily for running weekly batch jobs.

Oracle GoldenGate provides non-invasive changed data capture capabilities to ODI.

ODI starts and stops Oracle GoldenGate processes automatically during a Mapping execution.

ODI and Oracle GoldenGate enable real-time business intelligence.

Right-click the step in Package Editor and select the No Logging menu item.

Modify Operator Navigator settings to disable that step from being displayed.

In Package Editor, click the step, go to the Advanced tab, and set Log Steps in the journal to Never.

Periodically schedule a scenario that usesOdiPurgeLogto remove that step from the ODI logs.

You can add a primary key even if it does not physically exist on the related database catalog, by adding constraintson the data store.

You can add a primary key even if it does not physically exist on the related database catalog, by adding constraints to the data store diagram.

You cannot add a primary key if it does not physically exist on the related database catalog. You can flag only non-null conditions to be checked.

You cannot add a primary key if it does not physically exist on therelated database catalog. You can reverse engineer only the existing constraints.

OdiOutFile

OdiFileCopy

OdiFileMove

OdiInFile

You need not deploy the generated code manually in a source or target server. ODI Agent coordinates the execution of commands prepared for the job, and executes them on the correct server.

You must deploy the generated code manually in a source or target server. You must then compile the generated code and then double-check if the code prepared for the development server is the same as the code for the production server.

You need not deploy the generated code manually in a source or target server. ODI prepares a package for the development environment.

You must deploy the generated code manually in a source or target server. You must copy all procedures generated into the development, test, and production servers.

This works only for Oracle and Informix.

This works only for Oracle and MySQL.

Create a new generic technology to support it.

Use the out-ofthe box Generic SQL technology.

The project must be explicitly mapped within an ODI mapping.

A customize knowledge module is needed.

An ODI procedure must be associated with it.

It can be defined for every technology listed in the topology.

It is not possible to enforce constraints on some technologies such as flat files and Java Messaging Service (JMS) queries.

It is not possible to enforce constraints on any technology.

It is only possible to forward-engineer it to the flat file definition.

It is possible to enforce a primary key on a flat file by using a CKM; however, you have to save it as a fixed file.

Variables

Datastores

Knowledge Modules

Reusable Mappings

the schema hosting the Work repository

the schema hosting theWork schema of the default schema defined for your source data server

the schema hosting the Staging Area

SYS

from the source database into flat files that are then loaded into the target database

directly from the source database to the target database

from the source database onto the server running the Agent and then into the target database

from the source database into the machine running ODI Studio and then into the target database

odiRef.getSession()

odiRef.getInfo()

odiRef.getPrevStepLog()

odiRef.getStep()

It is not possible to use a specific partition.

Only ODI variables can be used to filter the target table loading.

An option in the Mapping can be used to declare partitions but an ODI variable must be used to evaluate the correct partition value.

An option in the Mapping can be used to declare the partition that has to be used for the loading.

ODI automatically computes the load order based on the order on which the data stores were added to the Mapping.

You can use the Target Order field.

You can use the Target Load Order field.

You can use the Load Order field.

high availability

minimal footprint

access to WebLogic connection pools

management in Enterprise Manager Cloud Control