Database Reference
In-Depth Information
Property
Description
With this, you can define the session log filename. The default session log filename is
SESSION_NAME.log
. You can also
define the parameters in this option. We will discuss the parameter file in detail later in the chapter. When you define the para-
meter, pass the value from the parameter file.
Session Log
File Name
Session Log
File Direct-
ory
With this, you can define the session log file directory. You can also define the parameters in this option. When you define the
parameter, pass the value from the parameter file.
Parameter
Filename
If you use the parameters and variables in your code, you need to pass the values from the parameter file. You can define the
parameters' filename and path here.
Enable Test
Load
You can select this option to allow only a few records to pass through the mapping. This option is useful when you are in the
testing phase of your project.
When you select the
Enable Test Load
option, you can define the number of records you wish to flow from
Mapping
. Sup-
pose you have 10,000 records to process. You can check the
Enable Test Load
option and mention the number of records you
wish to test. So, if you define 100 records, Informatica will only process 100 records out of the 10,000 records.
Number of
rows to test
$Source
connection
value
You can define the
Database Connection
value here. Consider that your database connection's name is
ORACLE
. If you define
ORACLE
at this place, you can select
$Source
in the
Mapping
tab for the source connection.
$Target con-
nection
value
You can define the
Database Connection
value here. Consider that your database connection's name is
ORACLE
. If you define
ORACLE
at this place, you can select
$Target
in the
Mapping
tab for the target connection.
This property allows you to treat records as
INSERT
,
UPDATE
,
DELETE
, or
DATA DRIVEN
for the records that come from a
source. The default property is
INSERT
, which indicates all the records that come from a source will be inserted into the tar-
get.
Treat source
rows as
The
DATA DRIVEN
property is selected when you use the update strategy transformation in
Mapping
. We will talk about the
update strategy transformation in
Chapter 7
,
The Lifeline of Informatica - Transformations
.
You can select either a source-based or a target-based commit type. The default property is the target-based commit type.
If you select a source-based commit type, Informatica commits the data into the target-based commit type for commit interval
and flush latency intervals. Flush latency is the time interval for which you wish to commit the data. If you define the flush
latency as 5 seconds and the commit interval as 10,000, Informatica will commit the data to the target-based commit type for
whichever interval it reached first. Flush latency is a property defined by the Informatica PowerCenter administrator. So, you
need not be worried about how to set up this property. In most cases, data is committed based on the commit interval, so we
don't use the flush latency property frequently.
Commit
Type
If you select the target-based commit type, Informatica commits the data based on the commit interval.
Commit On
End Of File
This option is selected by default. This property indicates that the records will be committed to the target. If the file contains a
smaller number of records, then the commit interval is defined.
