Error ORA-01461
Moderators: chulett, rschirm, roy
Error ORA-01461
Hi All
We are migrating from the 8.7 to the 11.5 version.
We have the Error ORA-01461 in a very simple job who read a file to upsert a table.
The key of the table is a varchar(9) but it contains only numerical characters (ex 007660008).
I presume that the connector see the value like a long even so it's define in varchar 9.
How can i handle this ?
Thank you.
We are migrating from the 8.7 to the 11.5 version.
We have the Error ORA-01461 in a very simple job who read a file to upsert a table.
The key of the table is a varchar(9) but it contains only numerical characters (ex 007660008).
I presume that the connector see the value like a long even so it's define in varchar 9.
How can i handle this ?
Thank you.
Hope This Helps
Regards
Regards
ORA-01461: can bind a LONG value only for insert into a LONG column
It's typically about a CLOB field unless your Oracle is ancient and still actually has LONG as a datatype. Can't have anything to do with your VC2(9) field so seems to me we'd need to see the metadata for all of the columns to offer any further help.
It's typically about a CLOB field unless your Oracle is ancient and still actually has LONG as a datatype. Can't have anything to do with your VC2(9) field so seems to me we'd need to see the metadata for all of the columns to offer any further help.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I've got a few vicarious migrations under my belt from hanging out here.
And yes, you should not be surprised to find several things that used to "work fine" but were actually only working because of loopholes or bugs in the old version you were taking advantage of (so to speak), issues that have since been plugged or tightened up as Paul mentioned. Especially with such a long upward leap as you are taking.
And yes, you should not be surprised to find several things that used to "work fine" but were actually only working because of loopholes or bugs in the old version you were taking advantage of (so to speak), issues that have since been plugged or tightened up as Paul mentioned. Especially with such a long upward leap as you are taking.
-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:
Sometime in my near future I'm doing an upgrade from 8.0.1 on AIX to 11.7.0.1 on (RHEL on) cloud. Not really looking forward to that one. And they want Stewardship Center and Enterprise Search.
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.
Well, then that means it's time to involve support unless you are short on fixpacks, in which case I'd suggest you get current for your release. There's absolutely no reason that putting 'only digits' into a string would case any kind of problem.
Only other thing I'd throw out there: have you tried to explicitly substring that problem field down to size before sending it to the connector? Really shouldn't be necessary but IMHO would be a good test before you report the issue.
Only other thing I'd throw out there: have you tried to explicitly substring that problem field down to size before sending it to the connector? Really shouldn't be necessary but IMHO would be a good test before you report the issue.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
We are doing a 9.1.2 to 11.5 Migration on AIX to LINUX and there are a number of "gotchas", but not this ORA-error is not among them.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>