ORA-01461 Error when mapping table with multiple varchar2(4000) fields

(Note: I think this was an earlier problem, supposed fixed in 11.0, but we are experiencing in 11.7)
If I map an Oracle 9i table with multiple varchar2(4000) columns, targeting another Oracle 9i database, I get the ORA-01461 error (Can't bind a LONG value only for insert into a LONG).
I have tried changing the target columns to varchar2(1000), as suggested as a workaround in earlier versions, all to no avail.
I can have just one varchar2(4000) map correctly and execute flawlessly - the problem occurs when I add a second one.
I have tried making the target column a LONG, but that does not solve the problem.
Then, I made the target database SQL Server, and it had no problem at all, so the issue seems to be Oracle-related.

Hi Jon,
Thanks for the feedback. I'm unable to reproduce the problem you describe at the moment - if I try to migrate a TEXT(5), OMWB creates a VARCHAR(5) and the data migrates correctly!! However, I note from you description that even though the problematic source column datatype is TEXT(5), you mention that there are actually 20 lines of text in this field (and not 5 variable length characters as the definition might suggest).
Having read through some of the MySQL reference guide I note that, in certain circumstances, MySQL actually changes the column datatype specified either at table creation time or when interfacing with other databases ( ref 14.2.5.1 Silent Column Specification Changes and 12.7 Using Column Types from Other Database Engines in the MySQL reference guide). Since your TEXT(5) actually contains 20 lines of text, MySQL (database or JDBC driver .... or both) may be trying to automatically map the specified datatype of the column to a datatype more appropriate to storing 20 lines of text.... that is, to a LONG value in this case. Then, when Oracle is presented with this LONG value to store in a VARCHAR(5) field, it throws the ORA-01461 error. I need to investigate this further, but this may be the case - its the first time I've see this problem encountered.
To workaround this, you could change the datatype of the column to a LONG from within the Oracle Model before migrating. Any application code that accesses this column and expects a TEXT(5) value may need to be adjusted to cope with a LONG value. Is this a viable workaround for you?
I will investigate further and notiofy you of any details I uncover. We will need to track this issue for possible inclusion in future development plans.
I hope this helps,
Regards,
Tom.

Similar Messages

ORA-04062 error when running forms with different users

ORA-04062 error when running forms with different users
I have a form that has a block that should display some data from another users tables. (The other user's name is dynamic, it's selected from a list box)
I wrote a stored procedure to get the data from other user's tables.
When I compile the form and run it with the same user I compiled, it works without any error. But when I run the compiled form with another user I get the ORA-04062 (signature of procedure has been changed) error.
I tried setting REMOTE_DEPENDENCIES_MODE to SIGNATURE in init.ora but it didn't help.
My Forms version is 6i with Patch 15.
Database version is 9.
Here is my stored procedure:
TYPE Scenario_Tab IS TABLE OF NUMBER(34) INDEX BY BINARY INTEGER;
TYPE Open_Curs IS REF CURSOR;
PROCEDURE Get_Scenarios(User_Name IN VARCHAR2, Scen_Table OUT Scenario_Tab) IS
Curs Open_Curs;
i NUMBER;
BEGIN
OPEN Curs FOR
'SELECT Seq_No FROM '|| User_Name ||'.scenario';
i := 1;
LOOP
FETCH Curs INTO Scen_Table(i);
EXIT WHEN Curs%NOTFOUND;
i := i + 1;
END LOOP;
END Get_Senarios;
I would be happy to solve this problem. It's really important.
Maybe somebody can tell me another way to do what I want to do. (getting a list of values from another users tables)

I think it should be a better solution to create a package,
and put your own TYPES and procedure into it.
CREATE OR REPLACE PACKAGE PKG_XXX IS
TYPE TYP_TAB_CHAR IS TABLE OF .... ;
PROCEDURE P_XX ( Var1 IN VARCHAR2, var2 IN OUT TYP_TAB_CHAR );
END ;
Then in your Form :
Declare
var PKG_XXX.TYP_TAB_CHAR ;
Begin
PKG_XXX.P_XX( 'user_name', var ) ;
End ;

ORA-01461 error when migrating MySQL -- Oracle table data

All,
I'm migrating MySQL 4.x to Oracle10g. Everything went smoothly except for one table was unable to migrate data, giving me the following error:
Unable to migrate data from source table mysql.mytable to destination table root.MYTABLE :
ORA-01461: can bind a LONG value only for insert into a LONG columnThe offending source column in MySQL is defined as TEXT. In OMWB it is TEXT (5). The Oracle model originally defined it as VARCHAR2(1), but I resized it to VARCHAR2(4000) since it contains about 20 lines of text.
Neither the mysql or the oracle data models have a LONG column anywhere. Any idea's what might be causing this error?
Thanks.

Hi Jon,
Thanks for the feedback. I'm unable to reproduce the problem you describe at the moment - if I try to migrate a TEXT(5), OMWB creates a VARCHAR(5) and the data migrates correctly!! However, I note from you description that even though the problematic source column datatype is TEXT(5), you mention that there are actually 20 lines of text in this field (and not 5 variable length characters as the definition might suggest).
Having read through some of the MySQL reference guide I note that, in certain circumstances, MySQL actually changes the column datatype specified either at table creation time or when interfacing with other databases ( ref 14.2.5.1 Silent Column Specification Changes and 12.7 Using Column Types from Other Database Engines in the MySQL reference guide). Since your TEXT(5) actually contains 20 lines of text, MySQL (database or JDBC driver .... or both) may be trying to automatically map the specified datatype of the column to a datatype more appropriate to storing 20 lines of text.... that is, to a LONG value in this case. Then, when Oracle is presented with this LONG value to store in a VARCHAR(5) field, it throws the ORA-01461 error. I need to investigate this further, but this may be the case - its the first time I've see this problem encountered.
To workaround this, you could change the datatype of the column to a LONG from within the Oracle Model before migrating. Any application code that accesses this column and expects a TEXT(5) value may need to be adjusted to cope with a LONG value. Is this a viable workaround for you?
I will investigate further and notiofy you of any details I uncover. We will need to track this issue for possible inclusion in future development plans.
I hope this helps,
Regards,
Tom.

ORA-00977 Error When Moving Table Between Tablespaces

I used the "Alter table <tablename> move tablespace <newtablespace>" command on tables that contain a LONG datatype, and get an ORA-00977 error. Was successful with other tables that did not contain a LONG. This was on a 8.1.7.0 database, running on Solaris 8. Any idea what the problem is?

Like most other useful Oracle features, it is not supported on tables with long columns. In order to change tablespaces with this table, you will have to export it, drop it, recreate it in the new tablespace then import the data into the new table.
Your other choice is to rebuild the table using clob instead of long.

Error While mapping table with 100 Columns

Hello
Actually i had a requirement in which i have to map the data into target table from more than 50 tables with complex join conditions
So I created 5 maps separately to load the data and now i am feared that while i deploy the the first map the other columns which doesnt have a map
will be filled with nulls and some of the columns have unique constraint on it so its giving me error
Please Help me out i need to submit my Assignment by Monday
Thanks
Sriks

Bharadwaj Hari wrote:
Hi,
I agree with u...I am not sure of the environment the user has so i put forth all the 3 option that crossed my mind that time....thats why i said he has to choose what best suits him/her...
Also if the database is huge and we create physical temp tables (option 2 and ur idea) its like having redundant data in the database which is also a problem....So ist upto the user to actually evaluate the situation and come up with what best suits him/her...
Regards
BharathHi,
I understand your opinion. But I am not sure that the user have enough experience to choose the best option by his one. And about the redundant data: because of this I wrote that he should truncate the tables after the last mapping which loads all data into the real target table.
Regards,
Detlef

Error when creating table with nested table of object

Dear all,
I tried to create a table that contains nested table of an object but got an error:
create or replace type some_obj is object (
a number, b blob
4 /
Type created.
create or replace type some_type is table of some_obj;
2 /
Type created.
SQL>
create table test (obj_id number, temp some_type) nested table temp store as nes_tab;
Table created.
SQL> create table test (obj_id number, temp some_type) nested table temp store as nes_tab
ERROR at line 1:
ORA-00955: name is already used by an existing objectWhat is causing the error? How can I troubleshoot this?
best regards,
Val

Valerie Debonair wrote:
never mind, I put "/" at the end of the create statement that makes executing create table twice....Yep. If I'm writing a script, I tend to just stick with "/" for all my statements, including the SQL as well as the DDL, otherwise it can be confusing whether a ";" is needed or not or whether it will try and execute it twice like you found.
"/" works for all.

ORA-00904 error while export table with CLOB

All,
I'm trying to export from Oracle Client 8.0.4 an specific Oracle 9i R2 schema, but this error appears. This error is related with tables that have CLOB field types, because schemas with tables without this field type can be exported with no error. I've already run the catexp.sql script, but it haven't solved this problem.
Does anyone can help me?
Thanks,
Davi

You can try performing the import of the dump to see if it would work with 8i client or the 8.0.4 client.
if not, you may not be able to use this method to move data into 8.0.4 database that is no longer spported by current tools.
you may then want to try use other techniques like dumping tables into flat files and then using SQL*Loader to load into 8.0.4.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:88212348059#14506966201668

Ora-00600 error when registering xsd with large enumeration

I am trying to register the xsd:
http://212.130.77.78/StandatWS/StandatXSD.asmx/GetSchema?SchemaFile=std00019.xsd
It contains a very large enumerated type like this:
<xsd:simpleType name="std00019">
<xsd:annotation>
<xsd:documentation>Stofparametre</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="0000">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="0001">
<xsd:annotation>
<xsd:documentation>Syn</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
The file is more than 7000 lines of xml. If I try to cut it down to less than 4000 lines or so, then I can register it. Otherwise it give me an error like this:
1 begin
2 dbms_xmlschema.registerURI(
3 'http://212.130.77.78/StandatWS/StandatXSD.asmx/GetSchema?SchemaFile=std00019.xsd',
4 'http://212.130.77.78/StandatWS/StandatXSD.asmx/GetSchema?SchemaFile=std00019.xsd'
5 );
6* end;
SQL> /
begin
FEJL i linie 1:
ORA-00600: intern fejlkode, argumenter: [qmxiCreateColl2], [11], [], [], [],
ORA-06512: ved "XDB.DBMS_XMLSCHEMA_INT", linje 0
ORA-06512: ved "XDB.DBMS_XMLSCHEMA", linje 185
ORA-06512: ved linje 2
I am using 9.2.0.6.0
Do you know if there is a maximum length of an enumeration in oracle?

If you cannot post the schema please open a itar with oralce support so that the schema can be uploaded.

Error when mapping drive with read only permissions - unc path works fine

Hello,
we have user shares that we map to drive H:. the shares are in the form \\server\user\<loginname>. The shares have full permission and the files and folders have full permission for the user. To be clear, the shared folder is \\server\user. <loginname>
are several folders, one for each user.
We use a vb script to check if a user stores too much data and if yes, we set the permissions for the user to read only and delete (with icacls).
Unfortunately, it this happens, we cannot map the drive anymore on Windows 7 (on Windows XP it works fine). The error is "Permission denied". Interestingly, the user can still open the share with the unc - path.
Is there anything I can do, so that the user still has his drive mapped? Most user are not tech savvy enough to open their share with the unc - path.
Thank You,
Peter

Hi Peter,
Sorry for the delay in reply.
Please disable User Account Control in windows 7 to see if you can see the map drive. In the meantime, I suggest to use GPP instead of logon script to map drive.
GP Preferences Will Reduce Logon Scripts : Mapping Drives
http://blogs.technet.com/b/grouppolicy/archive/2009/02/11/gp-preferences-will-reduce-logon-scripts-mapping-drives.aspx
Please refer to the similar thread below to see if it helps:
Windows 7 Drive mapping via Logon script issue
http://social.technet.microsoft.com/Forums/en-US/6cdfae47-1ca0-46e8-8456-6aac2ee616b2/windows-7-drive-mapping-via-logon-script-issue
Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

ORA-00054 error when loading Oracle table using Data Services

Hello,
we are facing ORA-00054 error when loading Oracle table using BO Data services
(Oracle 10g database, BODS Xi 3.2 SP3)
Test Job performs
1- truncate table
2- load table (tested in standard and bulk load modes)
Scenario when issue happens is:
1- Run loading Job
2- Job end in error for any Oracle data base error
3- When re-running the same Job, Job fails with following error
ORA-00054: resource busy and acquire with NOWAIT specified
It seems after first failure, Oracle session for loading the table stays active and locks the table.
To be able to rerun the Job, we are forced need to kill Oracle session manually to be able to run the Job again.
Expected behaviour would be : on error rollback modifications made on table and BODS stops Oracle session in a clean way.
Can somebody tell me / or point me to any BODS best practice about Oracle error handling to prevent such case?
Thanks in advance
Paul-Marie

the ora-0054 can occure depending how the job failed before. If this occures you will need the DBA to release the lock on the table in question
Or
AL_Engine.exe on The server it creates the Lock. Need to Kill Them. Or stop it..
This Problem Occurs when we select The Bulkloading Option in orclae We also faced the same issue,Our admin has Killed the session. Then everything alright.

ORA-1722 ERROR WHEN SELECTING MFG_LOOKUPS TABLE

제품 : AOL
작성날짜 : 2003-04-07
ORA-1722 ERROR WHEN SELECTING MFG_LOOKUPS TABLE.
================================================
PURPOSE
Problem Description
sqlplus 에서 mfg_lookups table을 select할때,
ORA-1722 Invalid number 에러발생
Workaround
Solution Description
=======================================================
CREATE OR REPLACE VIEW mfg_lookups(
lookup_type,
lookup_code,
meaning,
description,
enabled_flag,
start_date_active,
end_date_active,
created_by,
creation_date,
last_update_date,
last_updated_by,
last_update_login
AS
SELECT lv.lookup_type,
TO_NUMBER(lv.lookup_code) lookup_code, <==== Wrong code!!!
lv.meaning,
lv.description,
lv.enabled_flag,
lv.start_date_active,
lv.end_date_active,
lv.created_by,
lv.creation_date,
lv.last_update_date,
lv.last_updated_by,
lv.last_update_login
FROM fnd_lookup_values lv
WHERE lv.LANGUAGE = USERENV('LANG') AND
lv.view_application_id = 700 AND
lv.security_group_id =
fnd_global.lookup_security_group(lv.lookup_type,
lv.view_application_id)
=================================================================
MFG_LOOKUPS 은 view로 fnd_lookup_values의 lookup_code값을 가지고 오는
방식이나, to_number로 변환하게 되어 있어 숫자가 아닌 문자의 경우
이와 같은 에러를 발생한다.
이번 경우, 고객이 새로 등록한 Lookup code였고, code값을 숫자의 format으로
다시 등록하니 해결됨.
Reference Documents
-------------------

Yes but this is a regular operation and the INSERT is the only opportunity.
BTW, look at what else I have just found:
INSERT INTO Local_Table (a, b)SELECT col1, col2 FROM DUAL INNER JOIN Table1@remote ON (1=1) LEFT JOIN Table2@remote ON (...)
OK.

ORA-0907 error when querying XMLDB Table using XMLExists

Hi All,
Get ORA-00907 error when trying to use XMLExists:
SELECT *
FROM tnmab_agreement_xml_binary A
WHERE
( XMLExists('declare default element namespace "http://com.oocl.schema.tnm.agreementbuilder"; $XML/Agreement/ShippingPartyGroups/ShippingParties/CustomerHolder[SAP_ID="$ARG"]')
passing agreements.AGREEMENT_XML as "XML", '5000003001' as "ARG")
OR
( XMLExists('declare default element namespace "http://com.oocl.schema.tnm.agreementbuilder"; $XML/Agreement/NamedCustomerGroups/NamedCustomer/SAP_IDs/StringWrappers[Value="$ARG"]')
passing agreements.AGREEMENT_XML as "XML", '5000003001' as "ARG")
ORA-00907: missing right parenthesis
*00907. 00000 - "missing right parenthesis"*
**Cause:*
**Action:*
Error at Line: 6 Column: 176
Any help is appreciated
Thanks
Auro

XMLExists('declare default element namespace "http://com.oocl.schema.tnm.agreementbuilder"; $XML/Agreement/ShippingPartyGroups/ShippingParties/CustomerHolder[SAP_ID="$ARG"]'
passing agreements.AGREEMENT_XML as "XML", '5000003001' as "ARG")no ')' after the closing quote

ORA -12569 error when querying dba_change_notification_regs table

Hi,
I am getting ORA-12569 error when i am trying to execute Select * from dba_change_notification_regs from sys user .we are working on oracle 10.2 version.
Please help in resoving the issue.
Thanks In advance.
Priya

ORA-12569:     TNS:packet checksum failure
Cause:      The data received is not the same as the data sent.
Action:      Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation.
If this doesn't resolve your issue, please see metalink 4933023.8 (problem fixed there)

ORA-00600:6711 When clicking tables in SQL Developer 1.5.1

Hello everyone.
This will be my first time to post something in this forum. I have used SQL Developer for quite sometime already and it has really helped me in my daily tasks. I am looking after multiple databases. I have no problem in moving around in most of them except one. I always encounter this ORA-600 error when I try to click on Tables from the tree on the left-hand side of the screen to list all the tables in the database. The suggested action is to "Report as a bug".
Hope anyone can help with this.

Nobody can help without details...
What DB? What version? Connection details? Can you connect with other tools?
K.

ORA-01461 error inserting over DB Link

We receive an ORA-01461 error (can bind a LONG value only for insert into a LONG column) when using HTMLDB to insert into a remote table over a database link. The remote table has two VARCHAR2 and one NUMBER columns - it does not contain a LONG column. Inserting via SQL*Plus is OK.
Any ideas anyone?
Barry

Anyone found a solution to this. I'm getting the same error. HTMLDB 1.6
I have TableA and TableB in remote db1. TableA=Master, TableB=Detail. Both tables have single column PK generated by a trigger.
In db2 I created a schema with viewA on TableA@db1 and viewB etc.
HTMLDB app accesses views.
I've tried to create a tabular form page to insert update delete into viewB but can only delete. Insert & update produces error:
Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01461: can bind a LONG value only for insert into a LONG column ORA-02063: preceding line from ORIXREPORTS.ORIXNZ.CO.NZ, update "IT_HTMLDB"."SCHEDULED_REPORT_PARAMETERS" set "SCHEDULED_REPORT_PARAMETER_ID" = :b1, "SCHEDULED_REPORT_ID" = :b2, "NAME" = :b3, "VALUE" = :b4, "VALUE_TYPE" = :b5 where "SCHEDULED_REPORT_PARAMETER_ID" = :p_pk_col
Have also tried a Master Detail page with similar problems.
I have only managed to get this to work by using the "Form on a Table with Report, 2 Pages" page creation option and then specifiying that Detail is editied in separate page. However this means deletes & updates are slow for the user as cannot do multi updates and deletes etc.
Any help appreciated.
Cheers
Ian

ORA-01461 Error when mapping table with multiple varchar2(4000) fields

Similar Messages

Maybe you are looking for