Mittwoch, 16. Dezember 2015

PowerCenter crashes sorted input aggregator mappings

Problem

TM_6281 ERROR: Partitioning option license required to run sessions with user-defined partition points.
This error occurs even though the session is not defined with partitioning.

Workaround solution (it seems there is a bug opened with Informatica)

Set custom properties AggSupprtWithNoPartLic = Yes

Description of the problem: https://mysupport.informatica.com/infakb/solution/4/Pages/15636.aspx
Instructions: https://mysupport.informatica.com/infakb/howto/1/Pages/17598.aspx
More detailed instructions: https://mysupport.informatica.com/infakb/howto/1/Pages/18015.aspx

See also post Load csv file with linebreaks within fields

Make process structure independent from workflow parameter file

If you use workflows that are the exactly same apart from the location of their parameter files, it seems advisable to make a 1:1 layer of a worklet between the workflow and the actual structure.

workflow A -- worklet A --- session 1
                         |- worklet 1 ...
                         |- worklet 2 ...
                         |- command 1 
                         ...

In that way you can put the worklet A and its child objects to a template folder from where you roll out to other folders. In case of a structural change the workflow does not get affected. Otherwise you would have to adapt the parameter file path after a workflow roll out.

Load csv file with linebreaks within fields

Problem

PowerCenter ignores by default that a linebreak might be enclosed in quotes such that it will consider a record with linebreaks in fileds as several records. The field port relation suffers a shift such that wrong content ends in ports.

Workaround solution

https://community.informatica.com/thread/28705 provides a solution by creating a custom property in the integration service admin console with name = MatchQuotesPastEndOfLine and value = Yes (path displayed by in attached screen shot).

One can work around this by creating a session custom property (see the other attached screen shot), but this seems to be a rather frequent problem such that it be more robust if setup as IS custom property.

It seems sensible to provide the other shown session custom property also as IS custom property for the same reason.