PL/SQL (MOSC)

MOSC Banner

DBMS_JOB using dbms_alert.WaitOne in Oracle 19 does not work as expected

edited June 2020 in PL/SQL (MOSC) 5 commentsAnswered ✓

Hi all,

In our product we uses deprecated package DBMS_JOB to submit and run Jobs.

DBMS_JOB runs an expression:

begin package_1.func_1(); end;

package_1.func_1

executes a loop that runs dbms_alert.WaitOne() procedure in the loop. Something like that:

loop

dbms_alert.WaitOne();

end loop;

When I ran the DBMS_JOB on versions prior to 19c it had a message that it had been changed and the execution went to the background.

RDBMS 19c now migrates the DBMS_JOB to DBMS_SCHEDULER objects (creates a copy):

https://mikedietrichde.com/2019/05/24/dbms_job-behavior-change-in-oracle-19c-during-upgrade/

But when in 19c when I run it from old DBMS job or new Scheduler job there is no confirmation message that DBMS Job had been changed. It looks like the execution is hanging on.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center