DSXchange

Both are 4 node .apt files. Both will cause your job to run on 4 nodes. Both have all four nodes on the same SMP machine ETL01. The differences I see are that the first appears to have four resource subdirectories for use by each node. If N1-N4 represent separate disks then each node will first use ...

1. Open Director and go to log of the job.
2. Select the log entry
3. Menu Tools =>Message Handler => Create new (I think)
4. demote to informational
5. save and exit.

Or
apply the IBM patch

Let's not call it a failure, let's call it a lovable eccentricity.
You are probably not doing anything wrong. It should be possible to control the partitiioning method of the transformer stage to something other then auto without throwing a warning.

There is a patch for AIX. Make IBM cough it up. I can't find the e-case number though.

Since this change is occurs within the job design the linkage to the table definition is broken. Why is adding another column to the lookup breaking the table definition linkage? Can you explain? Is the new column from the same table definition? Was it loaded from that table definition or hand-typed?

Search the forum for;
APT_IMPEXP_ALLOW_ZERO_LENGTH_FIXED_NULL

Set this to true and it should allow a zero length ('') for the NULL value in the decimal fixed width field upon export.

Try a Union

select
max(#TDREJDATECOL#)
from
#TDDBASE#.#TDREJTAB#
UNION
SELECT CAST('9999-12-31' AS DATE FORMAT 'YYYY-MM-DD')
;

core dump... orchadmin describe -s todd.ds ##I TFCN 000001 12:44:37(000) <main_program> Ascential DataStage(tm) Enterprise Edition 7.5.2 Copyright (c) 2004, 1997-2004 Ascential Software Corporation. All Rights Reserved ##I TUTL 000031 12:44:37(001) <main_program> The open files limit is 2000; raisin...

yes

Doing a orchadmin ll <dataset> core dumps when done from the command line and returns Unknown error reading record schema when done from Manager 1. An orchadmin check returns a successful check of the config file in $APT_CONFIG_FILE 2. An orchadmin cp also appears successful. so I believe the enviro...

There is no help for it that I am aware of. You'll have to use a MsgHandler or run the SQL beforehand to see if there are rows to load in some kind of overly complicated Sequence. We use a MsgHandler and demote the warning to Informational so that the wrapper shell script doesn't return a failure. I...

I would say that almost EVERYONE who has ever done EE is familiar with this particular message. You cannot export a field defined as nullable into a sequential file without handling the possibility of a NULL. There is no such thing as a NULL in a flat file. Searching the forum would have helped you ...

I was going by the Teradata pdf documentation for V2R6.0
-- 1143.pdf pg. 73.

n the precision. The range is from 1 through 18

Was it added for the .2 release of V2R6?

DECIMAL 18 is the largest decimal precision possible in Teradata. It is a Teradata limitation.

I answer these why questions from my three old Daughter all the time.
Why parameters? Because of purple.

Please mark this resolved.