ORA-27378: cannot stop jobs of type EXECUTABLE on this platform

Cause : An attempt was made to stop a job of type EXECUTABLE on a platform where the stop operation was not supported.

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

If the attempt to stop the job was made with the FORCE option set to FALSE, try again but change the FORCE option to TRUE.

update : 25-06-2017
ORA-27378

ORA-27378 - cannot stop jobs of type EXECUTABLE on this platform
ORA-27378 - cannot stop jobs of type EXECUTABLE on this platform

  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-12994 : drop column option only allowed once in statement
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • ora-01010 : invalid OCI operation
  • ora-14619 : resulting List subpartition(s) must contain at least 1 value
  • ora-38409 : invalid name or option for the attribute set: string
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-01704 : string literal too long
  • ora-32512 : type 'string' is unknown
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-08121 : Number of indexes need to be maintained offline exceeds limit for DML
  • ora-29309 : export dump file was generated by different version of DBMS_PITR package
  • ora-16605 : unable to delete template, template is in use
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-02449 : unique/primary keys in table referenced by foreign keys
  • ora-31085 : schema "string" already registered
  • ora-39052 : cannot specify SKIP_CURRENT on initial start of a job.
  • ora-29521 : referenced name string could not be found
  • ora-22890 : cannot specify name for REF column constraint
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-09779 : snyGetPort: failure to allocate a port.
  • ora-18004 : outline already exists
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-01263 : Name given for file destination directory is invalid
  • ora-01124 : cannot recover data file string - file is in use or recovery
  • ora-16792 : configuration property value is inconsistent with database setting
  • 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.