QUERY
Select col1, col2..col18, Null as col9 from .... where.... in Oracle enterprise stage. and for the attribute 16--sql type is varchar and length is 150. when i run this the error i get is
"main_program: Fatal Error: Caught ORCHESTRATE exception in main program: APT_ParseError: In field "ATTRIBUTE16": Parsing parameters "max=0" for schema type "string": Max length must be positive, got: "0"
Expected ";", got: <eof>, line 20
Expected ";", got: <eof>, line 20
Error parsing schema: Expected ")", got: <eof>, line 20"
the attribute16 is 19th column
Why it is taking length as ZERO eventhough i assigned as 150. Please Explain.
Oracle Query error in Datastage
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 236
- Joined: Sun Apr 01, 2007 7:41 am
- Location: Michigan
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 236
- Joined: Sun Apr 01, 2007 7:41 am
- Location: Michigan
Oracle Query error in Datastage
I have tested the code in toad. its fine. But it is not working from datastage.ITs schema is
ATTRIBUTE16, VARCHAR, LENGTH=150, NUllABLE
its not a key column and there is nothing under scale
ATTRIBUTE16, VARCHAR, LENGTH=150, NUllABLE
its not a key column and there is nothing under scale
-
- Participant
- Posts: 342
- Joined: Tue Nov 04, 2008 10:38 am
- Location: Chennai, India
Re: Oracle Query error in Datastage
This "test" bothers me as it doesn't really mean anything other than to show that your SQL - whether it be select or update or whatever - is syntactically correct. Toad doesn't care what kind of fields you are returning the values into while DataStage does. Quite a bit.just4u_sharath wrote:I have tested the code in toad. its fine. But it is not working from datastage.
If this is coming from a schema file, post it. Sounds like it is not quite kosher.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers