Explanation: | A file name specified in the session properties is incorrect. The operating system error displays when the file does not exist. |
User Response: | In the Workflow Manager, correct the file name in the session properties. If you are loading a packaged resource in Metadata Manager, check the value of the PowerCenter Integration Service Process property $PMSourceFileDir. Metadata Manager stores transformed metadata for packaged resources in IME files in the $PMRootDir/SrcFiles directory. If the $PMSourceFileDir property is not set to $PMRootDir/SrcFiles, Metadata Manager cannot find the IME files. |
Explanation: | This is an operating system error. |
User Response: | An operating system error number appears with this message. If necessary, see the operating system documentation for appropriate action. |
Explanation: | The Integration Service failed to identify a field separator. You may have repository inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Data is larger than field length (delimited files only), forcing the Integration Service to truncate data. |
User Response: | To avoid truncating data, increase the field length accordingly. |
Explanation: | Insufficient buffer length. |
User Response: | In the session properties, increase the setting for Line Sequential Buffer Length. The record length may not be the size to which the Line Sequential Buffer Length should be increased. Check the source data file. |
Explanation: | You specified an incorrect FTP connection in a session. You might have used the wrong user name or password. Or the FTP server may be down. |
User Response: | Verify the correct FTP connection is specified in the session properties and manually test that FTP connection. |
Explanation: | You attempted to use FTP to transfer a file that does not exist. |
User Response: | Verify that the file exists and that you used the correct spelling. |
Explanation: | You do not have permission to access the remote file. |
User Response: | Contact the FTP system administrator. |
Explanation: | You specified the same quote mark for the escape character and the optional quotes character in a delimited flat file source. |
User Response: | Specify a different escape or quote character. |
Explanation: | One of the delimiters is the selected quote character. |
User Response: | Specify a delimiter other than the quote character. |
Explanation: | One of the delimiters is the specified escape character. |
User Response: | Specify a delimiter other than the escape character. |
Explanation: | You have not specified a delimiter. |
User Response: | Specify a delimiter. |
Explanation: | There is a missing closing quote in the specified column. |
User Response: | Review the file and add a closing quote character where appropriate. |
Explanation: | There are additional characters after the closing quote delimiter in the specified column. The Integration Service did not read the extra characters. |
User Response: | Look in the source file to verify if the skipped characters are intended to be a part of the column. If so, import the file into the Source Analyzer again. |
Explanation: | Internal error while reading from a source file. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | You configured the Integration Service to run in ASCII mode. The file source code page is Latin1, and you selected an escape character for the file source that is not valid in the Latin1 code page. |
User Response: | Select an escape character that is valid in the Latin1 code page. |
Explanation: | You configured the Integration Service to run in ASCII mode. The file source code page is Latin1, and you selected a delimiter for the file source that is not valid in the Latin1 code page. |
User Response: | Select a delimiter that is valid in the Latin1 code page. |
Explanation: | You configured the Integration Service to run in Unicode mode, and you selected an escape character for the file source that is not valid for the file source code page. |
User Response: | Select an escape character that is valid in the source code page. |
Explanation: | You configured the Integration Service to run in Unicode mode, and you selected a delimiter for the file source that is not valid for the file source code page. |
User Response: | Select a delimiter that is valid in the source code page. |
Explanation: | The code page you selected is not valid for delimited flat file formats. |
User Response: | Select a code page that is valid for delimited flat files. |
Explanation: | You configured the Integration Service to run in ASCII mode and selected an EBCDIC-based multibyte code page for a file source. |
User Response: | If data requires an EBCDIC-based multibyte code page, run the Integration Service in Unicode mode. Otherwise, select a valid code page for the source. |
Explanation: | The Integration Service could not find the code page you specified. |
User Response: | Install the correct code page. |
Explanation: | Multibyte data does not fit into the fixed-width boundary for this column. |
User Response: | Change the field width or pad the column with blanks so that fields fit correctly. |
Explanation: | The code page you selected is not valid for fixed-width files. |
User Response: | Select a code page that is valid for fixed-width files. |
Explanation: | The null character you specified is invalid in the source flat file code page. |
User Response: | Use a null character that is valid in the source flat file code page. |
Explanation: | You configured the Integration Service to run in ASCII mode and specified a null character that is not valid in the Latin1 code page. |
User Response: | Specify a null character that is valid in the Latin1 code page. |
Explanation: | The code page you selected is not valid for VSAM files. |
User Response: | Select a code page that is valid for VSAM files. |
Explanation: | You entered an invalid null character value. |
User Response: | Specify a null character value between 0 and 255. |
Explanation: | The number of bytes to skip between records is greater than 0. If the number of bytes to skip between records is greater than 0, then there is an alignment error in these bytes. The record data does not end at the fixed-width boundary for these skipped bytes. |
User Response: | Fix the data and the number of bytes to skip between rows/records setting. |
Explanation: | Remaining data in a non-repeating, binary null field does not end at the fixed-width boundary for that field. |
User Response: | Fix the data and/or the fixed-width settings. |
Explanation: | An error occurred reading the source file. |
User Response: | Check other error messages logged for more details. |
Explanation: | The non line-sequential data is too small. The data displayed is the row, including the trailing bytes between records. |
User Response: | Make sure the data is the correct length and the bytes between rows match the source file options. |
Explanation: | The reader cannot read the input field because the input field contains characters that are not in the Latin 1 code page. |
User Response: | Change the input field to contain Latin 1 character data. |
Explanation: | In a file source, at least one of the REDEFINES statements results in a character exceeding the field boundary. |
User Response: | Examine and correct the row where the error occurred. |
Explanation: | The definition is incorrect. |
User Response: | Edit the REDEFINES statement. |
Explanation: | In a file source, one of the REDEFINES statements leaves the row in the shift in state while another REDEFINES statement leaves the row in the shift out state. |
User Response: | Examine and correct the row where the error occurred or edit the REDEFINES statement. |
Explanation: | The Integration Service could not open the queue. |
User Response: | Check the additional error message for more information. |
Explanation: | The last row in the fixed-width file contains empty columns. The Integration Service skips the last row. |
User Response: | Verify the last row in the source file contains valid data. |
Explanation: | The source file contains string data in a numeric column. The Integration Service skips the row. |
User Response: | Verify the row in the source file contains valid data. |
Explanation: | The date format string for a datetime column contains a character that is not in 7-bit ASCII. |
User Response: | In the Designer, edit the flat file source definition using 7-bit ASCII characters for the datetime column format string. |
Explanation: | The source file contains invalid data in a datetime column. The Integration Service skips the row. |
User Response: | Verify the row in the source file contains valid data. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | In the Designer, you specified the same character as both the file delimiter and as the thousands separator for the specified numeric column. |
User Response: | Verify the source file contains different characters for the thousands separators and column delimiters. Edit the source definition in the Source Analyzer, or import it again. |
Explanation: | In the Designer, you specified the same character as both the file delimiter and as the decimal separator for the specified numeric column. |
User Response: | Verify the source file contains different characters for the decimal separator and column delimiter. Edit the source definition in the Source Analyzer, or import it again. |
Explanation: | The Integration Service cannot access the source file. |
User Response: | Verify the Integration Service can access the machine hosting the file. Grant read permission on the directory where the file is located to the Informatica Services account or the operating system user in the operating system profile. |
Explanation: | In the fixed-width file source, a multibyte character in a column spans over two columns. The Integration Service skips the row. |
User Response: | Verify that the row in the source file contains valid data. Also, verify that the data in the source file matches the source definition. |
Explanation: | You selected Indirect for the Source file type. When the mapping contains an associated source qualifier, the source file type must be direct. |
User Response: | Select Direct as the source file type. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | During a real-time session, the Integration Service issued a commit while processing a record. As a result, the session failed. |
User Response: | Make sure that all message fields in the change WebSphere MQ source are complete before running the session. |
Explanation: | The Integration Service cannot read the input field because it contains a null character. |
User Response: | Verify that the source does not have null values. |
Explanation: | The session failed because the line break character is the same character as the column delimiter in the flat file. |
User Response: | Configure different characters for the flat file line break character and column delimiter character. |
Explanation: | The session failed because the UTF-16BE or UTF-16LE code page is not supported for fixed-width flat files. |
User Response: | You can use these code pages with delimited flat files. |
Explanation: | The SFTP connection specified in the session has an error. Or, the SFTP server might be down. |
User Response: | Verify the correct SFTP connection is specified in the session properties and manually test the SFTP connection. Also, verify that the correct username and password was specified. |
Explanation: | The remote file does not exist. |
User Response: | Verify that the file exists and that the correct file name was specified in the SFTP connection. |
Explanation: | The SFTP user does not have permission to access the remote file. |
User Response: | Contact the SFTP system administrator. |
Explanation: | The FileRdrTruncateStringNull and FileRdrTreatNullCharAs custom properties are enabled at the same time. These custom properties determine how the Integration Service handles null characters in the flat file source. |
User Response: | Disable one of the properties. For more information about custom properties, contact Informatica Global Customer Support. |
Explanation: | When you enable the FileRdrTreatNullCharAs custom property, the Integration Service sets null characters in a source file to the character you define. The character format is invalid. |
User Response: | Define a valid octal character, such as \040. For more information about custom properties, contact Informatica Global Customer Support. |
Explanation: | When you enable the FileRdrTreatNullCharAs custom property, the Integration Service sets null characters in a source file to the character you define. The character specified is a multibyte character. |
User Response: | Define a valid single-byte character. For more information about custom properties, contact Informatica Global Customer Support. |