SAP Knowledge Base Article - Preview

3214364 - TEMP_EXTRACT_COLUMN_DELIMITER doesn't always pad blanks on single char as before - SAP IQ


TEMP_EXTRACT_COLUMN_DELIMITER doesn't always pad blanks on single char as before. The behavior on IQ 16.x is different from IQ 15.4.


1) Sybase IQ/ 7/Enterprise Linux64 - x86_64 - 2.6.18-194.el5/64bit/2015-11-21 10:25:22 (correct behavior: J is padded correctly as written on manual)

cat Extract_ASCII_fijo_iq15
P 12345678901
NULL 12345678901

2) SAP IQ/ - x86_64 - 3.10.0-327/64bit/2022-02-01 00:55:58 (different behavior: J is not padded with <3> blanks)

cat Extract_ASCII_fijo_iq16
P 12345678901
NULL 12345678901


But manual states:


Use TEMP_EXTRACT_COLUMN_DELIMITER to specify the delimiter between columns in the output of the data extraction facility. In the case of an ASCII extraction, the default is to separate column values with commas. Strings are unquoted by default.

The delimiter must occupy 1 – 4 bytes, and must be valid in the collation order you are using, if you are using a multibyte collation order. Choose a delimiter that does not occur in any of the data output strings themselves.

If you set this option to the empty string '' for ASCII extractions, the extracted data is written in fixed-width ASCII with no column delimiter. Numeric and binary data types are right-justified on a field of <n> blanks, where <n> is the maximum number of bytes needed for any value of that type. Character data types are left-justified on a field of <n> blanks.

Notes: The minimum column width in a fixed-width ASCII extraction is 4 bytes to allow the string ?NULL? for a NULL value. For example, if the extracted column is CHAR(2) and TEMP_EXTRACT_COLUMN_DELIMITER is set to the empty string '', there are two spaces after the extracted data.




  • SAP IQ 16.0 and higher
  • SAP IQ 15.4 ESD#7


SAP IQ 16.0 ; SAP IQ 16.1


TEMP_EXTRACT_COLUMN_DELIMITER doesn't does not  pad blanks  single char behavior 826722 CR 826722 CR 826722 CR# 826722 , KBA , BC-SYB-IQ , Sybase IQ , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.