Troubleshooting Informatica Error Messages and Resolution – Part 193

SQLServerF1

LGS_10019Failed to open the file stream [<file name>] due to the following error [<error text>].
Cause:The Log Manager was unable to open the log event file for reading or writing. This error can occur when the permissions for a log event file or the log event directory are modified after the Log Manager begins reading or writing or because the file was removed.
Action:Same as LGS_10008.

LGS_10021Failed to read log event from the file stream [<file name>] due to the following error [<error text>].
Cause:The Log Manager attempted to retrieve log events from the log event file. However, the log event file contains inconsistent data.
Action:Correct the error indicated in the message.
LGS_10024Log request failed due to the following error [<error text>].
Cause:The Log Manager attempted to retrieve log events from the shared directory location, but the retrieval failed due to an error.
Action:Correct the error indicated in the message and view logs events again.
LGS_10026The log service configuration is missing the log service directory value for the node <node name>.
Cause:The Log Manager could not write to the shared directory path for the log event files because the directory location is missing in the domain configuration.
Action:Configure a directory for the log event files.

LGS_10028The index file [<file name>] is corrupt.
Same as LGS_10011.
LGS_10029Failed to flush the file stream [<file name>] due to the following error [<error text>].
Same as LGS_10008.
LGS_10034Log request failed due to the following error [<error text>]. Unable to rollback changes due to the following error [<error text>].
Cause:The Log Manager wrote to log event files. However, the process was interrupted due to an error, and the Log Manager could not roll back the changes it made to the log event file. This error can occur if the Log Manager
writes to a shared directory location that becomes unavailable during the write process.
Action:Correct the errors indicated in the message and make sure the shared directory location is available.
LGS_10035The timestamp index file [] is corrupted.
Cause:The Log Manager uses the timestamp index file to access the log event files in a directory. However, the timestamp index file contains inconsistent data and the Log Manager cannot access the log event files in the directory.
Action:None.
LGS_10036The index file in the directory [] appears corrupted.
Cause:The Log Manager uses an index file in each log file directory for quick access to log event data files. However, the index file contains inconsistent data and the Log Manager cannot access the log event files in the directory.
Action:None.
LGS_10052The Log Manager could not find the session or workflow run.
Cause:The Log Manager has no information about the session or workflow run. The name is invalid, the run is not the latest, or the database table was purged.
Action:If you are using infacmd, verify that the workflow or session name is valid. If you are trying to get the session or workflow log in the Workflow Monitor, select the latest session or workflow run.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *