The parameter marker the ODBC stage uses in not numbered - Oracle, yes but not ODBC. It uses a simple question mark, so you would need to change all references to colon-anything to '?' - and then ensure they are listed in the same order as your columns are defined in the stage.ILLEGAL SYMBOL 1; VALID SYMBOLS ARE <IDENTIFIER>
Moderators: chulett, rschirm, roy
Strange. The parameter marker the ODBC stage uses in not numbered - Oracle, yes but not ODBC. It uses a simple question mark, so you would need to change all references to colon-anything to '?' - and then ensure they are listed in the same order as your columns are defined in the stage.
The parameter marker the ODBC stage uses in not numbered - Oracle, yes but not ODBC. It uses a simple question mark, so you would need to change all references to colon-anything to '?' - and then ensure they are listed in the same order as your columns are defined in the stage.-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The Dynamic Relational Stage always displays SQL with Oracle (positional) parameter markers, even though it uses the correct ones "under the covers".
However, the poster specifies that an ODBC stage has been used. The SQL was passed through to DB2 (the message came back from the database, not from the driver), so it contained only valid parameter markers.
Your diagnosis, therefore, is not correct. DB2 is complaining about some other 1 in the SQL. Have you, for example, used 1 in a WHERE clause when the data type is Char or VarChar, and you should have used '1'?
However, the poster specifies that an ODBC stage has been used. The SQL was passed through to DB2 (the message came back from the database, not from the driver), so it contained only valid parameter markers.
Your diagnosis, therefore, is not correct. DB2 is complaining about some other 1 in the SQL. Have you, for example, used 1 in a WHERE clause when the data type is Char or VarChar, and you should have used '1'?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.