Database Reference
In-Depth Information
ERROR at line 1:
ORA-27370: job slave failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:accessing execution agent failed with
status: 2
ORA-27301: OS failure message: The system cannot find the file specified.
ORA-27302: failure occurred at: sjsec 6a
ORA-27303: additional information: The system cannot find the file specified.
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 1
Services Created by the ORADIM Utility
ORADIM is a command line utility for creating Windows services, which implement RDBMS
and ASM instances. In case you have ever taken a close look at the services ORADIM creates,
you may have noticed that it creates two services in Oracle10
g
and subsequent releases. If, for
example, you create an RDBMS instance called TEST as follows:
C:> oradim -new -sid TEST -syspwd secret -startmode manual -srvcstart demand
you will see these two new services:
OracleServiceTEST
OracleJobSchedulerTEST
The service OracleServiceTEST implements the RDBMS instance. Opening the
registry with
regedit.exe
reveals that the service HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\OracleServiceTEST is based on the executable
oracle.exe
. The
service OracleJobSchedulerTEST has status disabled and is implemented by
extjob.exe
. This
service must be started for external jobs owned by database users other than SYS to complete
successfully.
OracleJobScheduler Service
The new service OracleJobScheduler
ORACLE_SID
, where
ORACLE_SID
is the name of an
instance created with
oradim.exe
, is undocumented in Oracle10
g
. It is documented in
Oracle
Database Platform Guide 11g Release 1 for Microsoft Windows
. The Oracle11
g
documentation
points out that the service must be configured to run as a user with low privileges before enabling
it. By default, OracleJobScheduler
ORACLE_SID
is configured to run as user SYSTEM. For security
reasons, this setting must be modified. Otherwise, any database user with enough privileges to
execute external jobs might use operating system authentication to connect as SYS and take
control of databases on the local system. The account used to run OracleJobScheduler
ORACLE_
SID
should not be a member of the groups Administrators or ORA_DBA.
