ORA-27074: unable to determine limit for open files

Cause : The getlrimit() ysstem call returnde an errro.

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

Check errno.

update : 21-08-2017
ORA-27074

ORA-27074 - unable to determine limit for open files
ORA-27074 - unable to determine limit for open files

  • ora-01664 : Transaction which has expanded the Sort Segment has aborted
  • ora-30653 : reject limit reached
  • ora-25438 : invalid variable name: string
  • ora-28164 : REVOKE already specified
  • ora-03254 : unable to execute the sql in read only database
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-06521 : PL/SQL: Error mapping function
  • ora-26508 : null materialized view connection
  • ora-16133 : Datafile string has incorrect terminal recovery stamp.
  • ora-32312 : cannot refresh a secondary materialized view "string"."string"
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-19031 : XML element or attribute string does not match any in type string.string
  • ora-12350 : database link being dropped is still mounted
  • ora-25124 : Database link name not allowed.
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-14154 : only one of STORE IN or clause may be specified
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-09950 : Unable to get server operating system privileges
  • ora-31607 : function string is inconsistent with transform.
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-27463 : invalid program type string
  • ora-23471 : template not authorized for user
  • ora-16244 : taking checkpoint and paging out string bytes to disk
  • ora-24038 : RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
  • ora-19034 : Type not supported during schema generation
  • ora-01503 : CREATE CONTROLFILE failed
  • ora-07745 : slemcl: $CLOSE failure
  • ora-31500 : change source string is not a ManualLog change source
  • ora-24075 : cannot specify agent with NULL address and non-NULL protocol
  • 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.