ORA-02310: exceeded maximum number of allowable columns in table

Cause : The attributes in the object type column exceeded the maximum number of columns allowed in a table.

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

Specify fewer attributes for the object type and retry the operation.

update : 25-05-2017

ORA-02310 - exceeded maximum number of allowable columns in table
ORA-02310 - exceeded maximum number of allowable columns in table

  • ora-16013 : log string sequence# string does not need archiving
  • ora-13189 : recursive SQL parse failed
  • ora-14510 : can specify VALIDATE INTO clause only for partitioned tables
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-02238 : filename lists have different numbers of files
  • ora-21560 : argument string is null, invalid, or out of range
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-06767 : TLI Driver: alloc failed during release
  • ora-09951 : Unable to create file
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-07594 : spiip: $GETJPIW failure
  • ora-19716 : error processing format string to generate name for backup
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-24273 : translation text is required if translation type is T or S
  • ora-28263 : Insufficient memory in global context pool
  • ora-25006 : cannot specify this column in UPDATE OF clause
  • ora-26010 : Column string in table string is NOT NULL and is not being loaded
  • ora-30677 : session is already connected to a debugger
  • ora-14001 : LOCAL clause contradicts previosly specified GLOBAL clause
  • ora-39078 : unable to dequeue message for agent string from queue "string"
  • ora-19103 : VALUE keyword keyword
  • ora-31052 : Cannot delete ACL with other references
  • ora-16252 : Rebuild operation not permitted
  • ora-30200 : Wrong NLS item was passed into OCINlsGetInfo()
  • ora-29875 : failed in the execution of the ODCIINDEXINSERT routine
  • ora-24330 : internal OCI error
  • ora-39014 : One or more workers have prematurely exited.
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • 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.