Introduction to DAC and Informatica Interaction

Introduction to DAC and Informatica Interaction

DAC orchestrates ETL routines written in Informatica and uses the Informatica pmcmd and pmrep command line interface tools to run workflows. At runtime, DAC consolidates all parameters—including runtime, database specific, SQL, and application level—into a parameter file while invoking the workflows. DAC also sets the session log file name, and, at the end of the routine execution, collects valid statistics, such as workflow status, number of row processed, and read/write throughputs.

DAC Session Log File Naming Conventions

DAC provides a log file name for each Informatica session it executes. If a workflow does not run concurrently, and, therefore, does not have multiple instances, DAC uses the following naming convention for the log file:

[session_name].[source_database_name].log

If a workflow runs concurrently because it is configured to loop , DAC uses the following naming convention for the log file

[dac_task_name].S[session_number].[source_database_name].log

If a workflow runs concurrently because a DAC_EP_PREFIX execution plan level parameter has been defined , DAC uses the following naming convention for the log file:

[prefix].[session_name].[source_database_name].log

The source database name is appended to allow for multi-source ETL processes in which the same task may be run as many times as there are sources, and the log files must be distinguishable.
DAC will shorten the name of the session log file if the naming convention produces files names greater than 100 characters.
If the length of the absolute file name (fully qualified with directory names) is more than 250 characters, Informatica may fail and return a "File name too long" error when it tries to create the workflow/session log files. To help avoid this error, Oracle recommends that the variables $PMSessLogDir and $PMWorkflowDir have values that are short, such as C:\infalogs, rather than the typical value C:\Informatica\PowerCenter<version number>\server\infa_shared\SessLogs.

However, even if you use short values for the variables $PMSessLogDir and $PMWorkflowDir, DAC may still shorten the length of the log file names. To enable DAC to use longer file names (over 100 characters, which is the default), edit the variable informatica.max.sesslogfile.length in the infa-config.properties file, which is located in the <DAC_Config_Location>\conf-shared directory.

Informatica Log File Naming Conventions

The naming conventions for Informatica log files is different depending on whether the DAC_EP_PREFIX execution plan level parameter has been defined. Table 3-1 lists the naming conventions for the Informatica log files.

Table 3-1 Informatica Log File Naming Conventions

Command That Generates Log	Log File Name Without DAC_EP_PREFIX Defined	Log File Name With DAC_EP_PREFIX Defined
Pmcmd: startworkflow getworkflowstatus	WF.log	<PREFIX>_WF.log
Pmcmd: getSessionDetails	WF_DETAIL.log	<PREFIX>_WF_DETAIL.log
Pmrep: getSessionSet	WF_SESSIONS.log	<PREFIX>_WF_SESSIONS.log

Connectivity Requirements

You should be familiar with the following connectivity requirements for DAC and Informatica.