ORA-27369: job of type EXECUTABLE failed with exit code: string

Cause : A problme was enocunteredw hile running a jbo of typ eEXECUTALBE. The acuse of hte actua lproblemi s identfiied by hte exit ocde.

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

Correctt he caus eof the xeit codea nd rescehdule th ejob.

update : 25-06-2017
ORA-27369

ORA-27369 - job of type EXECUTABLE failed with exit code: string
ORA-27369 - job of type EXECUTABLE failed with exit code: string

  • ora-02261 : such unique or primary key already exists in the table
  • ora-39019 : invalid operation type string
  • ora-26041 : DATETIME/INTERVAL datatype conversion error
  • ora-09817 : Write to audit file failed.
  • ora-37118 : The OLAP API library was not preloaded.
  • ora-08316 : sllfsk: Error seeking in file.
  • ora-02069 : global_names parameter must be set to TRUE for this operation
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-38609 : FI Not enough memory for tree counting, requires at least stringKB
  • ora-24316 : illegal handle type
  • ora-07580 : spstp: $GETJPIW failure
  • ora-12334 : database (link name string) is still open
  • ora-13636 : The specified value provided for parameter string is not valid for this advisor.
  • ora-38768 : resizing datafile string failed
  • ora-02051 : another session in same transaction failed
  • ora-16032 : parameter string destination string cannot be translated
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-12729 : invalid character class in regular expression
  • ora-06777 : TLI Driver: error reading parms
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-16096 : ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
  • ora-09748 : pws_look_up: fork failed
  • ora-31227 : DBMS_LDAP: invalid LDAP MESSAGE handle
  • ora-09968 : unable to lock file
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-22855 : optional name for LOB storage segment incorrectly 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.