My Oracle Support Banner

ORA-16639 When trying to Stop Jobs Forcefully In RAC Environment,with No OS Process Detected for the Job (Doc ID 2092652.1)

Last updated on MARCH 08, 2022

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


When trying to  Stop Jobs Forcefully In RAC Environment,the below error will be encountered ,

DBMS_SCHEDULER.stop_job (job_name => 'AQ$_PLSQL_NTFN_1438866628');
END; 2 3
4 /
ERROR at line 1:
ORA-16639: specified instance inactive or currently unavailable
ORA-06512: in "SYS.DBMS_ISCHED", line 210
ORA-06512: in "SYS.DBMS_SCHEDULER", line 557
ORA-06512: in line 2

In this case we can kill the job by using its OS process(kill -9 PSID)

But When tried to get the detail of  OS process associated with the job by using the below query,It will show as null (no OS process detected for the job)

SQL> select owner,JOB_NAME,SESSION_ID,RUNNING_INSTANCE,ELAPSED_TIME,CPU_USED from dba_scheduler_running_jobs where JOB_NAME='AQ$_PLSQL_NTFN_1438866628';

JOB_NAME                                     SECONDARY_PROCESS_ID                  SECONDARY_OS_PRO
------------------------------ ---------------- -------------------------------------------------------------


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.