GitHubContribute in GitHub: Edit online

Explanation of Informatica PowerCenter Connector Log Errors

Problem

We have found some errors in log files when analyzing Informatica PowerCenter workflows with Manta. Could you provide detailed information as to what these errors mean?

Solution

The table below describes the error messages you can find in Manta connector log files (e.g., ifpcDataflowMasterScenario_INFA_REP.properties.log, etc.).

Log message Probable cause Consequences
Source filename is empty in session extension... The source filename is not defined in the session, or it is defined by a parameter that is not found in the parameter file. The session is not analyzed.
Connection name or variable is undefined in source/target definition... The connection name or variable is not defined in the source/target definition, or it is defined by a parameter that is not found in the parameter file. The session is not analyzed.
Unable to find parameter file at path... The parameter file defined in the session or workflow is not found at the specified path. It is necessary to check if the parameter file exists in the path specified by the workflow or in the path specified in the Informatica PowerCenter connection properties in the property ifpc.parameter.files.dirs. The session or workflow is not analyzed.
Source has no workflow There is no workflow definition in the source file. It is possible that there is only a mapping in the XML file or the XML file is not valid. The source file is not analyzed.

There is no mapping for the connection string...

Cannot find any matching system for Connection...

There is an SQL override in a transformation with a connection to a database whose database dictionary has not been extracted, or the connection settings are not sufficient.

Verify the connection details and have Manta scan this database or map the existing database to this connection via *DictionaryMantaMappingManual.csv by copying the respective connection information from *DictionaryMantaMapping.csv and inserting the connectionString or serverName from this error message into the Connection ID column.

The SQL override is ignored.

Failed to parse input at position 3,15—the statement will be ignored

Lexer error: mismatched character ”=” expecting ”!”

A specific error when caused by Teradata SQL override (detected by parser) eu.profinit.manta.connector.teradata13.parser.TD13Lexer:

A legacy != and ~= syntax for the Teradata non-equal operator that only works over an ODBC connection (see the user manual about Teradata ODBC: https://docs.teradata.com/r/Enterprise_IntelliFlex_Lake_VMware/ODBC-Driver-for-Teradata-User-Guide-17.20/Deprecated-SQL-Transformations/Teradata-ODBC-Specific-Comparison-Operators-deprecated-in-14.10). This ODBC-specific syntax was deprecated in Teradata 14.10 and will completely cease to work in Teradata 16.00.

Replace the non-standard operators != and ~= in Teradata scripts and queries with the standard <> operator.

 The SQL override is ignored.
Connection variable ”...” is not blank and the resolved value is the same in the transformation...

An attempt to resolve a placeholder where an Informatica variable or parameter is expected, which has resulted in an unchanged value. This may be caused by one of the following.

  1. No parameter or variable was passed in, and therefore, the resolved value is unchanged;
    for example, when a connection variable is expected but the actual connection name is passed "Relational:NZEDW_ODBC".
  2. A parameter or variable was passed in, but it could not be resolved. Manta keeps the placeholder intact in such cases; for example, if the parameter $FileName is not defined, the resolved value will remain $FileName.
Cannot find the table in the lookup procedure...

This can be caused by one of two issues.

  1. A consequence of previous errors — Please review those to identify the root cause; for example, the parsing of SQL override for the lookup failed; or the database connection is ODBC or JDBC without proper alias mapping (check for prior “Cannot find any matching system for Connection” and “There is no mapping for the connection string” errors). Manta then attempts to use the lookup table name which is often empty when SQL override is used.
  2. An incorrectly configured lookup table — This is less likely when the workflow is being used and running in production.
The session or workflow is not analyzed.