Partitioned Table With User Defined Type Causes ORA-21700 On Update Of Partition Key After Dropping Type (Doc ID 1484903.1)

Last updated on MARCH 27, 2014

Applies to:

Oracle Server - Enterprise Edition - Version 11.1.0.7 to 11.2.0.3 [Release 11.1 to 11.2]
Information in this document applies to any platform.

Symptoms

After dropping a type used in a partitioned table with force option, column is no longer shown on table nor dictionary tables, but UPDATE command raises error:

ORA-21700: object does not exist or is marked for delete.

Error is reported for 11.1.0.7, and reproducible in 11.2.0.3 as well.

The following example illustrates the behaviour.

Sample output of the last few commands are the following:

SQL> SELECT * FROM test1;

   COL1_PK COL2_PART_KEY COL3_DATA
---------- ------------- -------------------------------------------
         1      20120001 data 1
         2      20120002 data 2

SQL>  UPDATE test1 set col2_part_key = 3 WHERE col1_pk = 2;
UPDATE test1 set col2_part_key = 3 WHERE col1_pk = 2
       *
ERROR at line 1:
ORA-21700: object does not exist or is marked for delete


SQL> INSERT INTO test1 VALUES (3,20120001, 'data 1');

1 row created.

SQL> DELETE test1;

3 rows deleted.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms