I am using ODI Build ODI_12.1.3.0.0ODIBP_GENERIC_150402.2220.The MS SQL Server source table is using a column name Comment. I have changed the datastore to [COMMENT], but when I map the field to my Oracle datastore with column name COMMENT_, it gives an error on the MS side. When I drag and drop the column from the source to the destination table in the mapping, it sets the destination expression to PWO."[Comment]". This nomenclature is wrong for MS because with the double quotes that ODI is adding, MS thinks there are brackets in the column name and there aren't. If I manually modify the expression, to remove the double quotes, it unbinds the object and removes the Technical Description and Parsed Text in the logical side ([PWO (PWO)].[Comment] and @{R0} respectively). Once unbound, ODI skips this column when creating the temporary staging table, but then tries to reference the column it never created when copying the data from the staging table to the final destination table.
Does ODI have a bug when dealing with reserved word column names or is there another alternative?