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 : 24-08-2017

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-01906 : BACKUP keyword expected
  • ora-24061 : cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero
  • ora-19572 : cannot process file string, file is being being resized
  • ora-13338 : failure in reversing LRS polygon/collection geometry
  • ora-13142 : invalid PROXIMITY window definition
  • ora-37028 : (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
  • ora-13780 : SQL statement does not exist.
  • ora-07260 : spdcr: wait error.
  • ora-33068 : (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset.
  • ora-29270 : too many open HTTP requests
  • ora-02822 : Invalid block offset
  • ora-30927 : Unable to complete execution due to failure in temporary table transformation
  • ora-22613 : buflen does not match the size of the scalar
  • ora-06303 : IPA: Message send error
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-13304 : failure to insert a transformed geometry object in a table
  • ora-09925 : Unable to create audit trail file
  • ora-01075 : you are currently logged on
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-12832 : Could not allocate slaves on all specified instances
  • ora-01642 : begin backup not needed for read only tablespace 'string'
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-12819 : missing options in PARALLEL clause
  • ora-19773 : must specify change tracking file name
  • ora-02493 : invalid file increment size in NEXT clause
  • ora-19264 : XQ0044 - invalid namespace in attribute constructors
  • ora-24162 : name value pair list is full, cannot add another entry
  • ora-13121 : layer type type mismatch with topo_geometry layer type
  • 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.