Transformations
Router[C/A]
-Provides multiple targets
from single source.
-Router allows to use a
condition .
-It tests the data for one or
more conditions.
Ex:- 1)to test data based on 3
conditions use one Router
transformation instead of 3
Filters
2) groups : Input/ Output
Output group 2types –user
defined and default
Aggregator [Ports :I/O/V]
-Performs calculations on
groups of data
[min,max,average,total]
-Use Aggregator to eliminate
the Duplicate rows in flat
files[Use group by ports]
-Components : Agg exp,group
by port, sorted input, aggregate
cache.
-Don’t use sorted input when
the session was incremental
aggregation & input data is
data driven.
Sorter[C/A]
-Allows to sort the data. We
can sort the data from source
transformation in ascending or -we can find Large or smallest
descending order according to numeric value in a group.
a specified sort key.
-The data which is passing
through Sorter is sorted
according to sort key.
Active:Can change the number
of rows that passes through it
Ex: Filter-Removes that do not
meet the filter condition.
Filter [C/A]
-In Filter we can pass only one
condition –It also allows to use
a condition to test data
-It tests the data for One
condition.
-To maximize session
performance use Filter as
close as to Source in the
Mapping
-Filter condition returns true
or false for each row passes
through it.
Expression[C/P]
-Expression is for
computations.
-It calculates a value.
-Expression performs a
calculation based on values
with in a single row.
Ex:- Based on the price and
quantity of a particular item,
you can calculate the total
purchase price for that item.
Rank[C/A]
-To select the TOP or
BOTTOM rank of data.
-we can select top 10
Clients in a company
Passive: It does not change the
no. of rows that passes through it
Ex:- Expression performs a
calculation on data .
SequenceGenerator[p/c]
-Is for generating Unique serial
numbers.
-We use this, when the data is
not coming from source.
-Provides two output ports:
NEXTVAL and CURRVAL.
-Generates numeric values.
-Can replace missing values.
Properties: start value/
increment by, end value,
Current value,cycle,
no.of cached values,reset
Stored
Procedure[p/c/u]
-Calls a procedure.
-It generates a status code to
know the stored procedure is
completed successfully or not.
-For maintaining databases we
use stored procedures.
Status code: Provides error
handling for the informatica
server during a workflow.
UN CONNECTED: to run
nested stored procedures.
NORMALIZER
-Use Normalizer instead of
Source Qualifier when you
normalize a COBOL source .
-Normalizes records from
COBOL and Relational sources
[in mapping designertransselect
Normalizer trans create.]
XML Source Qualifier [p / c]
-Use this only with an XML source
definition. -U can link only one
XML source qualifier to one XML
source definition. –It has one
input/output port for every column
in the XML source.
Lookup [ports: I/O/L/R]
-Lookup is mostly used to “if
target row present update else
insert “ kind of operation.
-I used to see whether the row
we are processing already
exists in the target or not
-If it exists update the target, if
not exists do an insert.
We use lookup
-to search for related value.
-to perform some calculations
-to search whether records
exists or not in the target table.
-lookup is basically used when
we want to get some value
based on some condition
-in lookup do SQL Override
first and then go for condition.
Properties:
Connected Lookup
1.we can use Dynamic or static
cache
2.Supports User defined default
values
3.Is used to fetch values based
on incoming values.
4.Connected Lookup is
connected in the mapping.
Dynamic Cache
1. we can insert rows into cache
as we pass to the target
2. when the condition is false,
server inserts rows
This indicates that the row is
not in the source or target table.
Look SQL override:
-Overrides the default SQL
statement to query the look up
table.
-Specifies the SQL statement to
use for querying look up values.
-Use only with lookup caches
enabled.
Persistent Cache:
If it is persistent we can save the
lookup cache files and reuse
them ,If non persistent the rows
will be deleted
Shared Cache
-We can share the lookup
cache between multiple
transformations.
-We can shared an unnamed
cache between transformations
in the same mapping.
-We can share named cache
between transformations in
the same or different mappings.
Un Connected Lookup
1.We can use a static cache
2.Does not supports.
3.Used for updating slowly
changing dimension tables.
4.not connected in the mapping.
5.use return port only in this
transformation
Static Cache
1.we cannot insert or update
rows
2. when the condition is
TRUE: server returns the value
from lookup table
FALSE: server returns default
value for connected & null for
unconnected
Joiner[C/A]
-Joins two related
heterogeneous Sources in
different locations
-We can use two relational
sources existing in separate
data bases.
-Two different ODBC sources.
Relational table and XML
sources with at least one
matching port we can join two
sources
-Joiner allows to join sources
that contain binary data.
Cannot Join in the following
Situations: -
-both input pipe lines originate
from the same SourceQualifier.
Normal : Based on the
condition the server discards all
rows of data from master and
detail source that do not match.
Master: Keeps all rows of
data from the detail source and
the matching Rows from the
master source . From the master
source it discards the
unmatched rows.
Detail outer : Keeps all rows
from the master source and the
matching rows from the detail
source.
Full Outer: keeps all rows of
data from both the Master and
Detail source.
SOURCE QUALIFIER
-to filter records when the
server reads source data.
-to specify sorted ports
-to select only distinct values
from source.
Properties: sql query, user define join,

MIGRATION:
-You need to check several
things before making folder
copies between environments:
-Have a backup Of dev, QA,
and Production repository.
-No informatica jobs are
running or scheduled to run
during the folder copy time.
-You must wait until jobs
finish, or stop all jobs before
doing the move.
-Remove locks, make sure users
are out of development, QA,
Production repository before
moving any folders. -Be sure
all work has been saved
-View locks and remove all old
locks that still remain after all
developers logged out.(no jobs
are running)
-Copy shared folders first, then
project folder.
-Stop and start informatica
services-Be sure scheduled
jobs come backup.
Moving Mappings,Sessions,
etc from Development to
production environment
-Copy development folder to
production folder using folder
copy option in repository
manager. -In this way all the
source and target tables and
mappings will be copied to
production environment.
-Copy option will get all the
objects to the production .
Export/Import will have to be
done separately for mapping,
session etc. -When we copy a
folder from one Repository to
another Repository every thing
will be copied into the moved
Respository: Stores
information or metadata used by
informatica server and client
tools.
Metadata: Represents diff
types of objects like mappings,
transformations, source
definitions, Target definitions.
Metadata Repository:
-Is a web based application that
allows you to run reports.
-Provides number of reports,
including reports on executed
sessions, mappings, and source
and target schemas.
-Providing information on how
to install and use the web based
metadata reporter to generate
reports on metadata.
Bad data handling:
We can clean the bad data before
doing informatica loading by
using some scripts (shell scripts)
which will check for number of
columns/ date format/ numeric
values/ size for data files.
Surrogate Key
-It has system generated
artificial primary key values
-It allows to maintain
historical records in DW .
-SK is unique for each row in
the table.
-SK is a substitution for the
natural primary key.
-Is is just a unique identifier or
number for each row.
source filter, no.of sorted ports, pre, post sql
Testing Mappings And
Sessions
-We have to write the test cases
that business validity and also
to make sure that we are getting
the right target.
Example to make it clear:
-Let’s say you are extracting
data from source into staging
area, in that case
-One of your test cases will be,
to check the row count of
source and then the row count
of the staging tables and
compare the results. Row
count should be Match.
Usually when we talk of DW
Testing, most of the times we
have to write the SQL queries to
do the testing against source,
staging and Target.
We have to check for:
1.Source- Target Validation
2.Scheduling Process
3.Constraints
4.Full load, Delta Load, Reload
Processes.
5.Business Logic
6.All DLL definitions
-We have QA lead, we will talk
to him.
-Depending upon data different
validations are done (eg: date,
concats etc)
Unit Testing: is testing the
single module or mapping.
Integration Testing:
Combining two modules or
mappings and checking whether
data is getting reflected in
another module.
Repository.
Session log files:
-Server creates session log file
for each session.
-It writes information about
session
into log files such as
initialization
process, creation of SQL
commands
for errors and load summary.
Session Detail File:
-This file contains load
statistics for each target in
mapping.
-Includes information such as
table name, number of rows
written or rejected.
Performance detail
file:
Contains information about
performance
Reject File:
This file contains the rows of
data that the writer does not
write to targets.
Control Files:
Contains the information about
the target flat files such as data
format and loading instructions
Session Parameters:
Source File Name: use the
parameters when you want to
change the name or location of
session source file between
session runs.
Target File Name: is used
when u want to change the
name or location of session
target file between session runs.
Reject file name: is used when
u want to change the name or
location of session reject file
MAPPING
PARAMETERS and
VARIABLES.
Mapping Parameters: -
-Represents a constant value.
-We can define before running a
session.
-In parameter file we can define
Mapping parameters and
Variables and Session
Parameters.
-Mapping Parameters retains
the same value through out the
entire session.
EX: In my project instead of
creating separate mappings for
each Client or Customer, We
created a mapping for single
Customer.
-Before running the session, Enter
the value of the parameter in the
Parameter File.
Mapping variable:-
-Mapping Variables and
Parameters represents a value
that can change through the
SESSION.
Parameter File:
-Parameter File is to define the
values for Parameters and
Variables used in a session.
-It is created by Text editor
such as Word pad or Note pad.
-In Parameter file we can define
Mapping parameters, Mapping
variables and Session
Parameters
Recovering Sessions:
-If you stop a session or if an
error causes a session to stop,
refer to the session and error
logs to determine the cause of
failure.
-Correct the errors and then
complete the session:
Use one of the following to
complete the session:
 Run the session again if
the server has issued a
commit.
 Consider performing
recovery if the server has
issued at least one
commit.
Recovering stand alone
session:
-A stand alone session is a
session that is not nested in a
batch.
-If a stand alone session fails
we can recover by using a
menu command or pmcmd.
-These options are not available
for batched session
Q. I am trying to run a
workflow with a parameter file
and one of the session keeps on
failing?
Ans: In the parameter file, the
parameter may not be listed
 The session uses the
parameter file to start all
sessions in the WF.
 Check the session
properties see whether
session parameters are
defined correctly in the
parameter file
 Use pmcmd to start the
between session runs.
Target LoadOrder[Joiner
Transformation-designer]
“Setting the order in which
the server sends rows to
different target definitions in
a mapping”
--To set the Target Load Order:
1.Create a mapping that contains
multiple Source Qualifier Trans.
2.When the mapping is completed,
select Mappings -Target Load
Plan[dialog box]
3.Select a Source Qualifier from
the list.
4.Click the up and down buttons
to move the Source Qualifier
within the load order – ok -save
-Constraint based Loading[WFM]
EX: 1. ‘A’ has a primary key, B and
C has foreign keys referencing
the ‘A’ primary key.
2. C - has Primary key , that D
references as a Foreign key.
These four tables receive records
from a single active source.
LOAD MANAGER
When the server runs a WF ,the
Load manager:
-Locks the workflow and reads
workflow properties.
-Reads the parameter file and
expands workflow variables.
-Runs workflow tasks. –Starts the
DTM to run session
DTM:
When the server runs a SESSION ,
The DTM :
-Fetches session and mapping from
the repository.
-Creates the session log file.
-Runs pre-session shell commands.
-Creates and runs mapping reader ,
writer and transformation threads to
extract, Transform and load data.
-Runs post-session shell commands.
Aggregator
trans- Performance.
To improve the performance of
Aggregator and Session use
SORTED INPUT.
Aggregate Cache
-Server Stores group values in an
index cache and row data in the
data cache.
-Filter before aggregation.
-We cannot use sorted input when
the source is Data driven.
IncrementalAggregation a COBOL Copy book(.cpy
-If we run the session with
incremental aggregation enabled,
we should not do modifying the
index which store Historical
aggregate information.
Sorted Input
-Shows that input data is pre sorted
by groups.
Data driven
-Is a default option if the
mapping for the session
contains an update
strategy transformation.
-If we do not choose Data driven -If the ( .cbl ) file and ( .cpy )
when a mapping contains an
Update Strategy, The Work
Flow Manager shows a warning. for the location of the ( .cpy )
session.
Cobol Copy Book
-Must be a text file.
-A period must exist at the end
of the line to separate one line
from the other.
-Field names cannot have
parenthesis( )
-The level of record type from 1
to 99 must start with a zero( 0 ).
Working with COBOL Copy
books...
-The designer cannot recognize
file) as a COBOL file (.cbl),
because it lacks the proper
format.
-To import the COBOL copy
book in the Map Designer, we
can insert it into a COBOL file
template by using the COBOL
Statement " COPY ".
-After we insert the Copy book
file into the COBOL file
template, we can save the file
as a ( .cbl ) file and import it in
the Designer.
file are not in the same local
directory, the designer prompts
file.
-When the COBOL Copy book
file contains tabs,The designer
expands tabs into spaces.
-By default the designer
expands a tab character into 8
spaces
-The OCCURS Clause
specifies the number of
repeated occurrences of data
items with the same format in
a table.
-The REDEFINES Clause is to
have multiple field definitions

Partitioning [workflow DEBUGGER
manager] “ I used to find out the changes
between the transformations and
Round Robin partition:
-To process each partition
approximately the same number
of rows.
Hash partition
-To group rows of data among
partitions server uses hash
function.
-In Hash partition there are two
types of keys.
Hash auto-keys: Use at RANK,
SORTER
Hash user keys: To generate the
partition key specify a number of
ports.
Key Range Partition:
-If the Sources or Targets in the
pipeline are partitioned by key
range we use key range partition.
1) Set the partition type at the target
instance to key range.
2) Create 3 partitions
3) Choose ITEM_ID as the partition
key.
4) Set the key ranges as follows
ITEM_ID Start Range End
Range
Partition#1 1000 3000
Partition#2 3000 6000
Pass Through [default]
-We use this when we want to
increase the performance.
-By default mapping contains this
at Source Qualifier and Target
Instance.
what level the change is occurring”.
When we run the debugger , the
designer displays:
Debug log:View message from the
Debugger.
Target window: View target data.
Instance Window: View
transformation data
-The DEBUGGER runs a workflow
for each session type.
We can run the Debugger
-Before running the Workflow.
-After running the Workflow.
DEBUG PROCESS:
1)Creating break points: Create in
mapping to find out the error
condition.
2)Configure the debugger:
3)Run the Debugger:
The server reads the break points
and Pauses the Debugger when
the break points evaluate to
TRUE.
Power center
-allows controlling of several
systems from a central point.
-allows global repositories.
-gives you the ability to partition
your loads for performance.
This allows multiple reader and
writer threads.
-Power center is for EDW.
-Power center can source data
from mainframe, legacy,
ERP,EAI
for the same storage
SLOWLY CHANGING
DIMENSIONS
TYPE 1 : Current data
-New row insert it
-Any update in source, update the
target.
-Insert or Update.
“to keep the recent values in the
target”
TYPE 2: History
-New row -> Insert it.
-Any update in source- Insert a
new row
“to keep full history of changes in
the target,( PK is changed)”.
TYPE 3: History and current.
-New row – Insert it.
“to keep the current and previous
values in the target”.
Those dimensions which will
change over time are SCD.
Power Mart
-does not
-does not
-One reader and writer thread.
-Power mart is for data mart
needs.
-Can source data from relational
and flat files.
MAPPLET/ WORKLET/ PMCMD
Mapplet:
-If we are using the same set of
Transformations in N number
of mappings then we will create
that particular set as a single
mapplet.
-You can't put a mapplet inside
another mapplet.
-Mapplets are like pre-processor
macros not like sub-routines –
when the session is loaded,
every mapplet instance is
replaced by contents of the
mapplet.
You cannot use the following
objects in a Mapplet
1.Normalizer Trans, 2.Cobol
Sources 3.XML Source
Qualifier Transformation.
4.XML sources, 5.Target
Definitions 6.Other Mapplets.
Worklet:
-Worklet is like another task but
actually it contains set of tasks.
-Create Worklet when you want Workflow
to reuse a set of Workflow
logic in several workflows.
“I used worklets with in
workflow and just scheduled
that one workflow”
pmcmd using in unix
unix prompt$ pmcmd <enter>
pmcmd>connect –U user name
-p password –s server name:
port no <enter>
pmcmd>getwfdetails –f folder
name WF name<enter>
displays :[user name,password,
start time, end time ,fail?succ?]
pmcmd>getsessiondetails –f
WORKFLOW / PMCMD FOLLOWING Mapping Standards
Workflow: Following Mapping
-My datamart is with 3 batch Standards:
incremental load
-Minimize the use of Stored
-We already have batch sessions
Procedures
running as workflow
-So I have been assigned with Naming Conventions—like
multiple assignments which are giving specific names
under workflow. -Error Handling
Scheduling Workflow Audit Maintainance
There are 3 options -How many input records you
1)Run on demand->Manual are getting
-Should not be checked if U -How many records loaded into
have any of the scheduler warehouse-How many errors
settings on. Process Tracking—
2)Run continuously-> -Which map, which session,
-As per schedule but start on which table got invoked
server Initialization. during
-is a special option to keep in the ETL process
loop. -because we are not touching
3)Run on server initialization-> the
-As per Schedule but starts on metadata
Server initialization, But -According to the audit they
continuous. need the statistics of the ETL
-check this only if U want to process in their warehouse
run the session on initializing. [Find in Repository]
-In workflow manager the Event- If Running Concurrent
wait and Event-Raise tasks are to
Sessions[fails]
control the sequence of task
execution in the workflow. -In WF-Manager select session
-Tasks we create in Workflow and in general tab: select FAIL
manager are non-reusable, Tasks we PARENT if this TASK fails
create in Task Developer are and fail parent if this task
reusable. does not.
pmcmd
-Run workflow by using PMCMD
command.
Command : pmcmd Start workflow
–s ip of infa server. port-U****-
P****-F Folder_ NAME_Wait
Workflow_name`.
-pmcmd is used to communicate
with the Informatica server.
-Used to start and stop workflows
and Tasks.
 worklet.session name
Informatica performance tuning
-If you look at session log, you will
come to know which part of the
mapping took long time.
-The SQL in the Source Qualifier
might take long time to return
results since you are joining 3
large tables.
-The Lookup cache creation will
also take much time to cache 20
million records.[This can be tuned
by having Dynamic Lookup-
Persistent cache]
-If you feel that Normalization takes
much time then try to replace the
Normalizer with an Expression
using right logic.
-Avoid using unwanted ports in the
Transformations.
Target Bottlenecks:
We can identify target bottlenecks
by configuring the session to write
to a flat file target. If the session
increases when you write to a flat
file, You have a target bottleneck.
Tuning:- Drop indexes and key
constraints. -- Use bulk loading.
-Increase database network packet
size. – Optimize target database.
Source: Extract the query from
the session log and run it. Measure
the time. If there is difference then
go for tuning
Tuning: Optimize the query. Use
conditional filters.
Error (Session)
-Data type mismatches. – Column
Value truncated, Table or View
does not exists in the database.
-Out of table space.
Handling
-Check the session Log (Run a test
loads with Verbose mode ON to
give more information about data).
-Check for directory paths.
-Check for the Source file names.
-Check for the source and Target
Database connections-Remove the
Test load option after testing is
1.Eliminate Unnecessary ports in -Creating Indexes
Source Qualifier.
2.Add where clause where ever
necessary.
3.Create indexes on lookup
condition ports.
4.Indexing each column in the
lookup condition can improve
session Performance.
Particularly large lookup tables. Explain Plan:-
5.Do not select the row into a
lookup unless that row is
needed.
6.Use Bulk loading.
-Disable the index updates during SQL> EXPLAIN PLAN/ SET
the bulk load and then refresh
the indexes after the load.
-This is generally faster than
dropping and rebuilding indexes.
7.The lookup cache creation will
also take much time to catch
millions of records. [this can be
tuned by having dynamic
lookup – persistent cache]
8.Create appropriate indexes on
target table.
Read performance
-Reduce the no. of records
processed.
-Move the Filters/Aggregations to
the beginning [ next steps
processes number of records]
Write performance
-Drop indexes before loading [ if
update is not there]
-Disable constraints before load and Options:
re-enable the constraints after load.
-Consider increasing the commit
level.
Qes: When you are running a
session, Ur mapping is fine.Ur
session is fine and Ur session ran
successfully.But the data is not
loaded into ur Database.
Ans:- Could be in test load. – If it is
an Incremental load then the source
record might be already existing in
the Target table.
Oracle performance tuning
-Enough Table Spaces
-Avoiding too many spaces
-Set SQL TRACE ON to display
the statistics.
-Use auto trace function in
SQL*PLUS to automatically see
the Explain Plans.
-Use HINTS where ever needed.
EXPLAIN PLAM gives you the
plan how your query will be
executed, also gives you the
“Cost” of the query.
statement_id = ‘emp_sal’ FOR
SELECT ename,job,sal,dname /
FROM emp,dept
WHERE emp.deptno=dept.deptno
AND NOT EXISTS (SELECT *
FROM sal grade WHERE emp.sal
BETWEEN losal AND hisal);
SQL>EXPLAIN PLAN FOR
SELECT * FROM emp;
SQL>DESC plan_table;
SET TRACEON: Creates a trace
file.
TK PROF:- Just a translator that
converts trace file into a readable
format.
-Parsing/Optimizing/Executing
$TKPROF Ora_12558.trc
trace.txt file stored in a
formatted version trace.txt.
TKPROF Command Line
-EXPLAIN/TABLE/SYS/SORT/
RECORD/PRINT/INSERT.
-Use Hints.
 done.-Run debugger
-Target Load Option as “Normal”.
Importing Sources
Importing Excel sheets [source]
Open the Excel file.
-Select the columns and rows that
you need to use as source.
-In the first row, enter the column
names as it is for table(don't
include spaces).
-Then select from that row onwards
till the column you require.
- Now click (on the menu) Insert
Name -->Define.
If U have many sheets create ranges
for each of the sheets
2. Format numeric columns as
'Number'
3. Save the file.
4. Create an ODBC DSN pointing
to the file
Now in Informatica- Designer,
choose 'Import from Database' and
specify the DSN name and then
choose the tables to be imported.
Importing Flat files
Flat file
-While importing flat file into the
source it will ask for delimiters.
-At that place there is a check box
to enable to treat the consecutive
characters as Delimiters. Just
enable it.
-When u click on “import from file”
in the source menu , in the source
analyzer in the second screen there
exists a check box to treat
consecutive delimiters as one.
-Check or Uncheck this as per your -In web application we can
Requirement.
Upgrading from version 6.2 to 7.0
-Make a backup of the repository on be available to others.
the server.
-Repository->file->export->to
location on the same server.
-Uninstall Informatica 6.2 –Install
Informatica 7
-Repository 7.1->import->from the -Is used to create a
same server.
Informatica Versions differences
Informatica 5x Informatica 6x
1.In 5x we will have to delete 1.In version 6x we can over
the existing mapping and write the existing mapping
session and copy the Updated and session.
one 2.From version 6x it is
2.We can not pass a parameter possible.
in Lookup SQL Over ride till 3.You can create flat file target
5x. definitions in the Designer to
3.Informatica 5x has output data to flat files.
server manager 4.You can include multiple
SQT in a mapplet.
5. 6x has workflow manager
and to watch the execution
workflow monitor.
6. Cannot do lookup on flat
files.
Informatica 7x 7x.Union Transformation
-UNION,CUSTOM,XML -is used to merge data from
STREAM transformation. pipeline branches into one
-Lookup on flat files. pipeline branch.
-Grid Technologies[ server -It merges data from multiple
sources similar to the UNION
Grid]- here servers running
on different operating systems ALL SQL statement to
can coexist on the same server combine the results from two
grid. or more SQL statements.
-You can import and export -The Union Transformation
repository objects [both does not remove duplicate
dependent and independent] rows.
-You can even use PMCMD -We connect heterogeneous
Repository. sources to this transformation
-In this we can create multiple
move the mapping which will input groups but only one
output group.
Custom transformation
-creates transformation
applications, such as sorting
and aggregation.
transformation that requires
multiple input groups, output
groups or both.