ORA-00057: maximum number of temporary table locks exceeded

Cause : The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.

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

Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.

update : 27-04-2017
ORA-00057

ORA-00057 - maximum number of temporary table locks exceeded
ORA-00057 - maximum number of temporary table locks exceeded

  • ora-24359 : OCIDefineObject not invoked for a Object type or Reference
  • ora-02833 : Server was unable to close file
  • ora-23405 : refresh group number string does not exist
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-13250 : insufficient privileges to modify metadata table entries
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-22615 : attribute is not a collection
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-32021 : parameter value longer than string characters
  • ora-06042 : NETDNT: message receive failure
  • ora-32123 : Attribute number is out of range
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-06126 : NETTCP: ORASRV unable to open network connection
  • ora-32403 : cannot use new values from mv log on "string"."string"
  • ora-40254 : priors cannot be specified for one-class models
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-03129 : the next piece to be inserted is required
  • ora-16094 : database shutdown during archival operation
  • ora-16788 : unable to set one or more database configuration property values
  • ora-12624 : TNS:connection is already registered
  • ora-29800 : invalid name for operator
  • ora-38782 : cannot flashback database to non-guaranteed restore point 'string'
  • ora-38483 : invalid FUNCTION/PACKAGE/TYPE name: "string"
  • ora-16228 : Insufficient recovery for logical standby
  • ora-10700 : Alter access violation exception handler
  • ora-28557 : unknown string for database link to non-Oracle system
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-16784 : the database name in Dependency property is incorrect
  • 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.