I've got a TPT LOAD job that has reserved words as the names of two of the columns in the target table. Ignoring the fact that this is a bad idea (I don't have control over what a column is going to be named), I went ahead and put double quotes around those reserved words for every occurance in the TPT script. When using TPT from version 14.10.00.13 (in my dev environment), this works fine. When using version 14.00.00.03 (in my production environment), it failes in the aquisition phase
LOAD_OPERATOR: connecting sessions
LOAD_OPERATOR: preparing target table
LOAD_OPERATOR: entering Acquisition Phase
LOAD_OPERATOR: TPT10508: RDBMS error 3707: Syntax error, expected something like a name or a Unicode delimited identifier or an 'UDFCALLNAME' keyword between ',' and the 'DATE' keyword.
LOAD_OPERATOR: disconnecting sessions
From my TPT script, here's the load step:
('INSERT INTO <TARGET>(
TO OPERATOR (LOAD_OPERATOR)
My question is, why the different behavior between the two versions and what can be done to make them behave the same? The options I've come up with are to upgrade the production server to TPT 14.10.00.13 or to change the column names. Target database is version 15.00.04.07.