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-05-2017

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

  • ora-01279 : db_files too large
  • ora-01522 : file 'string' to be renamed does not exist
  • ora-19669 : proxy copy functions cannot be run on DISK channel
  • ora-09811 : Unable to initialize package.
  • ora-29550 : Java session state cleared
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-19118 : duplicate default namespace definition - string
  • ora-36688 : (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
  • ora-09263 : spini: error initializing process
  • ora-15100 : invalid or missing diskgroup name
  • ora-28512 : cannot get data dictionary translations from string
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-07490 : scgrcl: cannot convert lock.
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-24323 : value not allowed
  • ora-12156 : TNS:tried to reset line from incorrect state
  • ora-27452 : %s is an invalid name for a database object.
  • ora-09934 : Link of current password file to old failed.
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-12673 : Dedicated server: context not saved
  • ora-07511 : sscggtl: $enq unexpected return for master termination lock
  • ora-32310 : object materialized views must select from an object table
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-22308 : operation not allowed on evolved type
  • ora-19722 : datafile string is an incorrect version
  • ora-29844 : duplicate operator name specified
  • 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.