Tuesday, March 11, 2008

"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:

  1. Validate session in the Workflow Manager.

  2. Save the workflow.

  3. Run the workflow.


More Information
To run the session after updates without validating (not recommended) do the following:

  1. Login to the Informatica PowerCenter Administration Console.

  2. Select the Integration Service.

  3. Select the Properties tab.

  4. Expand the Advanced Properties

  5. Select Edit.

  6. Select Run sessions impacted by dependency updates.

  7. Click OK.

at

2 comments:

Unknown said...

When I modify the SQL in a Source Qualifier, what steps are necessary to get the workflow to run? I validate the mapping, save in Designer, open Workflow Manager, open a workflow, validate the task, but when I save it says there are no changes. When I run it gives this error. Am I missing a step?

June 25, 2010 at 9:59 PM
Bikbar said...

I faced the same error. Reason was one of the underlying mapping was NOT checked-in.
Ensure that all your underlying objects are checked-in

May 24, 2011 at 2:16 PM

Post a Comment

Subscribe to: Post Comments (Atom)