This content has been marked as final. Show 1 reply
This error is a generic error that is a result of another, more specific error.
To determine the error do the following:
- If the session fails before initialization and no session log is created look for errors in workflow log, Integration Service log or other logs.
- If the session log is created and if the log contains errors such as "Caught a fatal signal/exception" or "Unexpected condition detected in file" then a core dump or Dr. Watson log has been created on the server machine. In this case get a stack trace and along with session log contact Informatica Technical Support.
- If you face this error for Windows 32-bit or 64-bit, and the session.log stops directly after starting the reader, compare the DDL of the sources with the DDL of the sources in the mapping. There might be a mismatch.
Bharath B S