ORA-01779 Error - on a table!

Hello all!
We have a problem here which cannot possibly be - somehow. We have an update on a table which is done by our own framework. Oracle replies with a 01779 error which can only occur on a view if I'm not totally wrong. Has anyone an idea or do you need additional information?
Greetings,
Daniel

Here is your formatted post --
TABLE_NAME TABLESPACE_NAME      CLUSTER_NAME                IOT_NAME PCT_FREE           PCT_USED INI_TRANS           MAX_TRANS           INITIAL_EXTENT        NEXT_EXTENT             MIN_EXTENTS           MAX_EXTENTS
VIEW_FIDES_ERST_EWB SYSTEM      10                     40                      1                     255                     1761280   4362240             1                249
PCT_INCREASE           FREELISTS            FREELIST_GROUPS        LOGGING BACKED_UP NUM_ROWS           BLOCKS EMPTY_BLOCKS      AVG_SPACE CHAIN_CNT AVG_ROW_LEN         AVG_SPACE_FREELIST_BLOCKS NUM_FREELIST_BLOCKS   DEGREE INSTANCES           CACHE
50                1                1                YES      N      1                1                N
TABLE_LOCK SAMPLE_SIZE             LAST_ANALYZED          PARTITIONED IOT_TYPE     TEMPORARY SECONDARY NESTED BUFFER_POOL ROW_MOVEMENT GLOBAL_STATS USER_STATS DURATION       SKIP_CORRUPT MONITORING CLUSTER_OWNER DEPENDENCIES
ENABLED     NO                     N                N       NO            DEFAULT   DISABLED NO      NO           DISABLED   NO           DISABLED
1 rows selected
OWNER                     OBJECT_TYPE
SYSADM                     TABLE
1 rows selected This will be more readable format.
Regards.
Satyaki De.
N.B.: I hope this one much more readable than previous one...

Similar Messages

Dbms_xmlschema.registerschema, (ORA-31084: error while creating table )..

Hello,
I have some problems with dbms_xmlschema.registerschema
My database is: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
My XSD schema is (SEPA pain.002.001.03.xsd) also available on this url: http://code.google.com/p/leontestbed/source/browse/trunk/bc2/sample/Schema/pain.002.001.03.xsd?r=241
After
begin
   DOK_XML_UTIL.p_vnesi_xsd_blob(401941242); -- store a XSD on file system from blob field
   dbms_xmlschema.registerschema(
    schemaurl => 'http://localhost/TEST1.XSD',
    schemadoc => bfilename('ETAX_LOAD','TEST1.XSD'),
    csid => nls_charset_id('AL32UTF8'));
commit;
end;I get:
ORA-31084: error while creating table "INIS_PROD"."Document2781_TAB" for element "Document"
ORA-02320: failure in creating storage table for nested table column "XMLDATA"."CstmrPmtStsRpt"."OrgnlPmtInfAndSts"
ORA-01792: maximum number of columns in a table or view is 1000
ORA-02310: exceeded maximum number of allowable columns in table
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 37
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 65
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 136
ORA-06512: at line 4
What I'am doing wrong or what is the reason for this error..

Arrgghhh.....
begin
   DOK_XML_UTIL.p_vnesi_xsd_blob(401941242);
   dbms_xmlschema.registerschema(
    schemaurl => 'http://localhost/TEST1.XSD',
    schemadoc => bfilename('ETAX_LOAD','TEST1.XSD'),
    csid => nls_charset_id('AL32UTF8')
    , local => true
, genTypes => false
, genTables => false);
commit;
end;sorry...

Raising ora-01426 error while truncating table

Hi,
We have a procedure which executes in the following process for few set of tabls
1. disables the constraints
2. truncating the tables
3. enabling the constraints
but after processing for 5 tables, while truncating the error throws
BEGIN <procedure name >; END;
ERROR at line 1:
ORA-01426: numeric overflow
ORA-06512: at "<procedurename> ", line 33
ORA-06512: at line 1
this line 33 point to execute immeidate 'truncate table < table name>
Can i know what would be reason for throwing ' numeric overflow' error while truncating table..
Thanks in advance

user9080289 wrote:
thanks.
My oracle verision is 11gThen you could have the bug described there. Follow the instruction how to workaround (monitoring flush, set stats to low value) or apply the patch #8226471.
Nicolas.

ORA-02373 error on expdp, table failed to import!!

Hi All,
Would need a little help from you guys. I am trying to take export of an schema, and as the expdp continues, it throws error while exporting one of the tables. I tried looking over the net, but found nothing on this.
I think it is high time to have a say from the pros :) !!
Here goes the error:
=========================================================================
ORA-31693: Table data object "SCHEMA-NAME"."TABLE-NAME" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-02373: Error parsing insert statement for table "SCHEMA-NAME"."TABLE-NAME".
ORA-00904: : invalid identifier
=========================================================================
The DB Server is 11g.
Any kind of help will be greatly appreciated!
Thanks in Advance.
Noman A.

Hi Kumar,
This is the description of the table:
Name Null Type
ID NOT NULL VARCHAR2(64)
COL-1 VARCHAR2(128)
COL-2 VARCHAR2(128)
COL-3 NOT NULL VARCHAR2(64)
COL-4 NOT NULL VARCHAR2(64)
COL-5 NOT NULL VARCHAR2(64)
COL-6 NOT NULL VARCHAR2(64)
COL-7 VARCHAR2(64)
COL-8 VARCHAR2(255)
COL-9 NOT NULL VARCHAR2(64)
COL-10 NOT NULL TIMESTAMP(6)
COL-11 NOT NULL TIMESTAMP(6)
COL-12 NOT NULL CHAR(1)
COL-13 BLOB()
COL-14 VARCHAR2(512)
COL-15 CHAR(3)
Thanks
Noman A.

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.

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.

ORA - 01779 error

The following update works fine whereas the second one errors out with ora-01779.
/* SQL is working */
update <target_table> sls
set sls.<ID_Column> =
SELECT matr.<ID_Column>
FROM <Source_table> matr
where matr.<Key_Column> = sls.<Key_Column>
/* Error SQL */ -- Am using this for Performance
update
SELECT matr.<ID_Column> MATR_MATR_ID,
sls.<ID_Column> SLS_MATR_ID
FROM <Source_table> matr, <target_table> sls
where matr.<Key_Column> = sls.<Key_Column>
set SLS_MATR_ID = MATR_MATR_ID;

See:
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:760068400346785797
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:548422757486
And you can search for more examples on that site.

ORA-06502 error with external table having long records

I'm getting a strange error with the oci driver that I don't get with the thin driver.
The basic situation is that we using external tables and both the oci and thin drivers have been working until we tested with a table that had longer records than the previous tables. The new table has 1800 byte records.
The thin driver still works fine with the new table. However, the oci driver generates the following error with the new table:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
I suspect that with oci driver the oci DLLs are reading the external file and the DLLs can't handle the longer record length.
Particulars
- Oracle DB Server is 10.2.0.1 on SunOS 5.9
- OCI Instant Client instantclient_10_2 on Windows XP
- OCI client code from DB server installation running on DB server
- Works with thin driver from Windows XP and on DB server machine for all record lengths
- Works with both OCI drivers for records < 1800 bytes (don't know actual limit)
- Fails with both OCI drivers for records = 1800 bytes.
Does anyone out there have any thoughts.
Thanks in advance.

Your access parameters are in the wrong order. External tables are a bit fussy like that. Refer to the access_parameters section in the Utilities manual and follow the order there. From memory it will go something like this:
RECORDS DELIMITED...
LOG/BAD/DISCARDFILE...
FIELDS TERMINATED...LDRTRIM
MISSING FIELD VALUES...
fields...
)Regards...

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

SQL*LOADER 시 발생하는 ORA-1653 ERROR

제품 : SQL*PLUS
작성날짜 : 2002-04-25
SQL*LOADER 실행 시 발생하는 ORA-1653
====================================
PURPOSE
다음은 SQL*LOADER 실행시 ORA-1653 ERROR가 발생시에 조치하는
방법을 설명한다.
Explanation
ORA-1653 error 는 특정 tablespace 에 space 가 부족해서 table의
extent가 일어나지 못해서 발생하는 error 이다 .
먼저 error message 에서 tablespace name 이 무엇인지 먼저
check 한다.
그리고 다음 command 를 이용해 해당 tablespace 를 늘려주면 된다.
ALTER TABLESPACE tablespace_name ADD DATAFILE '.....' size 100m;
그러나 이때의 tablespace 가 SYSTEM 일 경우는 user 의 default
tablespace 가 잡혀있지 않기 때문이어서 근본적인 해결이 필요하다.
이 경우는 무작정 tablespsace 를 늘리지 말고 user 의 default
tablespace 를 create 후 user 에게 할당해주도록 한다.
CREATE TABLESPACE tablespace_name datafile '...' size 100m;
ALTER USER user_name IDENTIFIED BY passwd
DEFAULT TABLESPACE tablespace_name
TEMPORARY TABLESPACE temp ;
위와 같이 user의 default tablespace 를 변환한 후, 이 default
tablespace 안에 create table을 다시 한 후 sql*loader 를 실행한다.
Reference Documents
--------------------

Hi,
You must have more than one tnsnames file or multiple installations of oracle. What i suggest you do (as I'm sure will be mentioned in ed's link that you were already pointed at) is the following (* i assume you are on windows?)
open a command prompt
set TNS_ADMIN=PATH_TO_DIRECTOT_THAT_CONTAINS_CORRECT_TNSNAMES_FILE (i.e. something like set TNS_ADMIN=c:\oracle\network\admin)
This will tell oracle use the config files you find here and no others
then try sqlldr user/pass@db (in the same dos window)
see if that connects and let us know.
Cheers,
Harry
http://dbaharrison.blogspot.com

ORA-13249: Error in Rtree .. Spatial Index fails 10.2.0.3.0

We have a table with spatial data (polygon), containing 2.4 million rows. SRID=8307. Creating spatial index fails on this table. Spatial version 10.2.0.3.0 and it is valid in dba_registry. Please help. Thanks in advance. Error message is
Error starting at line 3 in command:
CREATE INDEX SST_BASEDATA.SIDX_ISPSPATIALTEMP ON SST_BASEDATA.ISP_SPATIALTEMP (GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('tablespace=tdx_basedata_isp layer_gtype=POLYGON') PARALLEL
Error report:
SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: Error in Rtree: [mdrcrrdmddata, select /*+ PARALLEL(a, 32767) */ rid, cen from M8_1CC99$$ a where cen >= :1 and cen <= :2], 83243 83244
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10

We have a similar problem with ORACLE 10.2.0.3, SRID 31297, 2-dimensional data, points, lines polygon.
We installed a new Computer (WINDOWS 2003 Server, Oracle 10.2.0.3) and transfered an application from an existing Oracle 10.2.0.2 instance.
We transferred the data by exp/imp utility.
The creation of the index failed (during import or creating the index by a sql command)
for all tables with more than 2 mill rows with the following message:
SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
We did not get the ORA-13249 error.
For tables with less than 1 mill rows the index was created.
We decided to go back to Oracle 10.2.0.2 and all works fine.
We will upgrade the database to 10.2.0.3 when a patch will be available.

Problem in updating fa_additions SQL Error: ORA-01779: cannot modify a column which maps to a non key-preserved table

Hi,
After using sql loader to import informations in the table fa_mass_additions and after the functionnal uses a treatment to imputate this assets, it asks me to do an update on the table fa_additions to change the value of attribute1 but i get an error
Error report:
ORA-01779: cannot modify a column which maps to a non key-preserved table
ORA-06512: at line 11
01779. 00000 - "cannot modify a column which maps to a non key-preserved table"
*Cause:    An attempt was made to insert or update columns of a join view which
           map to a non-key-preserved table.
*Action:   Modify the underlying base tables directly.
please how can i do this update?

Hi,
The "fa_additions" is a view, not a table.
You should update the base table "fa_additions_b".
Regards,
Bashar

Error ORA-01779 while updating view

I am using oracle 9i version is 9.2.0.1.0, While updating i am getting error,which i mention below.
ORA-01779:cannot modify a column which maps to a non key-preserved table
In this view there is no any group function.
Help me please.

ORA-01779:
     cannot modify a column which maps to a non key-preserved table
Cause:      An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.
Action:      Modify the underlying base tables directly.

Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01779:

I have a tabular form based on a view like:
select
t1.id,
t2.network_id,
t2.month_id,
t2.icp_ic,
t1.status,
t1.disc_comment
from
table1 t1,
table2 t2
where
t1.month_id (+) = t2.month_id and
t1.network_id (+) = t2.network_id and
t1.icp_id (+) = t2.icp_id
id is a surrogate key of table1 and there is a trigger to populate this on insert. There is also a unique index on table2 (month_id, network_id, icp_id). When I change the disc_comment column through the form and try to save I get an error:
Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01779: cannot modify a column which maps to a non key-preserved table
If I take out the outer join, it works fine. The problem is table1 will not have a row for every row in table 2, hence I need the outer join. Any ideas how I can get around this problem?
Regards
Sadanand

Hi Andy,
Yes I am paginating the form and I am not getting a set of blank rows. What I mean by next set of records is - if the page is showing rows 11 to 20 and I enter a comment against row 15 and save, the form inserts the comment into the table via the INSTEAD OF trigger and the page automatically refreshes with rows 21 to 30 from the query. On the other hand, if I click Prev link and redisplay rows 11 to 20, change the comment and click on Save, the form updates the comment and refreshes the page with rows 11 to 20. If I update the comment again, it redisplays page with rows 11 to 20 and this is the behaviour I desire when I insert data. Remember that I am using outer join, so there will be a mix of inserts and updates of data. I hope my explanation is clear. I have tried removing the tabular form region and starting from scratch but that hasn't helped - maybe I will drop the page and recreate it.
As for checksum error, you are right - it disappears after I logout and login again.
Regards
Sadanand

Unable to Insert record In forms: error -ORA-01779 :cannot modify a column

Hi,
I have created one form with two block.
Block-1 : Based on View
Block-2 : Based on table
There is is relationship between Block-1 and Block-2.
Block-1 is populating from LOV.
I just need to insert /update record Block-2 based on data from Block-1
So Block-1 I have made read only at runtime (Inser/update all properties are false).
Now when I insert record in Block-2 based on record from block-1, and getting below error.
"ORA-01779: cannot modify a column which maps to a non key-preserved table"
It is not allowing to insert record.
Please help me.
Subir

The error states that there is some operation on a view, not an a table.
Now when I insert record in Block-2 based on record from block-1What does that mean? How do you insert records in block 2?
When exactly occurs the error?

ORA-01779 Error - on a table!

Similar Messages

Maybe you are looking for