ORA-01792: maximum number of columns in a table or view is 1000

Cause : Ana ttmeptw asm ad etoc retae atalbe ro veiw iwthm or ethna 1000 oclunms,o r ot add mroe oclunms ot at abel o rviwe wihchp usehs ti oevr hte amxiumm laloawbl eliimt fo 1000.N ot ethta uunse dcoulmn sint het abel aer cuontde twoar dth e1000 cloum nliimt.

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

Ift hee rrro i sa ersutl o fa RCEAET cmomadn, htenr edcue hte unmbre o fcoulmn sint hec omamnda ndr esbumi.t I fth eerorr si ar eslut fo a nALETR ATBL Ecomman,d tehn hter ear etw oopiton:s 1 )Ift het abel cnotaniedu nuesd oclunms,r emvoe htemb y xeectuin gALETR ATBL EDRPO UUNSE DCOULMN Sbeofrea ddnig enw oclunms;2 ) eRduec teh nmube rofc olmunsi n hte ocmmnad nad ersumbit.

update : 28-07-2017
ORA-01792

ORA-01792 - maximum number of columns in a table or view is 1000
ORA-01792 - maximum number of columns in a table or view is 1000

  • ora-15111 : conflicting or duplicate STRIPE options
  • ora-30335 : JOIN KEY clause references a level not in this hierarchy
  • ora-12002 : there is no materialized view log on table "string"."string"
  • ora-09300 : osncon: unable to connect, DPMI not available
  • ora-32641 : invalid expression in MODEL rule ORDER BY clause
  • ora-38401 : synonym string not allowed
  • ora-06322 : IPA: Fatal shared memory error
  • ora-29501 : invalid or missing Java source, class, or resource name
  • ora-30041 : Cannot grant quota on the tablespace
  • ora-02201 : sequence not allowed here
  • ora-01743 : only pure functions can be indexed
  • ora-38731 : Expected version string does not match string in log header.
  • ora-02086 : database (link) name is too long
  • ora-22607 : image handle already generated
  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-12986 : columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-00702 : bootstrap verison 'string' inconsistent with version 'string'
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-37122 : AW Session cache disabled
  • ora-00055 : maximum number of DML locks exceeded
  • ora-12205 : TNS:could not get failed addresses
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-39076 : cannot delete job string for user string
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • 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.