Archives of the TeradataForum

Message Posted: Mon, 28 Apr 2003 @ 16:32:53 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Srini,

When data is fastexported without the use of 'INDICATORS' it results in null values being amended to the data type defaults in the fastexport dataset.

   eg. CHARACTER    null -> blank
       DATE         null -> zero
       INTEGER      null -> zero
       SMALLINT     null -> zero
       DECIMAL      null -> zero

The use of indicators should ensure that all null values remain as nulls. Indicator Mode is, to the best of my knowledge, the default mode, so perhaps check this is not turned off in your case ...

If reloading the exported data back into Teradata, fast/multiload uses the indicator array to assign the null values to the appropriate columns.

Therefore, make sure you add 'indicators' to the syntax of your script.

E.g.:

 BEGIN LOADING
     DDEWD02P.CUSTOMER_ACCOUNT
     ERRORFILES
         DDEWU01P.CUSTOMER_ACCOUNT_ET,
         DDEWU01P.CUSTOMER_ACCOUNT_UV
         CHECKPOINT 50000
         INDICATORS;                 /* add to fastload script */

Note also, the fastexported output dataset will be increased in size by the addition of the indicator array to the front of the data parcel and the LRECL may need to be amended accordingly.

The size of the indicator array is determined by the number of columns to be exported as each byte can represent up to 8 columns. Eg. to export 21 columns, fastexport uses 21 indicator bits so the indicator array will increase the record length by 3 bytes. [i.e. Allow 1 extra byte for every 8 columns on table]. To cater for this, you may need to add a new Filler to the end of the 'Define' step.

Julie.

	<Prev	Next>		<<First	<Prev	Next>	Last>>