ORA-27371: jobs of type EXECUTABLE are not supported on this platform

Cause : The user tried to create a job or program of type EXECUTABLE on a platform where such jobs are not supported.

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

Switch to a different platform or create a different type of job or program.

update : 28-04-2017
ORA-27371

ORA-27371 - jobs of type EXECUTABLE are not supported on this platform
ORA-27371 - jobs of type EXECUTABLE are not supported on this platform

  • ora-16756 : resource guard could not open standby database read-only
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-31162 : element or attribute "string" has no SQLType specified
  • ora-00398 : abort thread recovery due to reconfiguration
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-29827 : keyword USING is missing
  • ora-16225 : Missing LogMiner session name for Streams
  • ora-25191 : cannot reference overflow table of an index-organized table
  • ora-13033 : Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
  • ora-25109 : standby lock name space has illegal character 'string'
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-25963 : join index must be created on tables
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-13860 : Invalid service name
  • ora-14008 : missing THAN keyword
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-30752 : column or table string is not substitutable
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-13293 : cannot specify unit for geometry without a georeferenced SRID
  • ora-01178 : file string created before last CREATE CONTROLFILE, cannot recreate
  • ora-24049 : invalid agent name string, names with AQ$_ prefix are not valid
  • ora-30647 : error retrieving access parameters for external table string.string
  • ora-06763 : TLI Driver: error sending disconnect
  • ora-07418 : sfareq: Database writer got error in timing function.
  • ora-23537 : function or procedure string is not allowed to be invoked from this site.
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-29253 : Invalid count argument passed to procedure dbms_sql.define_array
  • ora-22977 : missing or invalid attribute
  • 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.