ORA-27159: failure setting process scheduling priority

Cause : Oracle was unable to set the scheduling priority desired.

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

Consult the Oracle Administrator's Guide.

update : 30-04-2017
ORA-27159

ORA-27159 - failure setting process scheduling priority
ORA-27159 - failure setting process scheduling priority

  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-17502 : ksfdcre:string Failed to create file string
  • ora-12571 : TNS:packet writer failure
  • ora-32813 : propagation schedule string already exists
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-02466 : The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.
  • ora-21604 : property [string] is not a property of transient or value instances
  • ora-27013 : skgfqdel: cannot delete an open file
  • ora-31019 : Recursive deletion snapshot too old for string/string
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-24340 : cannot support more than 255 columns
  • ora-24436 : Invalid statement Handle.
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-24386 : statement/server handle is in use when being freed
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-16606 : unable to find property "string"
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-28534 : Heterogeneous Services preprocessing error
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-10639 : Dump library cache during kksfbc-reparse-infinite-loop error
  • ora-16508 : channel handle not initialized
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-19036 : Invalid query result set in newContextFromHierarchy()
  • ora-31210 : DBMS_LDAP: PL/SQL - LDAP get_dn error.
  • ora-17500 : ODM err:string
  • ora-00083 : warning: possibly corrupt SGA mapped
  • ora-06766 : TLI Driver: close failed during release
  • ora-23315 : repcatlog version or request string is not supported by version 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.