Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

Why does the "/q" arguement no longer function in Job Scheduler with Release 21c?

I upgraded from 18c to 21c on a Windows 10 platform.

The following code worked for multiple releases.I use the code below to create a job so that I can have consistency as I promote code from environment to environment.

However, after I upgraded to 21c I realized that the job wasn't firing. After trial-and-error, I discovered that the /q argument (Quiet) was preventing the Windows command job from working like it used to.

PROCEDURE proc_job_weekly_backup IS
 BEGIN
   dbms_scheduler.create_job 
   (
     job_name             => 'job_weekly_backup',
     job_type             => 'EXECUTABLE',
     job_action           => 'C:\Windows\System32\cmd.exe',
     number_of_arguments  => 3, 
     start_date           => sysdate,
     repeat_interval      => 'freq=weekly; byday=sun; byhour=17; byminute=00; bysecond=0;', 
     end_date             => NULL,
     enabled              => FALSE,
     auto_drop            => FALSE,
     comments             => 'Perform Weekly Backup'
   );
   dbms_scheduler.set_job_argument_value('job_weekly_backup', 1, 'C:\SS_Library_Backups\LibraryBackup.cmd');
   dbms_scheduler.set_job_argument_value('job_weekly_backup', 2, '/q'); --Echo Off
   dbms_scheduler.set_job_argument_value('job_weekly_backup', 3, '/c'); --Run Command and then terminate
 END proc_job_weekly_backup;
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

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