My Oracle Support Banner

Scheduler Jobs Fail On Remote Scheduler Agent On Windows With Error 255 (Doc ID 1535765.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Microsoft Windows x64 (64-bit)
Microsoft Windows (32-bit)


When running a remote external Job from a database machine to a remote windows server that has scheduler agent installed, the job fails with the below error:

Job terminated with error number: 255

Below steps to be checked:

1-Ensure that the user who will run the job is granted log on as a batch job and the User Account Controls are turned off.

2-Ensure that not use the Administrator user as the credentials users, it must be another user.

3-Ensure that the installed scheduler agent installed in 64 bit over a 64 bit windows machine.

4-The Windows service (OraClient11g_home1_OracleSchedulerExecutionAgent) was started, and registration with the database was successful.


Patch 12886827 has been applied, but the Job is working for one and need the server to be restarted to run again.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.