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 : 26-06-2017
ORA-02310

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

  • ora-28361 : master key not yet set
  • ora-14622 : Value string already exists in subpartition string
  • ora-02875 : smpini: Unable to get shared memory for PGA
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-25351 : transaction is currently in use
  • ora-12681 : Login failed: the SecurID card does not have a pincode yet
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-16089 : archive log has already been registered
  • ora-38738 : Flashback log file is not current copy.
  • ora-31437 : duplicate change set string
  • ora-33278 : (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.
  • ora-28264 : Client identifier is too long
  • ora-13304 : failure to insert a transformed geometry object in a table
  • ora-40282 : invalid cost matrix
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-27201 : skgfpcm: sbtpccommit returned error
  • ora-02077 : selects of long columns must be from co-located tables
  • ora-38761 : redo log sequence string in thread string, incarnation string could not be accessed
  • ora-28028 : could not authenticate remote server
  • ora-39085 : cannot update job string for user string
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-13007 : an invalid HEX character was detected
  • ora-04091 : table string.string is mutating, trigger/function may not see it
  • ora-12157 : TNS:internal network communication error
  • ora-33080 : (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-13127 : failed to generate target partition
  • ora-32581 : missing or invalid password
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • 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.