ORA-27370: job slave failed to launch a job of type EXECUTABLE

Cause : The scheduler ran into an error when the job slave tried to start a job of type EXECUTABLE. The rest of the error stack will provide more detailed information on what the exact problem was.

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

Correct the problem specified in the error stack and reschedule the job.

update : 27-04-2017

ORA-27370 - job slave failed to launch a job of type EXECUTABLE
ORA-27370 - job slave failed to launch a job of type EXECUTABLE

  • ora-06911 : CMX: t_event returns ERROR
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-30960 : The entity is neither an XPATH nor a NAMESPACE.
  • ora-29529 : invalid function or method call string in trigger string
  • ora-00160 : global transaction length string is greater than maximum (string)
  • ora-03113 : end-of-file on communication channel
  • ora-29262 : bad URL
  • ora-07549 : sftopn: $OPEN failure
  • ora-22874 : attribute "string" is not part of the type "string"
  • ora-12073 : request cannot be processed
  • ora-29913 : error in executing string callout
  • ora-12725 : unmatched parentheses in regular expression
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-33219 : (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-01517 : log member: 'string'
  • ora-13798 : Parameter string cannot be NULL.
  • ora-39179 : unable to load table "string"."string" because of OID transform
  • ora-01486 : size of array element is too large
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-13799 : threshold not found
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-25450 : error string during evaluation of rule set string.string
  • ora-09321 : slzdtb: unable to convert zoned decimal to binary
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-13154 : invalid precision specified
  • ora-06267 : NETNTT: bad state
  • ora-32133 : Cannot get stream from LOB/FILE
  • 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.