LGS Messages

Explanation:	The day limit or size limit for log event files was reached, and the Log Manager purged the log event files. However, the Log Manager did not delete the file because it was in use or recently modified.
User Response:	None. The Log Manager will delete the file during the next log purge if the file is not in use or recently modified.

LGS_10010 Not all files are deleted in directory: <directory name>.

Explanation:	The Log Manager attempted to purge the log event files in the directory. However, some of the log event files were recently modified or still in use by the Log Manager.
User Response:	None. The Log Manager will delete the file during the next log purge if the file is not in use or recently modified.

LGS_10013 Invalid number of log events were received.

Explanation:	The Log Manager attempted to retrieve log events, but the number of events is invalid. This error can occur when you use infacmd to retrieve log events, but you enter an invalid number of events. For example, you enter 0 for the number of log events to retrieve.
User Response:	Enter a valid number of log events to retrieve.

LGS_10016 Failed to close the file merge stream due to the following error <error text>.

Explanation:	The Log Manager could not close multiple file streams to the same log event file. This error can occur because the permissions for the log event file were modified after the Log Manager began writing or because the file was removed.
User Response:	Correct the error indicated in the message and make sure the user account that runs Informatica Services has read and write permission on the file.

LGS_10017 Error creating the directory <directory name>.

Explanation:	The Log Manager could not create the directory in the shared location for log event files. This error can occur because the Log Manager does not have sufficient access permissions on the shared directory location for the log event files.
User Response:	Make sure the user account that runs Informatica Services has read and write permission on the shared directory location.

LGS_10019 Failed to open the file stream <file name> due to the following error <error text>.

Explanation:	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.
User Response:	Correct the error indicated in the message and make sure the user account that runs Informatica Services has read and write permission on the file.

LGS_10021 Failed to read log event from the file stream <file name> due to the following error <error text>.

Explanation:	The Log Manager attempted to retrieve log events from the log event file. However, the log event file contains inconsistent data.
User Response:	Correct the error indicated in the message.

LGS_10024 Log request failed due to the following error <error text>.

Explanation:	The Log Manager attempted to retrieve log events from the shared directory location, but the retrieval failed due to an error.
User Response:	Correct the error indicated in the message and view logs events again.

LGS_10026 The log service configuration is missing the log service directory value for the node <node name>.

Explanation:	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.
User Response:	Configure a directory for the log event files.

LGS_10028 The index file <file name> is corrupt.

Explanation:	The Log Manager uses an index file in each log file directory for quick access to log event data files. The Log Manager was unable to read from or write to the index file. This error can occur when the permissions for an index file are modified or because the file was removed.
User Response:	Correct the error indicated in the message and view log events, export log events, or purge log events again. Make sure the user account that runs Informatica Services has read and write permission on the file.

LGS_10034 Log request failed due to the following error <error text>. Unable to rollback changes due to the following error <error text>.

Explanation:	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.
User Response:	Correct the errors indicated in the message and make sure the shared directory location is available.

LGS_10035 The timestamp index file <file name> is corrupted.

Explanation:	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.
User Response:	Contact Informatica Global Customer Support.

LGS_10052 The Log Manager has no record of the requested session or workflow run.

Explanation:	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.
User Response:	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.

LGS_10060 The log fetch operation does not accept both Run ID and Run instance name as inputs.

Explanation:	You specified both Run ID and Run instance name.
User Response:	Use the -RunInstance or -RunId option, but not both.

LGS_10006 The file <file name> was skipped during automatic purge.