Conversion issue
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 72
- Joined: Wed Dec 12, 2007 2:29 am
Conversion issue
Hi Friends
I am getting below warning messages in multiple jobs
Implicit conversion from source type "string[max=24]" to result type "string[max=8]": Possible truncation of variable length string.
These warnings were not coming earlier.
We had a DB maintenance after which we are seeing these errors. Also interestingly these errors come in the first run after db maintenance. From the second run,most of the warnings gets corrected. In both the runs, code and data is exactly same.
We are using Oracle 10g as database.
Please suggest
Thanks
I am getting below warning messages in multiple jobs
Implicit conversion from source type "string[max=24]" to result type "string[max=8]": Possible truncation of variable length string.
These warnings were not coming earlier.
We had a DB maintenance after which we are seeing these errors. Also interestingly these errors come in the first run after db maintenance. From the second run,most of the warnings gets corrected. In both the runs, code and data is exactly same.
We are using Oracle 10g as database.
Please suggest
Thanks
Some questions come to mind:
- What is your SELECT statement to get this column? (Is it a database or a derived column)
- If a database column, what does a "describe" show for the exact same table, schema, database and user show in Oracle?
- What is your SELECT statement to get this column? (Is it a database or a derived column)
- If a database column, what does a "describe" show for the exact same table, schema, database and user show in Oracle?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 72
- Joined: Wed Dec 12, 2007 2:29 am
-
- Participant
- Posts: 72
- Joined: Wed Dec 12, 2007 2:29 am
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Participant
- Posts: 72
- Joined: Wed Dec 12, 2007 2:29 am
Please activate $OSH_PRINT_SCHEMAS as a parameter and run the job with it set to "true". Look at the schemas to make sure of what datatype the column is at each stage.
Something odd is happening. Is this only for one column or for all text columns? Is this example of a varchar(24) one of the columns that stops erroring after a run or one where the warning remains?
Something odd is happening. Is this only for one column or for all text columns? Is this example of a varchar(24) one of the columns that stops erroring after a run or one where the warning remains?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
It will give warning because source is 24 and we are truncating data to 8, better use the substring functionality. var = trim(input)[1,8]
I hope, we will not get more than 8 char in input
I hope, we will not get more than 8 char in input
~Atul Singh
<a href=http://www.datagenx.net>DataGenX</a> | <a href=https://www.linkedin.com/in/atulsinghds>LinkedIn</a>
<a href=http://www.datagenx.net>DataGenX</a> | <a href=https://www.linkedin.com/in/atulsinghds>LinkedIn</a>