Server job - ORA-01036: illegal variable name/number
Moderators: chulett, rschirm, roy
As already noted, it's all about the number of columns defined in the stage versus selected in your DML and what you've marked as keys. For yours to work, there must be three columns defined in the stage (in the order mentioned in the sql, of course) with none of them marked as a Key. Key fields must be bound into the where clause and would only be appropriate for a reference lookup where I'm assuming this is a source query.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The column and table names mentioned in the SQL must exactly match those in the Oracle schema. I've seen this error occur when the wrong schema was specified. You might also verify that the data types specified in your DataStage job are appropriate for the values being selected.
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.