Unwanted NULL Values Observed In Target Flat File When Loading Data From An Oracle Table To a Target Flat File Using ODI 11g OdiSqlUnload (Doc ID 1906450.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Data Integrator - Version 11.1.1.6.5 to 11.1.1.6.5 [Release 11gR1]
Information in this document applies to any platform.

When using the ODI version 11.1.1.6.5 tool called OdiSqlUnload tool to export data to a flat file and setting parameters for the:

using Unicode values retrieved using the ODI Substitution Methods:

"-XFILE_SEP=<%odiRef.getTargetTable("XFILE_SEP_FIELD")%>"
"-XROW_SEP=<%=odiRef.getTargetTable("XFILE_SEP_ROW")%>"

you observe that the flat file contains the following:

first row: '1(nul);(nul)'
second row: '(nul)'
third row: '2(nul);(nul)'
fourth row: '(nul)'

If however you use hardcoded hexadecimal notation:

"-XFILE_SEP=3B"
"-XROW_SEP=0D0A"

the file is formatted correctly:

first row: '1;'
second row: '2;'

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Symptoms

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.