Blog Network Home > Informatica Way > Informatica Exceptions – 3

Informatica Exceptions – 3

by Rajamani Vasudevan on July 8, 2008 in Informatica Way

Here are few more Exceptions:

1. There are occasions where sessions fail with the following error in the Workflow Monitor:

“First error code [36401], message [ERROR: Session task instance [session XXXX]: Execution terminated unexpectedly.] “

where XXXX is the session name.

The server log/workflow log shows the following:

“LM_36401 Execution terminated unexpectedly.”

To determine the error do the following:

a. If the session fails before initialization and no session log is created look for errors in Workflow log and pmrepagent log files.

b. If the session log is created and if the log shows errors like

“Caught a fatal signal/exception” or

“Unexpected condition detected at file [xxx] line yy”

then a core dump has been created on the server machine. In this case Informatica Technical Support should be contacted with specific details. This error may also occur when the PowerCenter server log becomes too large and the server is no longer able to write to it. In this case a workflow and session log may not be completed. Deleting or renaming the PowerCenter Server log (pmserver.log) file will resolve the issue.

2. Given below is not an exception but a scenario which most of us would have come across.

Rounding problem occurs with columns in the source defined as Numeric with Precision and Scale or Lookups fail to match on the same columns. Floating point arithmetic is always prone to rounding errors (e.g. the number 1562.99 may be represented internally as 1562.988888889, very close but not exactly the same). This can also affect functions that work with scale such as the Round() function. To resolve this do the following:

a. Select the Enable high precision option for the session.

b. Define all numeric ports as Decimal datatype with the exact precision and scale desired. When high precision processing is enabled the PowerCenter Server support numeric values up to 28 digits. However, the tradeoff is a performance hit (actual performance really depends on how many decimal ports there are).

You might want to read these awesome related posts


{ 5 comments }

1 sangram takmoge October 1, 2008 at 7:11 am

I am facing ’session terminated unexpectedly’ error.
Session can generate log but does not have any of the two errors mentioned above. I guess this error is a problem with the source connection. The last entry in the log show that xxxx is the source etc. but nothing is shown after this in the log.

2 sangram takmoge October 1, 2008 at 7:15 am

I found following link. Hope this will work for some of you. In my case I don’t have access to run the scripts here against the repository tables.

http://hasimma.blogspot.com/2006/07/informatica-71informatica-session.html

3 Poobalan June 9, 2009 at 9:50 am

To add a point here related to Error code : 36401 and the possible resolution (if applicable).

1) There is a date column in Normalizer transformation with data type ‘NString’ and mapped to String column in the next transformation(filter), causes the 36401 error.

Fix : The data type in filter transformation has been changed to ‘Date/Time’ datatype and got fixed the error.

4 MANISH October 17, 2010 at 11:36 pm

This is not a connection related, its related to datatype, i am half-way thro its resolution

5 karan January 28, 2011 at 12:42 pm

Hi i am having a query while i am running a session around 800 records are getting rounded up out of 40000 records the precision of the table is 34 after 16th char it is getting rounded up…i had enabled high precesion in session properties

Comments on this entry are closed.