Thursday, 4 September 2008

sql loader and tab separated multibyte fields

when you use following part in your control file:
fields terminated by X'0009' optionally enclosed by X'0022'

you probably notice that the multi tab characters got swelled to one tab character, which causes that null value fields are gone, and the next non-null fields got shifted in that way, that there are no null values between 2 non-null value fields in db.

The solution to this issue is removing the "optionally enclosed ..." statement.

1 comment:

Bas de Ruiter said...