9 Replies Latest reply on Jul 22, 2020 3:12 AM by Nico Heinze

    Line Sequential Buffer length

    Cyber King Seasoned Veteran

      Hi guys,

      Any one know what will be the main reason for line Sequential Buffer Length Error?

       

      When i tried with Maximum length of each column i found this error.. but i didnt crossed the maximum length of the column on DB level as well....

       

      Please share your exact Reasons

        • 1. Re: Line Sequential Buffer length
          Namratha Dhoolipalla Seasoned Veteran

          Hi,

           

          Can you please provide the complete error message that you are receiving? If this error is occurring during mapping execution, can you provide the input which is causing this error?

           

          Thanks,

          Namratha

          • 2. Re: Line Sequential Buffer length
            Cyber King Seasoned Veteran

            Row [1813]: Record length [317070] is longer than line sequential buffer length [2830] for

            /home/path/file.dat

            But I using maximum of 4000 charcters for 3 columns... I have used UTF-8.... And thr is problem of my Input?

            • 3. Re: Line Sequential Buffer length
              Akshada Sable Seasoned Veteran

              Hi Cyber King,

               

              Line sequential buffer length(RSBL) specifies the accepted length of bytes from an individual record of a flat file source.

              From the provided error message, I understand the length is set to 2830 but the record length is 317070, which is more than the RSBL.

               

              To accommodate the records of variable length, it is recommended to set the RSBL value to a higher value considering worst case scenarios.

              Refer https://docs.informatica.com/data-integration/data-services/10-0/performance-tuning-guide/source-optimization/flat-file-source-optimization.html for more details on this.

               

               

              Kind Regards,

              Akshada

              • 4. Re: Line Sequential Buffer length
                Cyber King Seasoned Veteran

                Actually , i have two mappings old one automatically taking Line Sequential Buffer length automatically, We have defined like default value to 1024. But why particularly this mapping creating issue... could you please tell us why we need to change manually?

                • 5. Re: Line Sequential Buffer length
                  Akshada Sable Seasoned Veteran

                  Hi Cyber King,

                   

                  The buffer length depends on the input record, for the mapping runs that we are comparing here, are you using the same data? Is the issue seen for the same set of data?

                   

                  You can verify the Line Sequential Buffer Length value for both the files by checking the advanced File properties:

                  • Flat file data object -> Advanced tab -> Run-time:Read -> Line Sequential Buffer length

                  Review if both the mappings are running with same configurations. If yes, use the same data set against both the mappings and let me know the results.

                   

                  The error/concern in question here is due to length of a specific input record.

                   

                  Kind Regards,

                  Akshada

                  • 6. Re: Line Sequential Buffer length
                    Cyber King Seasoned Veteran

                    Hi , I have checked the Flatfile , actually its counting length of Pipe symbol as well, its like a bug from informatica...??

                    • 7. Re: Line Sequential Buffer length
                      Syed Muzamil Guru

                      Hi,

                       

                      Please verify if the flat file configuration (delimiter settings) is identical in both the mappings. If the Pipe symbol is being read part of data, then this would be not a delimiter.

                       

                      As Akshada suggested please revisit the flat file configuration and verify the Line Sequential Buffer Length value and delimiter settings for both the files by checking the advanced File properties:

                       

                       

                       

                      Thanks,

                      Syed

                      • 8. Re: Line Sequential Buffer length
                        Cyber King Seasoned Veteran

                        First mapping using Delimiter comma(,) and second mapping using Delimiter Pipe symbol... I have checked all properties correctly... And also verified that rejected row length on notepad ++ and its calculated with pipe symbol...informatica considered that Pipe symbol count as well... But it should not count that pipe symbol... Though we declared delimiter pipe on flatfile properties... could you please suggest how to handle in this situation...

                         

                        Line Sequential Buffer is default 1024 ... I should not touch that... But it should work na?

                        • 9. Re: Line Sequential Buffer length
                          Nico Heinze Guru

                          There's one mean little catch with the delimiter character(s) in flat file definitions:

                          Whenever a session is created based on a mapping with a flat file source (or target, for that matter), the delimiter character for that particular flat file source is taken from the actual Source Definition.

                          Now if you ever change the delimiter definition in the flat file Source Definition, this change will NOT be taken over to any existing session. Here the delimiter character remains as it's set in the session.

                          So, whenever you change a flat file Source Definition AND there are sessions which use this flat file source definition, you have to edit all sessions using this Source Definition to change the delimiter character in the properties of the session.

                           

                          Unfortunately you haven't mentioned whether this is the case here. So that's why I'm asking if this is the case here. If so, you have to edit the second session, edit the source file properties, and change the delimiter character here. To me it looks as if the comma is still the delimiter character for your second session, and this behaviour might be an explanation for this issue.

                           

                          Regards,

                          Nico