Scheduled Job Running Shell Script Fails With ORA-27369
(Doc ID 391820.1)
Last updated on JULY 23, 2023
Applies to:
Oracle Database - Standard Edition - Version 10.1.0.2 and laterOracle Database - Enterprise Edition - Version 10.1.0.2 and later
Linux x86
Oracle Solaris on SPARC (64-bit)
"ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error" was still occurring for non oracle users running DBMS_SCHEDULER executed shell scripts. Problem was fixed when filesystem where ORACLE_HOME was mounted on was found to have been mounted w/ nosetuid. Changing mount option to setuid resolved problem
***Checked for relevance on 01-Oct-2014***
Checked for Relevance on 27-MAY-2016
Checked for Relevance on 09-Jul-2019
Symptoms
A Scheduler job has been configured using the DBMS_SCHEDULER package. The job executes a shell script using the option job_type=>'EXECUTABLE'. The script performs a write operation to an output file, for example a redirect operation or touch. The write operation fails with:
ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted
Or
ORA-27369: job of type EXECUTABLE failed with exit code: 274662 Or ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error
In dba_scheduler_job_run_details.additional_info, the following details are recorded:
ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted STANDARD_ERROR="touch: cannot touch `<file_name>': Permission denied"
Or
ORA-27369: job of type EXECUTABLE failed with exit code: 274662 STANDARD_ERROR="Oracle Scheduler error: Config file is not owned by root or is writable by group or other or extjob is not setuid and owned by root"
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |