problem:--- grant profile to the users.

answer:--- profile(connect, NG repository explorer,NG metadata admin) ----

1 can open packages, procedures,variables,sequences
2 cannot modify existing procedures and packages and also cannot view interfaces
3 cannot create new procedure,packages,variables ,sequences and interfaces
4 can create models and datastore and also modify
5 you cannot modify and create any thing in topology

profile(connect,repository explorer, metadata admin) ----

1 can open packages, procedures,and interface,variables,sequences
2 cannot modify existing procedures and packages and can view interfaces
3 cannot create new procedure,packages,variables ,sequences and interfaces
4 can create models and datastore and also modify
5 you cannot modify and create any thing in topology

profile(connect,NG designer) ----

1 can open packages, procedures,and,variables,sequences
2 can modify existing procedures and packages and cannot view interfaces
3 can create new procedure,packages,variables ,sequences and interfaces
4 can create models and datastore and also modify
5 you cannot modify and create any thing in topology
profile(connect,designer) ----
1 can open packages, procedures,and interface,variables,sequences
2 can modify existing procedures and packages and can view interfaces
3 can create new procedure,packages,variables ,sequences and interfaces
4 can create models and datastore and also modify
5 you cannot modify and create any thing in topology

profile(connect,NG designer,NG metadata admin) ----

1 can open packages, procedures,and,variables,sequences
2 can modify existing procedures and packages and cannot view interfaces
3 can create new procedure,packages,variables ,sequences and interfaces
4 can create models and datastore and also modify
5 you cannot modify and create any thing in topology

profile(connect,designer,metadata admin) ----

1 can open packages, procedures,and interface,variables,sequences
2 can modify existing procedures and packages and can view interfaces
3 can create new procedure,packages,variables ,sequences and interfaces
4 can create models and datastore and also modify
5 you cannot modify and create any thing in topology

problem:---JKM STEPS( oracle consistent set)

answer:----1 go to model and choose the right km(jkm oracle consistent)
2 right click on the model add to cdc or select the individual table
for which you want to start journal.
3 right click on model add subscriber.
4 right click on model start journal.
5 now create the interfaces and at source datastore in interface select the journal check box.
6 create a package and drag the model twice in the package.
7 select the first model and change the propery in the the properties option to journal model
and check the option extend window and lock subscriber and also add the subscriber in
properties.
 8 do the same for the other model but this time check the check box of unlock subscriber and
purge journal
and add subscriber in properties.
9 drag the interface in between the two models and connect.

problem:-- significance of start,add subscriber,remove subscriber,stop,extend window,lock

subscriber,unlock subscriber,purge
journal.
answer:---1 start box is to start the journals.(the step we perform manually for starting the
journal).
2 add subscriber box add the subscribers that we enter the list into the Subscribers window at
bottom window.
3 remove subscriber is to remove the subscriber that we enter the list into the Subscribers
window at bottom window.
4 stop box is to stop the journal.(the step we perform manually for droping the journal).
5 extend window gives the window id to J$ table which used to be blank before extending the
window.extend window
works on whole consistant set which means whole model it extend the window for all the table
of the model.
6 lock subscriber marks(snapshot) the data for that window set (extend window) which need to
be fetched.This operation
performs a subscriber(s) specific "snapshot" of the changes in the consistency window. This
snapshot includes all
the changes within the consistency window that have not been consumed yet by the
subscriber(s).
lock subscriber update the max window ID value in SNP_CDC_SUBS table.
7 unlock subscriber-- This operation commits the use of the changes that where locked during
the Lock Subscribers
operations for the subscribers. It should be processed only after all the changes for the
subscribers have been
processed.unlock subscriber update the min with max window ID value in SNP_CDC_SUBS
table.
8 purge journal--After all subscribers have consumed the changes they have subscribed to,
entries still remain in
the journalizing tables and should be deleted.

problem:---JKM STEPS( oracle simple)

answer:----1 go to model and choose the right km(jkm oracle simple)
2 right click on the model add to cdc or select the individual table
for which you want to start journal.
3 right click on model add subscriber.
4 right click on model start journal.
5 now create the interfaces and at source datastore in interface select the journal check box.
6 create a package and drag the intefaces in the package connect all of them.

problem:--- new features of odi.

answer:-- 1 odi studio
2 sumulation of execution.
3 stop immediate option in operator
4 dataset option for set operators (union ,minus ,intersection )
5 quick edit option in interface
6 lookup option in interface.
 7 partitioning option in interface.
8 use of native sequence(eg oracle sequence).
9 sdk.
10 java EE agent.
11 odi console (join the metadata nevigator and light weight designer)
12 new technologies are added in the topology.
13 Derived Select for Temporary Interfaces
14 Automatic Temporary Index Management

problem:-- odi tools

answer:--1 OdiExportAllScen -FROM_PROJECT=10022 -TODIR=/temp/ -RECURSIVE_EXPORT=yes
2 OdiExportMaster "-TODIR=/temp/" "-ZIPFILE_NAME=export.zip" "-XML_CHARSET=ISO-
8859-1" "-JAVA_CHARSET=ISO8859_1" "-EXPORT_VERSIONS=YES"
3 OdiExportWork "-TODIR=/temp/" "-ZIPFILE_NAME=workexport.zip"
4 OdiGenerateAllScen -PROJECT=1003 generates all scenarios in the project whose id is 1003
for the current repository.
5 To copy the remote directory /test_copy555 on the FTP server machine recursively to the
local directory C:\temp\test_copy:
OdiFtpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -
LOCAL_DIR=C:\temp\test_copy -REMOTE_DIR=/test_copy555
6 To copy the local directory C:\temp\test_copy recusively to the remote directory /test_copy555
on the FTP server machine:
OdiFtpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp\test_copy
-REMOTE_DIR=/test_copy555"
7 To copy the remote directory /test_copy555 on the SSH server machine recursively to the
local directory C:\temp\test_copy
OdiScpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -
LOCAL_DIR=C:\temp\test_copy -REMOTE_DIR=/test_copy555

To copy all files matching the Document*.txt pattern (this includes for example the files
Document.txt, Documentt.txt, and Documenttt.txt) under the remote directory / on the SSH server
machine to the local directory C:\temp\
OdiScpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp -
REMOTE_FILE=Document*.txt -REMOTE_DIR=/

To copy the Document1.txt file under the remote directory / on the SSH server machine to the
local directory C:\temp\ as a Sample1.txt file:
OdiScpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -REMOTE_DIR=/
REMOTE_FILE=Document1.txt -LOCAL_DIR=C:\temp -LOCAL_FILE=Sample1.tx
8 To copy the local directory C:\temp\test_copy recursively to the remote directory
/test_copy555 on the FTP server machine:
OdiSftpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp\test_copy
-REMOTE_DIR=/test_copy555

To copy all files matching the Document*.txt pattern (this includes for example the files
Document.txt, Documentt.txt, and Documenttt.txt) under the local directory C:\temp\ to the remote
directory / on the FTP server machine:
OdiSftpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp -
LOCAL_FILE=Document*.txt -REMOTE_DIR=/

To copy the Document1.txt file under the local directory C:\temp\ to the remote directory / on
the FTP server machine as a Sample1.txt file:
OdiSftpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp -
LOCAL_FILE=Document1.txt -REMOTE_DIR=/ -REMOTE_FILE=Sample1.txt
 9 OdiSendMail -MAILHOST=mail.mymail.com "-FROM=Application Oracle Data
Integrator<odi@mymail.com>" -TO=admin@mymail.com "-SUBJECT=Execution OK" -
ATTACH=C:\log\job.log -ATTACH=C:\log\job.bad
10 To copy the remote directory /test_copy555 on the SSH server machine recursively to the
local directory C:\temp\test_copy.
OdiSftpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -
LOCAL_DIR=C:\temp\test_copy -REMOTE_DIR=/test_copy555

To copy all files matching the Document*.txt pattern (this includes for example the files
Document.txt, Documentt.txt, and Documenttt.txt) under the remote directory / on the SSH server
machine to the local directory C:\temp\
OdiSftpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp -
REMOTE_FILE=Document*.txt -REMOTE_DIR=/

To copy the Document1.txt file under the remote directory / on the SSH server machine to the
local directory C:\temp\ as a Sample1.txt file.
OdiSftpGet -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -REMOTE_DIR=/ -
LOCAL_FILE=Document1.txt -LOCAL_DIR=C:\temp -LOCAL_FILE=Sample1.txt
11 To copy the local directory C:\temp\test_copy recursively to the remote directory
/test_copy555 on the FTP server machine.
OdiSftpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp\test_copy
-REMOTE_DIR=/test_copy555

To copy all files matching the Document*.txt pattern under the local directory C:\temp\ to the
remote directory / on the FTP server machine.
OdiSftpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp -
LOCAL_FILE=Document*.txt -REMOTE_DIR=/

To copy the Document1.txt file under the local directory C:\temp\ to the remote directory / on
the FTP server machine as a Sample1.txt file.
OdiSftpPut -HOST=disdev3 -USER=test_ftp -PASSWORD=<password> -LOCAL_DIR=C:\temp -
LOCAL_FILE=Document1.txt -REMOTE_DIR=/Sample1.txt
12 Concatenation of the files *.log of the folder: /var/tmp into the file /home/all_files.log
OdiFileAppend -FILE=/var/tmp/*.log -TOFILE=/home/all_files.log
13 Copy the file "host" from the directory /etc to the directory /home:
OdiFileCopy -FILE=/etc/hosts -TOFILE=/home/hosts
14 To delete the file my_data.dat from the directory c:\data\input, generating an error if it is
missing.
OdiFileDelete -FILE=c:\data\input\my_data.dat -NOFILE_ERROR=yes
15 Rename the "host" file into "hosts.old"
OdiFileMove -FILE=/etc/hosts -TOFILE=/etc/hosts.old
16 Wait indefinitely for file flag.txt in directory c:\events and proceed when this file is detected.
OdiFileWait -ACTION=NONE -DIR=c:\events -PATTERN=flag.txt -FILECOUNT=1 -
TIMEOUT=0 -POLLINT=1000
17 The command ...
OdiOutFile -FILE=/var/tmp/my_file.txt
Welcome to Oracle Data Integrator
This file has been overwritten by <%=odiRef.getSession("SESS_NAME")%>
... generates the file /var/tmp/my_file.txt on the UNIX machine of the agent that executed it.
18 OdiSqlUnload -FILE=C:\temp\clients.csv -DRIVER=sun.jdbc.odbc.JdbcOdbcDriver -
URL=jdbc:odbc:NORTHWIND_ODBC -USER=sa -PASS=NFNEKKNGGJHAHBHDHEHJDBGBGFDGGH
-FIELD_SEP=; "-DATE_FORMAT=dd/MM/yyyy hh:mm:ss"
select cust_id, cust_name, cust_creation_date from Northwind.dbo.Customers
generates the file C:\temp\clients.csv separated by ';', containing the result of the query on the Customers
table.
19 Unzip the file archive_001.zip from directory C:\archive\ into directory C:\TEMP:
OdiUnZip "-FILE=C:\archive\archive_001.zip" -TODIR=C:\TEMP\
20 Creation of an archive of the directory C:\Program files\odi:
OdiZip "-DIR=C:\Program Files\odi" -FILE=*.* -TOFILE=C:\TEMP\odi_archive.zip
21 Waits, with a polling interval of 5 seconds, for all the child sessions of the current session
named like "LOADxxx" and having the keywords "MANDATORY" and "CRITICAL", to be finished
OdiWaitForChildSession -PARENT_SESS_NO=<%=odiRef.getSession("SESS_NO")%> -POLL_INT=5 -
SESSION_NAME_FILTER=LOAD% -SESSION_KEYWORDS=MANDATORY,CRITICAL
22 Imports the /temp/DW01.xml export file (a project) into the WORKREP work repository using
DUPLICATION mode .
OdiImportObject -FILE_NAME=/temp/DW01.xml -WORK_REP_NAME=WORKREP -
IMPORT_MODE=DUPLICATION

problem:---types of facts and dimentions.

answer:--- Dimension -
A dimension table typically has two types of columns, primary keys to fact tables and textual\descreptive
data.
Fact -
A fact table typically has two types of columns, foreign keys to dimension tables and measures those that
contain numeric facts.
A fact table can contain fact’s data on detail or aggregated level.

type of facts---
Additive:
Additive facts are facts that can be summed up through all of the dimensions in the fact table. A sales fact
is a good example for additive fact.

Semi-Additive:
Semi-additive facts are facts that can be summed up for some of the dimensions in the fact table, but
not the others.
Eg: Daily balances fact can be summed up through the customers dimension but not through the time
dimension.

Non-Additive:
Non-additive facts are facts that cannot be summed up for any of the dimensions present in the fact
table.
Eg: Facts which have percentages, ratios calculated.

Factless Fact Table:

In the real world, it is possible to have a fact table that contains no measures or facts. These tables are
called “Factless Fact tables”.
Eg: A fact table which has only product key and date key is a factless fact. There are no measures in
this table. But still you can get the number products sold over a period of time.

Based on the above classifications, fact tables are categorized into two:
Cumulative:
This type of fact table describes what has happened over a period of time. For example, this fact table
may describe the total sales by product by store by day.
The facts for this type of fact tables are mostly additive facts. The first example presented here is a
cumulative fact table.

Snapshot:
This type of fact table describes the state of things in a particular instance of time, and usually includes
more semi-additive and non-additive facts.
The second example presented here is a snapshot fact table.
type of dimensions---
Conformed Dimension:
A Dimension that is used in multiple locations is called a conformed dimension.
A conformed dimension may be used with multiple fact tables in a single database, or across multiple
data marts or data warehouses.
Conformed dimensions mean the exact same thing with every possible fact table to which they are
joined.
Eg: The date dimension table connected to the sales facts is identical to the date dimension connected to
the inventory facts.

Junk Dimension:
A junk dimension is a collection of random transactional codes flags and/or text attributes that are
unrelated to any particular dimension.
The junk dimension is simply a structure that provides a convenient place to store the junk attributes.
Eg: Assume that we have a gender dimension and marital status dimension.
In the fact table we need to maintain two keys referring to these dimensions.
Instead of that create a junk dimension which has all the combinations of gender and marital status
(cross join gender and marital status table and create a junk table).
Now we can maintain only one key in the fact table.

Degenerated Dimension:
A degenerate dimension is a dimension which is derived from the fact table and doesn't have its own
dimension table.
Eg: A transactional code in a fact table.

Role-playing dimension:
Dimensions which are often used for multiple purposes within the same database are called role-playing
dimensions.
For example, a date dimension can be used for “date of sale", as well as "date of delivery", or "date of
hire".

Slowly Changing Dimensions:

Attributes of a dimension that would undergo changes over time.
It depends on the business requirement whether particular attribute history of changes should be
preserved in the data warehouse.
This is called a Slowly Changing Attribute and a dimension containing such an attribute is called a Slowly
Changing Dimension.

problem:-- scheduling steps in odi.

answer:---1 first modify the odiparam.bat or odiparam.sh parameters.
drivers , master rep username(database schema name),master rep encoded password(database schema
name),
work rep name(odi name in topology),odi username,odi user encoded password.
for encode the password go to path D:\bea\Oracle_ODI1\oracledi\agent\bin>encode.bat password
2 create the physical agent in the topology and map it with the logical agent.
3 again go to the path D:\bea\Oracle_ODI1\oracledi\agent\bin>agent.bat -NAME=Physical
agent name -PORT=port number
4 go the scenario add the schedule and select the context and logical agent and the time.
5 again go to topology and double click on physical agent and click on update the schedule .

problem:--difference between generic and non generic profiles.

answer:-- Generic profiles have the Generic privilege option checked for all objects' methods.
 This implies that a user with such a profile is by default entitled for all methods of all instances
of an object to which his profile is entitled.
Non-Generic profiles is not by default entitled for all methods on the instances, as the Generic
privilege option is unchecked for all objects' methods.
The administrator must grant the user the rights for the methods for each instance
For granting permissions for instances open user to which you want to grant privileges in
security manager
and from designer select that objet's instance and drag on that user it will open up a window
along with
privileges choose them and press ok.(in 10g its woriking but in 11g it's not still need to be
tested)

problem:--- physical schema ,physical agent,logical schema and logical agent.

answer:---1 physical Agent is a Java service which can be placed as listener on a TCP/IP port.
2 A logical schema is an alias that allows a unique name to be given to all the physical
schemas
containing the same datastore structures.
3 A logical agent is an alias that allows a unique name to be given to all the physical agents
with the same
function in different contexts.
4 The physical schema is a decomposition of the data server, allowing the Datastores (tables,
files, etc) to be classified. Objects stored in data
servers with this mode of classification can be accessed by specifying the name of the
schema attached to the object name.

problem:--- type of indexes in oracle.

answer:---- btree(binary tree) and bitmap.
btree--- 1 unique
2 non unique.
to create unique index---- create unique index abc on emp1(empno);
to create non unique index---- create index abc on emp1(ename);
to create index using multiple columns:---- create index abcd on emp (empno,ename,job);
to create function based index---- create index abc2 on emp1(upper(ename)); and create
unique index abc5 on emp1(upper(ename)); ,
create index comm_fun on emp (comm*2.5);
to create bitmap index use bitmap key word:--- create bitmap index abc3 on emp1(sal);
(bitmap cannot be unique type which means
we can not use unique keyword in create index syntax)
to check the type and uniqueness:----select index_name,index_type,uniqueness from
user_indexes; (for example)
INDEX_NAME INDEX_TYPE UNIQUENES
------------------------------ --------------------------- ---------
ABC NORMAL UNIQUE
ABC1 NORMAL NONUNIQUE
ABC2 FUNCTION-BASED NORMAL NONUNIQUE
ABC5 FUNCTION-BASED NORMAL UNIQUE
ABC3 BITMAP NONUNIQUE
PK_SNP_CDC_OBJ NORMAL UNIQUE
PK_SNP_CDC_TBL NORMAL UNIQUE
link for indexes----http://www.oracle.com/technetwork/articles/sharma-indexes-
093638.html.(to understand practically)
high-cardinality means-- (100-percent distinct)