FATAL ERROR : Unexpected Condition in file [\ZeusbuilderProduction\view\powrmart\server\dmapper\widget\wjoiner.cpp]

"Unexpected Condition at at wjoiner.cpp: line 8772" when running a PowerCenter session with Joiner transformation

Problem Description

When running a PowerCenter session with the mapping that has a Joiner Transformation with sorted input using a Sorter transformation, the session fails with the following errors in the session log in different versions of PowerCenter: FATAL ERROR : Unexpected Condition in file [\ZeusbuilderProduction\view\powrmart\server\dmapper\widget\wjoiner.cpp] line [8772].Contact Informatica Technical Support for assistance.Aborting this DTM process due to an unexpected condition. PowerCenter 7.1.x: FATAL ERROR : Unexpected Condition in file [/home1/build71/pm711n/server/dmapper/widget/wjoiner.cpp] line [8449].Contact Informatica Technical Support for assistance.Aborting this DTM process due to an unexpected condition.

Cause

This is due to insufficient buffer memory being allocated to run the session.

Solution

To resolve this set the DTM buffer block size to AUTO. However, if you do not want to run the session with AUTO, then set the DTM buffer size and Buffer Block size to the value that is specified in the session when run in the AUTO mode. PowerCenter 7.1.x To resolve this in versions prior to 8.x increase the DTM buffer size.

Applies To

PowerCenter

More Information

Alternatively you can clear the Sorted Input option in the Joiner transformation to avoid this error.

Reference

"Allocating Buffer Memory" under "Optimizing Sessions" in the PowerCenter Performance Tuning Guide

"TM_6795 ERROR: Session or its instance is invalidated and the Integration Service is configured not to run impacted sessions."

"TM_6795 ERROR: Session or its instance is invalidated and the Integration Service is configured not to run impacted sessions."

Problem Description

A PowerCenter session fails to run and the following error is in the workflow log: INFO : LM_36488 : (655482|7711) Session task instance [s_session] : [TM_6721 Started [Fetch Session from Repository].] ERROR : LM_36488 : (655482|7711) Session task instance [s_session] : [TM_6795 ERROR: Session or its instance is invalidated and the Integration Service is configured not to run impacted sessions.] ERROR : LM_36320 : (655482|7197) Session task instance [s_m_DP_All_Functions_sybs]: Execution failed. INFO : LM_36318 : (655482|7197) Workflow [all_function_sybs]: Execution succeeded.

Cause

This error will occur when the session has been invalidated due to a dependent object being updated and the Run sessions impacted by dependency updates Integration Service property is set to 'No' (the default setting).

Solution

To run the session successfully do the following: Validate session in the Workflow Manager. Save the workflow. Run the workflow.

More Information

To run the session after updates without validating (not recommended) do the following: Login to the Informatica PowerCenter Administration Console. Select the Integration Service. Select the Properties tab. Expand the Advanced Properties Select Edit. Select Run sessions impacted by dependency updates. Click OK.

XML Reader error:Downcasting from UNICODE to ASCII'.

problem
sources are XML Files.When I run the
workflow some sessions are failing and the error mesg in log is
'XML Reader error:Downcasting from UNICODE to ASCII'.This happens
only with some XML files.

solved

Goto Informatica PowerCenter Administration Console (8.1) >> change ascii to unicode

You can configure general properties for the Integration Service. You can override some of these properties at the session level or workflow level. To override these properties, configure the properties for the session or workflow.

To edit the general properties, select the Integration Service in the Navigator, and then click the Properties tab > General Properties > Edit.

Solved

others fix the xml file :

Please find the below link to get the XML parser tool.

www.architag.com/xray/

you can use this tool to parse your xml.

you have to update your source xml code page to UNICODE.

error importing xml with xsd: xsd too big (more than 500MB)

Problem :
When creating an xml source using an xsd, I am getting an error
saying that the xsd used is too big. It lets me complete the
import but the source is not valid. When trying to validate, I
get the following error message: "ThisXML definition is too
large. The total length of all columns must not exceed 500
MB""The XML definition is not valid"

Solve
In source analyzr open the source in edit xml mode (in xml editor) then
goto TOOLS.....>OPTIONS....>Override all infinite lengths with value(tik
this option and set the value to 200 or less)

Invalid lookup override

Problem :
LOOKUP transformation : SQL Override
SELECT DISTINCT TIM_DT_ID FROM L_TIM_DT
WHERE TIM_DT_ID >= '2006-01-01'

Error :
Severity Timestamp Node Thread Message Code Message
WARNING 3/6/2008 18:12:23 node01_quadjt MAPPING DBG_21263 Invalid lookup override

Solved :
while overriding the lookup you must have to give the
alias name as exisiting port name,

SELECT DISTINCT L_TIM_DT.TIM_DT_ID as TIM_DT_ID FROM L_TIM_DT
WHERE L_TIM_DT.TIM_DT_ID >= '2006-01-01'