Dbms_scheduler Succeeds If Connecting Through Sqlnet, Fails If Connecting Locally
(Doc ID 604641.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]Information in this document applies to any platform.
Symptoms
A Scheduled Job including Operating system commands fails with
ORA-27370: job secondary failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agent failed with status: 13
ORA-27301: OS failure message: Permission denied
ORA-27302: failure occurred at: sjsec 3
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at "SYS.EMAILMSG", line 21
ORA-06512: at line 1
The following test case can be reproduced when the job is owned by SYS schema and it is called by a package under SYS schema.
When the non SYS user runs the package by just doing sqlplus /, it fails (details given below in test case). But when the same user connects through SQLNET by supplying the necessary credentials, it succeeds.
Test Case
$ sqlplus /
SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 28 00:02:11 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> EXEC SYS.Emailmsg('test','imoin@cigna.com','email.sh');
BEGIN SYS.Emailmsg('test','imoin@cigna.com','email.sh'); END;
*
ERROR at line 1:
ORA-27370: job secondary failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agent failed with
status: 13
ORA-27301: OS failure message: Permission denied
ORA-27302: failure occurred at: sjsec 3
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at "SYS.EMAILMSG", line 21
ORA-06512: at line 1
SQL> connect ops$dba_adm@idbarep
Enter password:
Connected.
SQL> EXEC SYS.Emailmsg('test','imoin@cigna.com','email.sh');
PL/SQL procedure successfully completed.
.
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 |
Cause |
Solution |
References |