All Forums Tools
mjlocat 2 posts Joined 03/15
20 Apr 2016
Different behavior in reserved words between TPT and

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 (in my dev environment), this works fine. When using version (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:

STEP Load_Trans_Table
, COL2
, COL3
, "DATE"
, "TIME"
, COL6
, COL7
, COL8
, COL9
, :COL2
, :COL3
, :"DATE"
, :"TIME"
, :COL6
, :COL7
, :COL8
, :COL9

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 or to change the column names. Target database is version

You must sign in to leave a comment.