1.

How configuration management (Version control) takes place in odi

1-create a mapping
2-right click on that and genarate the senario. Fisrt time it will generate vers
ion 1
3-do some changes to the mapping and generate the scenario again. it will genera
te the next version
3-Update ur package/load plan to use the next version of the generated scenario.
2. Load Plan and Scenario difference.
1-Load plan is the highest component in a operator
2-A load plan can have multiple scenarios
3-Scenarios are the executable code .It can be a package/mapping/procedure
4-It always best practise to use a scenario in a load plan instead of a direct m
apping as scenarios are all ready compiles and faster
5-We can schedule the load plan.(parallel /dependent load)
6-A package scenario will simplify the work of a developer by making a multi-ste
p process into single click executable.
7.In Load plan, the scenarios will be executed In either serial or parallel mann
er. Load plan cannot be represented diagrammatically which is the case in a pack
age.
3.(create master and work repository schema for ODI)
How to create master and work repository on the DB
create user ODI_Master_Rep identified by Oracle_1 default tablespace Users tempo
rary tablespace temp;
grant connect, resource to ODI_Master_Rep;
create user ODI_Work_Rep identified by Oracle_1 default tablespace Users tempora
ry tablespace temp;
grant connect, resource to ODI_Work_Rep;
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/odi_11g/odi_ma
ster_work_repos/odi_master_work_repos.htm
4.Project Life Cycle of ODI
The project life cycle depends on the methods and organization of your developme
nt team. The following steps must be considered as guidelines for creating, work
ing with and maintaining an integration project.
Create a new project and import Knowledge Modules for this project.
Define the project organization and practises using folders, markers and documen
tation.
Create reusable components: mappings, procedures, variables, sequences. Perform
unitary tests.
Assemble these components into packages. Perform integration tests.
Release the work in scenarios.
Optionally, organize scenarios into Load Plans. See Chapter 15, "Using Load Plan
s."

5.How to create a project in ODI

1.topology tab-->physical architecture -->technology-->add the physical schema (
add if does not exist)
2.topology tab -->logical architecture -->technology-->add the physical schema a
nd assign the corresponding physical schema(add if does not exist)
3.designer tab-->create the model-->
6.Oracle technology not listing under logical archetecture
left pan.right top corner - uncheck hide unused technology
or u can directly asign the logical schema to physical schema .
both the way it can be done
7. What are the types of Knowledge Modules?
1.LKM(used to extract data from heterogeneous source systems (files, middleware,
databases, etc.) to a staging area).
2.IKM(used to integrate (load) data from staging to target tables)
3.RKM(used to perform a customized reverse-engineering of data models for a spec
ific technology. It extracts metadata from a metadata provider to ODI repository
. These are used in data models.)
4.JKM(used to create a journal of data modifications (insert, update and delete)
of the source databases to keep track of changes. These are used in data models
and used for Changed Data Capture.)
5.CKM( used to check data consistency i.e. constraints on the sources and target
s are not violated. These are used in data model s static checks and interfaces flow
checks. Static check refers to constraint or rules defined in data model to ver
ify integrity of source or application data. Flow check refers to declarative ru
les defined in interfaces to verify an application s incoming data before loading in
to target tables.)
8. Explain some differences between ODI 10g and ODI 11g and ODI12c
ODI 11g provides a Java API to manipulate both the design-time and run-time arti
facts of the product. This API allows you for example to create or modify interf
aces programmatically, create your topology, perform import or export operations
, launch or monitor sessions. This API can be used in any Java SE and Java EE ap
plications, or in the context of Java-based scripting languages like Groovy or J
ython.
External Password Storage, to have source/target data servers (and contexts) pas
swords stored in an enterprise credential store. External Authentication, to hav
e user/password information stored in an enterprise identity store (e.g.: LDAP,
Oracle Directory, Active Directory), and ODI authenticating against this store.
These two features let you optionally store critical information in dedicated st
orages and not within the ODI repository. The ODI Console may also use Oracle's
single-sign on systems with ODI.
9.what is does odi uses HSQLDB ?
1. Running from cron job
2. Preload and post load
3. Identify the mapping and do the design and analysis
1. Parameter files in ODI
2. Synonyms public vs private
3. Source qualifiers (How to call procedure in a mapping)
4. Complexity Analysis
5. Source qualifier and mapping
4. Environment setup
--------------------
difference betwwn package and load plan
what are agents
enable CDC
FLEXI FIELDS
DATA MIGRATION DO A DEMO
HOW TO CALL WEB-SERVICES FROM odi AND VICEVERSA
HOW TO DO EXCEPTION HANDLING
How IKM incremental update is different from JKM
what is plsql tables