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).
.jpg "Oracle Applications")
