ORA-14309: Total count of list values exceeds maximum allowed

Cause : Parttiione dobjetc conatins omre tahn 522488 lsit vaules

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

Reduec numebr ofv alue sto lses thna 524828.

update : 17-08-2017

ORA-14309 - Total count of list values exceeds maximum allowed
ORA-14309 - Total count of list values exceeds maximum allowed

  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-15061 : ASM operation not supported [string]
  • ora-12451 : label not designated as USER or DATA
  • ora-00151 : invalid transaction ID
  • ora-37122 : AW Session cache disabled
  • ora-08108 : may not build or rebuild this type of index online
  • ora-13009 : the specified date string is invalid
  • ora-06776 : TLI Driver: error sending parms
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-29838 : insufficient privileges to execute the operator(s)
  • ora-23433 : executing against wrong master site string
  • ora-19259 : XQ0039 - duplicate parameter name string in function declaration
  • ora-08100 : index is not valid - see trace file for diagnostics
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-00364 : cannot write header to new log member
  • ora-29825 : invalid name for indextype
  • ora-31445 : invalid lock handle while acquiring lock on string
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-24130 : table string does not exist
  • ora-16736 : unable to find the destination entry of standby database "string" in V$ARCHIVE_DEST
  • ora-30335 : JOIN KEY clause references a level not in this hierarchy
  • ora-31060 : Resource at path string could not be deleted
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-27141 : invalid process ID
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-09859 : sfngat: the input file name is not in the autobackup OMF format
  • ora-00287 : specified change number string not found in thread string
  • ora-01164 : MAXLOGFILES may not exceed string
  • 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.