did not have a compatible data type

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
syang@collaborative.com
Premium Member
Premium Member
Posts: 33
Joined: Tue Sep 02, 2014 7:43 am

did not have a compatible data type

Post by syang@collaborative.com »

I created a job that runs a query from Netezza and load data from one table and inserts it into another table. The job will abort if I don't change the "Type mismatch action" to "Keep" in the source Netezza DB stage. All the data type is correct but I keep getting the "did not have a compatible data type" warning.

Here is the warning:

NZ_SRC_FACT_FILLRATE_TRANSACTIONS: The following output link column(s): HEAD_DISCOUNT, QTY_INVOICED, PRICE, STD_COST were found in the result set of the query SELECT
SOURCE_SYSTEM_CODE,
ORDER_LINE_ID,
ORDERID,
LINE,
INVOICE_NUMBER,
MAX(INVOICE_DATE) AS INVOICE_DATE,
MIN(ORDER_DATE) AS ORDER_DATE,
SOLD_TO_CUSTOMER_ID,
ORDER_SITE,
AVG(HEAD_DISCOUNT) AS HEAD_DISCOUNT,
MAX(DUE_DATE) AS DUE_DATE,
MIN(DNSB_DATE) AS DNSB_DATE,
ITEM,
MAX(QTY_ORDERED) AS QTY_ORDERED,
MAX(QTY_SHIPPED) AS QTY_SHIPPED,
MAX(QTY_ALLOCATED) AS QTY_ALLOCATED,
SUM(QTY_INVOICED) AS QTY_INVOICED,
SALESPERSON,
MIN(SHIP_SITE) AS SHIP_SITE,
AVG(PRICE)AS PRICE,
AVG(STD_COST) STD_COST,
MIN(UM) AS UM,
MIN(UM_CONV) AS UM_CONV,
MIN(FILLKILL) AS FILLKILL
FROM dbo.fact_fillRate_transactions
WHERE (SHIP_TYPE <> N'm')
AND (FREIGHT_TERMS <> N'PU')
GROUP BY
ORDER_LINE_ID,
ORDERID,
LINE,
SOURCE_SYSTEM_CODE,
SOLD_TO_CUSTOMER_ID,
ORDER_SITE,
ITEM,
SALESPERSON,
INVOICE_NUMBER, but did not have a compatible data type. These columns will be dropped from the output link schema
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Do you have a question, or are you simply advising that this behaviour can occur?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
syang@collaborative.com
Premium Member
Premium Member
Posts: 33
Joined: Tue Sep 02, 2014 7:43 am

Post by syang@collaborative.com »

Sorry, I was wondering what causes this. And if there is a fix. Thanks.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

OK... let's start with the columns it called out: HEAD_DISCOUNT, QTY_INVOICED, PRICE, STD_COST. How are they defined in the job and in the actual source? Is there anything different about those three fields than any of the others in that regard?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply