Insert_Rejects: When checking operator: When validating export schema: At field "DT_ADDED": "null_field" length (1) must match field's fixed width (19)
I cannot see a direct way to change the null_field length for individual fields on reject links (you can set it at the file level but not for individual fields). One way around this is to change these fields to be varchar but the extra level of complexity is that the initial information is coming from a nullable date field in an Oracle table so that I have to import it as a timestamp (which then seems to insist on exporting as a char(19)).
Insert_Rejects: When checking operator: When validating export schema: At field "DT_ADDED": "null_field" length (1) must match field's fixed width (19)
If it is a database field - Make it Varchar (or something equivalent to this).
If it is a flat file, use the function Space(19).
-T.J.
Developer of DataStage Parallel Engine (Orchestrate).
If this is a sequential file just change the metadata type to varchar instead of timestamp. Actually you shouldn't bet getting this error since null dates are valid.
adscot wrote:The problem is that you can't set field level attributes on a reject file.
I was referring to doing this BEFORE the flat file output in a Transform Stage. This way, your records will NOT be rejected for that particular reason.
-T.J.
Developer of DataStage Parallel Engine (Orchestrate).
adscot wrote:The problem is that you can't set field level attributes on a reject file.
I was referring to doing this BEFORE the flat file output in a Transform Stage. This way, your records will NOT be rejected for that particular reason.
-T.J.
Ah ha I understand - sorry me being a bit slow. I can put a transform on the reject link prior to the output to resolve the output issues
