Data Type Varchar 1500
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am
Data Type Varchar 1500
Hi All,
i am having some problem with the column while loading data into data base using data stage.The column length on oracle data base was varchar(1500 char) and it cannot be changed.
but in data stage varchar of length greater than 500 is not supported. while running the server job i am getting this warning "Invalid precision value. Error in parameter 62." and the is not loading into this column.
Please tell me how can i solve this problem in data stage.
Waiting for your respnses.
i am having some problem with the column while loading data into data base using data stage.The column length on oracle data base was varchar(1500 char) and it cannot be changed.
but in data stage varchar of length greater than 500 is not supported. while running the server job i am getting this warning "Invalid precision value. Error in parameter 62." and the is not loading into this column.
Please tell me how can i solve this problem in data stage.
Waiting for your respnses.
Re: Data Type Varchar 1500
Of course you can handle large string values in DataStage, I've loaded 4K - and upwards of 16K for LongVarChars.yalamanchili wrote:but in data stage varchar of length greater than 500 is not supported. while running the server job i am getting this warning "Invalid precision value. Error in parameter 62." and the is not loading into this column.
![Confused :?](./images/smilies/icon_confused.gif)
What stage are you using to write to Oracle? How is the target field defined in your table - VARCHAR2(1500) or did you really mean VARCHAR(1500)? The fact that the word 'precision' appears in your error message implies to me that you are writing to a numeric field of some type, perhaps accidentally... are you using [drumroll] User Defined SQL?
![Shocked :shock:](./images/smilies/icon_eek.gif)
If so, ensure all your columns and parameter markers are properly aligned so all fields are actually ending up in the right place in your table. Or let the stage generate the SQL.
-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:
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am
Re: Data Type Varchar 1500
Hi chulett,
Let me explain my problem clearly to you. In the oracle data base the column was declared as"VARCHAR2(1500 CHAR)," I am using ODBC Stage for connecting to the oracle data base. while importing definations for that column i have given it as varchar(1500). While executing the server jobs i am getting the warning Invalid Precision Value and the values are not inserted into the column.
Plese let me know if anything extra information is required.
Waitng for response.
Let me explain my problem clearly to you. In the oracle data base the column was declared as"VARCHAR2(1500 CHAR)," I am using ODBC Stage for connecting to the oracle data base. while importing definations for that column i have given it as varchar(1500). While executing the server jobs i am getting the warning Invalid Precision Value and the values are not inserted into the column.
Plese let me know if anything extra information is required.
Waitng for response.
chulett wrote:Of course you can handle large string values in DataStage, I've loaded 4K - and upwards of 16K for LongVarChars.yalamanchili wrote:but in data stage varchar of length greater than 500 is not supported. while running the server job i am getting this warning "Invalid precision value. Error in parameter 62." and the is not loading into this column.![]()
What stage are you using to write to Oracle? How is the target field defined in your table - VARCHAR2(1500) or did you really mean VARCHAR(1500)? The fact that the word 'precision' appears in your error message implies to me that you are writing to a numeric field of some type, perhaps accidentally... are you using [drumroll] User Defined SQL?![]()
If so, ensure all your columns and parameter markers are properly aligned so all fields are actually ending up in the right place in your table. Or let the stage generate the SQL.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 30
- Joined: Fri May 26, 2006 6:01 am
Hi,ray.wurlod wrote:In the Columns grid on the link(s) where this column appears, what are the SQL Data Type and Precision settings? ...
In the Column Grid on link the sql data type was varchar and the length was 1500.
Other than this i have not given anything extra.
Please let me know if any extra information is required.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What makes you sure that this is the culprit? Could it be some other Char, Varcher or Numeric column that lacks any precision setting, or has an invalid precision setting, that might be the cause? Certainly the cobination VarChar and 1500 is perfectly valid.
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.
Please describe all stages used in this job, as your value may be getting lost in a prior stage and the error message relates to that stage.
Please paste the EXACT and ENTIRE message, as it often names the stage and link where the error is occurring.
Please paste the EXACT and ENTIRE message, as it often names the stage and link where the error is occurring.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
varchar(1500) is valid and I have used this...
varchar(1500) is valid and I have used this before... but I had aproblem when I used a column with datatype varchar(4000). This was not giving any error or warnings but it was inserting spaces into the target. This was resolved when I changed varchr ro char
Joji John
-
- Participant
- Posts: 232
- Joined: Fri Sep 30, 2005 4:52 am
- Contact:
Re: varchar(1500) is valid and I have used this...
jojipjohn wrote: while importing definations for that column i have given it as varchar(1500)
Have you provided it manually... Use whatever metadata coming for column after improting from database.
Thanks,
Anupam