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 : 17-08-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-01041 : internal error. hostdef extension doesn't exist
  • ora-06710 : TLI Driver: send interrupt break message failed
  • ora-16526 : unable to allocate task element
  • ora-30552 : The package/procedure/function cannot be changed
  • ora-31073 : Resource not retrieved using path name
  • ora-01215 : enabled thread string is missing after CREATE CONTROLFILE
  • ora-13428 : invalid modelCoordinateLocation
  • ora-12433 : create trigger failed, policy not applied
  • ora-12625 : TNS:missing argument
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-13192 : failed to read number of element rows
  • ora-19776 : PROXY restore to ASM diskgroup "string" is not supported.
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-02469 : Hash expression does not return an Oracle Number.
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-39783 : Invalid direct path transaction active
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-29876 : failed in the execution of the ODCIINDEXDELETE routine
  • ora-16771 : failover to a physical standby database failed
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-01559 : MAXEXTENTS for rollback segment must be greater than 1
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-33274 : (DBERR07) Timed out while trying to lock analytic workspace string for string.
  • ora-24009 : invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
  • ora-38741 : Formatted blocks value string is not valid.
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-30940 : Cannot resolve prefix 'string' for QName node '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.