Page 1 of 1

Error ORA-01461

Posted: Thu Jun 21, 2018 11:44 am
by thurmy34
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.

Posted: Thu Jun 21, 2018 12:14 pm
by chulett
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.

Posted: Thu Jun 21, 2018 3:17 pm
by PaulVL
I've got a few migrations under my belt now. The 1# issue encountered is Metadata related. Bad columns in the old job that were "warnings" are now aborts.

Posted: Thu Jun 21, 2018 3:30 pm
by chulett
I've got a few vicarious migrations under my belt from hanging out here. :wink:

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.

Posted: Thu Jun 21, 2018 6:23 pm
by ray.wurlod
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.

Posted: Fri Jun 22, 2018 1:47 am
by thurmy34
Hi
Here is the metaData
File
C1 Varchar(255)
C2 Varchar(255)
Connector
C1 Varchar(9)
V2 Varchar(32)
The error is on the column C1 who contains only digits.

Ps : we all agree that a migration is painfull !

Thank you

Posted: Fri Jun 22, 2018 6:39 am
by chulett
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.

Posted: Fri Jun 22, 2018 8:33 am
by ArndW
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.

Posted: Fri Jun 22, 2018 8:39 am
by thurmy34
Hi
The problem is solve.
The problem was the French accent is the C2 Column.
We change the NLS from NONE to MS1252-CS and everything is okay now.
Thank you

Posted: Fri Jun 22, 2018 9:00 am
by chulett
Not any kind of an expected error from that situation but glad you worked it out.