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 : 24-04-2017
ORA-02310

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

  • ora-39700 : database must be opened with UPGRADE option
  • ora-24408 : could not generate unique server group name
  • ora-07290 : sksagdi: specified directory for archiving does not exist.
  • ora-30100 : internal error [number]
  • ora-02391 : exceeded simultaneous SESSIONS_PER_USER limit
  • ora-09265 : spwat: error temporarily suspending process
  • ora-01289 : cannot add duplicate logfile string
  • ora-00111 : invalid attribute string
  • ora-09968 : unable to lock file
  • ora-24130 : table string does not exist
  • ora-02198 : ONLINE/OFFLINE option already specified
  • ora-28166 : duplicate rolename in list
  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-06137 : NETTCP: error during connection handshake
  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-25187 : specified exceptions table form incorrect
  • ora-25352 : no current transaction
  • ora-09274 : szrfc: insufficient role name buffer space
  • ora-37008 : (AWLISTALL06) number writers
  • ora-16104 : invalid Logical Standby option requested
  • ora-27486 : insufficient privileges
  • ora-31042 : Too many properties in type 'string'
  • ora-01987 : client os username is too long
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-12827 : insufficient parallel query slaves available
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-13415 : invalid or out of scope point specification
  • ora-22878 : duplicate LOB partition or subpartition specified
  • ora-12043 : invalid CREATE MATERIALIZED VIEW option
  • ora-19901 : database needs more recovery to create new incarnation
  • 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.