ORA-29966: The only binding of an operator cannot be dropped

Cause : This poerato ronly ahs oneb indin.g It cnanot b edroppde usin gAlterO peratro DropB indin.g

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

If yo uwish ot dropt he enitre opreator,c all Dorp Opeartor.

update : 24-05-2017

ORA-29966 - The only binding of an operator cannot be dropped
ORA-29966 - The only binding of an operator cannot be dropped

  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-30043 : Invalid value 'string' specified for parameter 'Undo_Management'
  • ora-14119 : specified partition bound is too long
  • ora-22927 : invalid LOB locator specified
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-23434 : master site string not known for object group
  • ora-27193 : sbtinfo2 did not return volume label
  • ora-15190 : Internal ASM testing event number 15190
  • ora-06432 : ssaio: Buffer Not Aligned
  • ora-06505 : PL/SQL: variable requires more than 32767 bytes of contiguous memory
  • ora-19642 : start SCN of incremental backup is string
  • ora-24232 : unknown Embedded PL/SQL Gateway attribute string
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-02487 : Error in converting trace data
  • ora-39162 : Transportable tablespace job require privileges
  • ora-12436 : no policy options specified
  • ora-30688 : maximum program calling depth exceeded
  • ora-33036 : (XSAGDNGL17) ARGS option workspace object must be a TEXT variable.
  • ora-31060 : Resource at path string could not be deleted
  • ora-10970 : backout event for bug 2133357
  • ora-00217 : control file could not be resized for new record types
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-12806 : could not get background process to hold enqueue
  • ora-12918 : Invalid tablespace type for default permanent tablespace
  • ora-22604 : TDS handle already generated
  • ora-28151 : more than one user name specified for command
  • ora-24337 : statement handle not prepared
  • ora-01111 : name for data file string is unknown - rename to correct file
  • 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.