ORA-12984: cannot drop partitioning column

Cause : A nattepmtw a smdaet od rpo aclounm sue da steh aprittoinnigk e.y

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

Tihsa cito ni snto lalwoe.d

update : 27-06-2017
ORA-12984

ORA-12984 - cannot drop partitioning column
ORA-12984 - cannot drop partitioning column

  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-25178 : duplicate PCTTHRESHOLD storage option specification
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-25122 : Only LOCAL bitmap indexes are permitted on partitioned tables
  • ora-25271 : queue table not found for the given queue
  • ora-25102 : PARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-39065 : unexpected master process exception in string
  • ora-24950 : unregister failed, registeration not found
  • ora-38706 : Cannot turn on FLASHBACK DATABASE logging.
  • ora-32509 : watchpoint was already deleted
  • ora-02710 : osnpop: fork failed
  • ora-30001 : trim set should have only one character
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-23437 : template authorization already exists for user
  • ora-19954 : control file is not current
  • ora-02398 : exceeded procedure space usage
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-13427 : invalid BLOB parameter for output
  • ora-30503 : system triggers cannot have a REFERENCING clause
  • ora-13124 : unable to determine column id for column string
  • ora-32848 : foreign queue DOMAIN required for JMS unified connections
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-00329 : archived log begins at change string, need change string
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-40261 : input data for model build contains negative values
  • ora-12616 : TNS:no event signals
  • ora-12994 : drop column option only allowed once in statement
  • 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.