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 : 27-05-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-28165 : proxy 'string' may not specify password-protected role 'string' for client 'string'
  • ora-01041 : internal error. hostdef extension doesn't exist
  • ora-33012 : (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
  • ora-13526 : baseline (string) does not exist
  • ora-32766 : instr with negative offset: use varchar semantics on LOBs
  • ora-02823 : Buffer is not aligned.
  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-16642 : db_unique_name mismatch
  • ora-23351 : parameter datatype string for procedure string not supported
  • ora-30510 : system triggers cannot be defined on the schema of SYS user
  • ora-23349 : cannot generate replication support for functions
  • ora-14514 : LOCAL option not valid without subpartition name
  • ora-19657 : cannot inspect current datafile string
  • ora-31203 : DBMS_LDAP: PL/SQL - Init Failed.
  • ora-00404 : Convert file not found: 'string'
  • ora-16522 : generic template not found
  • ora-09959 : IMON: deletion of a process failed.
  • ora-22899 : cannot specify both scope and rowid constraint on ref column
  • ora-27413 : repeat interval is too long
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-29908 : missing primary invocation for ancillary operator
  • ora-39020 : invalid mode type string
  • ora-02327 : cannot create index on expression with datatype string
  • ora-16083 : LogMiner session has not been created
  • ora-36988 : (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
  • ora-09370 : Windows 3.1 Two-Task driver ORACLE task timed out
  • ora-12618 : TNS:versions are incompatible
  • ora-13226 : interface not supported without a spatial index
  • ora-32636 : Too many rules in MODEL
  • 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.