DSXchange

Hi All i am running a parallel job on LINUX my input is sequential file iam getting this warnings

Sequential_File_266,0: Field "ACTIVITY_MAPPING_ID" has import error and no default value; data: {I D}, at offset: 0

Sequential_File_266,0: Import warning at record 0

Sequential_File_266,0: Import unsuccessful at record 0.

but there is no records rejected

thanx in avvance

Hi,

Check the data type for the field ACTIVITY_MAPPING_ID.
It is complaining that, the data 'ID' is not accepted for the given data type.
May be a Header line.

Does this field 'ACTIVITY_MAPPING_ID' have any NULL values?

sam

Import errors are row #0 are typically caused by neglecting to set the First Line is Column Names property to True.

The raw form of the "data" - here { I D } - helps to confirm that this is the case. Clearly "ID" can not be an integer.

check the data types

thanks for the reply , there are no null values for ket ACTIVITY_MAPPING_ID. My file structure is

ID|ACTIVITYID|MAPPEDACTIVITYID|MODIFIEDBY|LASTMODIFIEDAT
1651|15|-4101||
1652|15|-4007||
1653|15|-4001||
1654|15|-4110||
1077|402|-4107||
-14002|-4102|-4006||

for field ID i am giving name as ACTIVITY_MAPPING_ID since it is a key , data types are same as per source .first 3 are integer , modifiedby is varchar and lastmodifiedat is timestamp. If i change int to varchar for first 3 fields it is giving warning for Lastmodifiedat field.
Ray i am using first line is a column name still iam getting those warnings

thanks

Are you having any spaces or empty values in that field? What warning message are you getting after changing that field to varchar?

Sam

No spaces i am getting the same warning for next fields if i make it as varchar, i think it it taking the header as a records and rejecting it since ID cant be integer but i am using first line as a column name.

But are you setting the First Line is Column Names property (on the Stage tab Properties) to True? I suspect not, as noted earlier.

Problem solved , i redesigned the job again and reimported the metadata .

Thanks to all

What did you do differently?

Hi all,

We encountered the same problem recently after upgrading from v7.5A to 7.5.2 on AIX.

It seems that even if you have set the property "First Line is Column Names" to "True" you will receive a warning for the first line if you are using the file with a lookup stage and there is more that one lookup input. Splitting the lookup stage so you have one stage per input file will make the warning disappear...

It is probably a bug but it might help you save some time.

Mat