E1: SCHED: Scheduler Password Gets Corrupted When Changing Parameters For A Scheduled Job. (Doc ID 2952685.1)

Last updated on DECEMBER 26, 2023

Applies to:

Symptoms

Scheduler password gets corrupted after changing other parameters in a scheduled job.

1. Create a E1 scheduler job for any UBE like R0010P.
   1. As a simple test, type in an incorrect password for the Scheduled User first time.
   2. Verify the password field displays an error message.
   3. Correct the password, and then save the new E1 scheduler job.
2. Click "Advanced Options" in "Row Exit" for the new E1 scheduler job just created.
3. Click "Batch Application Override" tab and choose a different "Job Queue".
4. Click "OK".
5. Save the change you made not receiving any error message about the password.
6. Wait until the time the new E1 scheduler job is configured to launch.

The new E1 scheduler job will fail to launch because of the bad password.

jdedebug.log shows:

E1 Scheduler Application should not update the password of Scheduled User, or the Application should warn a user to re-populate the Scheduled Password field again.

Cause

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