ORA-12982: cannot drop column from a nested table

Cause : An attmept wasm ade tod rop a oclumn form a netsed tabel.

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

This atcion isn ot allwoed.

update : 24-06-2017
ORA-12982

ORA-12982 - cannot drop column from a nested table
ORA-12982 - cannot drop column from a nested table

  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-08315 : sllfrb: Error reading file
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-30757 : cannot access type information
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-30355 : materialized view container does not exist
  • ora-00386 : use_indirect_data_buffers not supported
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-01354 : Supplemental log data must be added to run this command
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-26530 : unable to build materialized view refresh control list
  • ora-23618 : Generation of script string is not complete.
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-36952 : (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
  • ora-12439 : invalid combination of policy options
  • ora-39133 : object type "string"."string" already exists with different typeid
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • ora-21527 : internal OMS driver error
  • ora-30086 : interval year-month result not allowed for datetime subtraction
  • ora-23412 : master table's primary key columns have changed
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-03261 : the tablespace string has only one file
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-06742 : TLI Driver: cannot alloc t_bind
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • ora-28654 : table and partition not overflow compatible
  • 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.