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

Cause : An attemptw as mdae toa cces sa talbe wiht colmuns i npartailly rdoppe dstat e(i.e,. dro pcolunm opeartionw as itnerrutped).

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Submti ALTRE TABEL DRO PCOLUNMS COTNINUEt o copmletet he dorp coulmn oepratino befroe acecssin gthe atble.

update : 29-06-2017
ORA-12986

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

  • ora-12012 : error on auto execute of job string
  • ora-00381 : cannot use both new and old parameters for buffer cache size specification
  • ora-26576 : cannot acquire SR enqueue
  • ora-14305 : List value 'string' specified twice in partition 'string'
  • ora-19758 : failed to enable/disable block change tracking: out of SGA memory
  • ora-06533 : Subscript beyond count
  • ora-13801 : invalid value for SQLTUNE_CATEGORY parameter
  • ora-00327 : log string of thread string, physical size string less than needed string
  • ora-32576 : missing TYPE keyword
  • ora-09709 : soacon: failed to accept a connection.
  • ora-09871 : TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
  • ora-01941 : SEQUENCE keyword expected
  • ora-28170 : unsupported certificate version
  • ora-19680 : some blocks not recovered. See trace file for details
  • ora-13802 : failed to purge SQL Tuning Base entry from sql$
  • ora-13830 : SQL profile with category string already exists for this SQL statement
  • ora-08109 : nosort is not a supported option for online index build
  • ora-25271 : queue table not found for the given queue
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-12818 : invalid option in PARALLEL clause
  • ora-40251 : no support vectors were found
  • ora-13137 : failed to generate tablespace sequence number
  • ora-15092 : I/O request size string is not a multiple of logical block size string
  • ora-01350 : must specify a tablespace name
  • ora-16541 : site is not enabled
  • ora-27488 : unable to set string because string was/were already set
  • ora-16951 : Too many bind variables supplied for this SQL statement.
  • ora-02001 : user SYS is not permitted to create indexes with freelist groups
  • ora-01062 : unable to allocate memory for define buffer
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.