Forum Stats

  • 3,769,469 Users
  • 2,252,968 Discussions
  • 7,875,040 Comments

Discussions

Categories

ORA-12986 ORA-00955 error after table set column as unused !

orasiya
orasiya Member Posts: 427 Bronze Badge
edited Mar 15, 2021 7:23AM in General Database Discussions

Dear firends,

I received the following erros, when accessing the table after table column drop !


ORA-12986: columns in partially dropped state. Submit the it ALTER TABLE DROP COLUMNS CONTINUE

ORA-00955: name is already used by an existing object

our database version is 18c (Exadata 7)

none of the following commands soloved our problems,

ALTER TABLE myTable DROP COLUMNS CONTINUE

ORA-12986: columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE


ALTER TABLE myTable DROP COLUMNS continue CHECKPOINT 250;

ORA-00955: name is already used by an existing object

any idea?


regards

Tagged:
· Share on TwitterShare on Facebook

Best Answer

Answers

  • EdStevens
    EdStevens Member Posts: 28,525 Gold Crown
    Accepted Answer

    It would help if we saw the actual, exact statement that produced the original error . . .

    · Share on TwitterShare on Facebook
  • orasiya
    orasiya Member Posts: 427 Bronze Badge

    alter table my_Table  set unused (col1);

    · Share on TwitterShare on Facebook
  • orasiya
    orasiya Member Posts: 427 Bronze Badge
    edited Mar 15, 2021 7:24AM

    ORA-12986 error after table column set as unused

    alter table my_Table set unused (col1);


    DB release 18c

    table size 15GB


    any idea for error ora-12986 ? is it a bug !

    regards

    · Share on TwitterShare on Facebook
  • Jonathan Lewis
    Jonathan Lewis Member Posts: 9,786 Gold Crown


    You need to remember exactly the sequence of events that resulted in this error.

    If you got ORA-12986 when you first attempted to set a column unused this means someone else had already done something to drop a column and had interrupted the process part way through.

    IF you can discover the exact history that's got you into the current position we may be able to help you.


    =======


    To investigate your current state, you should enable SQL tracing, and look in detail at the trace file for the first appearance of the error, this may tell you why you're getting the error you're getting.

    There's a note I wrote about a SIMILAR problem here: https://jonathanlewis.wordpress.com/2020/08/31/tracing-errors/ that demonstrates the approach.

    NOTE: this is NOT the problem you are describing even though the topic is about dropping columns.


    Regards

    Jonathan Lewis

    · Share on TwitterShare on Facebook