At 09:15 AM 9/12/01 -0700, you wrote:
>Hi.
>
>I am trying to load data from MS-SQL to UDB. I have
>created the similar table present on MS-SQL in UDB
>and I did a BCP from MS-SQL .
>
>While loading I am getting errors as its not taking
>space for some of the columns. The error is
>
>SQL3116W The field value in row "F0-1" and column "4"
>is missing, but the target column is not nullable.
>
>The columns have been declared as XXX CHARACTER(5)
>NOT NULL in both MS-SQL and UDB and is having spaces
>now in MS-SQL table. I checked the BCP file and
>confirmed that spaces are there for the 4th column and
>it is not null.
>
>The load statement I am using is
>
>load from xxx.out of del modified by coldel{
>timstampformat="yyyy/mm/dd hh:mm:ss:uuuuuu" messages
>xxx.msg replace into instance-name.xxx
>
>Can some time tell me if there is a way to load data
>from MS-SQL to UDB having some columns in the input
>file for load with spaces??
>
>Thanks.
You did not specify the character delimiter, which
therefore defaults to a double quote character (").
If you are loading a character field that consists
entirely of blanks, and you don't specify a character
delimiter on the field in the input file, it will be
considered a NULL value, and if the field in the table
is defined as "not null", the record won't load. (If
the field in the table is defined as nullable, a NULL
value will be used.)
The character delimiter is optional on fields, except
to force a value of blanks or when you want to do
something like include delimiter characters in the
value of the character field.
To get your blank values accepted, you need to put
double quotes around that input column (or specify a
different character delimiter with the "chardel" option
and put that character around the input column).
-- Eldon Tucker
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
