Log Options Settings

By PenchalaRaju.Yanamala

Log options allow you to configure how you want to save the session log. By
default, the Log Manager saves only the current session log.

Table 8-2 shows the Log Options settings of the Config Object tab:

Table 8-2. Config Object Tab - Log Options Settings

Log Options Description
Settings
Save Session Configure this option when you choose to save session log files.
Log By If you select Save Session Log by Timestamp, the Log Manager
saves all session logs, appending a timestamp to each log.
If you select Save Session Log by Runs, the Log Manager saves a
designated number of session logs. Configure the number of
sessions in the Save Session Log for These Runs option.
You can also use the $PMSessionLogCount service variable to
save the configured number of session logs for the Integration
Service.
Save Session Number of historical session logs you want the Log Manager to
Log for These save.
Runs The Log Manager saves the number of historical logs you specify,
plus the most recent session log. When you configure 5 runs, the
Log Manager saves the most recent session log, plus historical
logs 0-4, for a total of 6 logs.
You can configure up to 2,147,483,647 historical logs. If you
configure 0 logs, the Log Manager saves only the most recent
session log.

Error Handling Settings

Error Handling settings allow you to determine if the session fails or continues
when it encounters pre-session command errors, stored procedure errors, or a
specified number of session errors.

Table 8-3 describes the Error handling settings of the Config Object tab:

Table 8-3. Config Object Tab - Error Handling Settings

Error Description
Handling
Settings
Stop On Errors Indicates how many non-fatal errors the Integration Service can
encounter before it stops the session. Non-fatal errors include
reader, writer, and DTM errors. Enter the number of non-fatal
errors you want to allow before stopping the session. The
Integration Service maintains an independent error count for each
source, target, and transformation. If you specify 0, non-fatal errors
do not cause the session to stop.
 Optionally use the $PMSessionErrorThreshold service variable to
stop on the configured number of errors for the Integration Service.
Override Overrides tracing levels set on a transformation level. Selecting
Tracing this option enables a menu from which you choose a tracing level:
None, Terse, Normal, Verbose Initialization, or Verbose Data.
On Stored Required if the session uses pre- or post-session stored
Procedure procedures.
Error If you select Stop Session, the Integration Service stops the
session on errors executing a pre-session or post-session stored
procedure.
If you select Continue Session, the Integration Service continues
the session regardless of errors executing pre-session or post-
session stored procedures.
By default, the Integration Service stops the session on Stored
Procedure error and marks the session failed.
On Pre- Required if the session has pre-session shell commands.
Session If you select Stop Session, the Integration Service stops the
Command session on errors executing pre-session shell commands.
Task Error If you select Continue Session, the Integration Service continues
the session regardless of errors executing pre-session shell
commands.
By default, the Integration Service stops the session upon error.
On Pre-Post Required if the session uses pre- or post-session SQL.
SQL Error If you select Stop Session, the Integration Service stops the
session errors executing pre-session or post-session SQL.
If you select Continue, the Integration Service continues the
session regardless of errors executing pre-session or post-session
SQL.
By default, the Integration Service stops the session upon pre- or
post-session SQL error and marks the session failed.
Error Log Type Specifies the type of error log to create. You can specify relational,
file, or no log. By default, the Error Log Type is set to none.
Error Log DB Specifies the database connection for a relational error log.
Connection
Error Log Specifies table name prefix for a relational error log. Oracle and
Table Name Sybase have a 30 character limit for table names. If a table name
Prefix exceeds 30 characters, the session fails.
Error Log File Specifies the directory where errors are logged. By default, the
Directory error log file directory is $PMBadFilesDir\.
Error Log File Specifies error log file name. By default, the error log file name is
Name PMError.log.
Log Row Data Specifies whether or not to log transformation row data. When you
enable error logging, the Integration Service logs transformation
row data by default. If you disable this property, n/a or -1 appears
in transformation row data fields.
Log Source Specifies whether or not to log source row data. By default, the
Row Data check box is clear and source row data is not logged.
Data Column Delimiter for string type source row data and transformation group
Delimiter row data. By default, the Integration Service uses a pipe ( | )
delimiter. Verify that you do not use the same delimiter for the row
data as the error logging columns. If you use the same delimiter,
you may find it difficult to read the error log file.
Partitioning Options Settings

When you configure dynamic partitioning, the Integration Service determines the
number of partitions to create at run time. Configure dynamic partitioning on the
Config Object tab of session properties.

Table 8-4 describes the Partitioning Options settings on the Config Objects tab:

Table 8-4. Config Objects Tab - Partitioning Options

Partitioning Description
Options
Settings
Dynamic Configure dynamic partitioning using one of the following methods:
Partitioning Disabled. Do not use dynamic partitioning. Define the number of
-partitions on the Mapping tab.
Based on number of partitions. Sets the partitions to a number
that you define in the Number of Partitions attribute. Use the
$DynamicPartitionCount session parameter, or enter a number
-greater than 1.
Based on number of nodes in grid. Sets the partitions to the
number of nodes in the grid running the session. If you configure
this option for sessions that do not run on a grid, the session runs
-in one partition and logs a message in the session log.
Based on source partitioning. Determines the number of partitions
using database partition information. The number of partitions is
-the maximum of the number of partitions at the source.
Based on number of CPUs. Sets the number of partitions equal to
the number of CPUs on the node that prepares the session. If the
session is configured to run on a grid, dynamic partitioning sets
the number of partitions equal to the number of CPUs on the node
that prepares the session multiplied by the number of nodes in the
-grid.
Default is disabled.
Number of Determines the number of partitions that the Integration Service
Partitions creates when you configure dynamic partitioning based on the
number of partitions. Enter a value greater than 1 or use the
$DynamicPartitionCount session parameter.

Session on Grid Settings

When Session on Grid is enabled, the Integration Service distributes workflows

and session threads to the nodes in a grid to increase performance and
scalability.

Table 8-5 describes the Session on Grid setting on the Config Object tab:

Table 8-5. Config Object Tab - Session on Grid

Session on Grid Setting Description
Is Enabled Specifies whether the session runs on a grid.
Working with a Session Configuration Object

Create a session configuration object when you want to reuse a set of Config
Object tab settings. After you create a session configuration object, you can
configure sessions to use it.

To create a session configuration object:

In the Workflow Manager, open a folder and click Tasks > Session
1.Configuration.
The Session Configuration Browser appears.
2.Click New to create a new session configuration object.
3.Enter a name for the session configuration object.
4.On the Properties tab, configure the settings.
5.Click OK.

To use a session configuration object in a session:

In the Workflow Manager, open the session properties and click the Config
1.Object tab.
2.Click the Open button in the Config Name field.
A list of session configuration objects appears.
3.Select the configuration object you want to use and click OK.
The settings associated with the configuration object appear on the Config Object tab.
4.Click OK.