"Translated from MoS article" job does not work on its own initiative

Workarounds that the job cannot actively run on its own

References:
Jobs do not execute automatically (Doc ID 309945.1)


Suitable for:
Oracle server-enterprise edition-version:9.2.0.4
This problem can occur on any platform.


Symptoms:
The Job cannot be run on its own initiative.

Job_queue_processes has been set to a value greater than 0

You have checked the value of the SGA variable kkjsre, which is 0

Examples:

Sql> CONN sys/*********** as SYSDBA
Connected.
Sql> Oradebug Setmypid
Statement processed.
sql> oradebug Dumpvar SGA kkjsre
Word kkjsre_ [20b7480, 20b7484) = 00000000

Reason:

For the job to be self-executing, the SGA variable kkjsre must be 1

Canceling the process being shutdown (canceling a shutdown in progress) is one reason for this variable value of 0.

How to resolve:

1) Log in with Sys

2) Run the following command:

Sql> exec dbms_ijob.set_enabled (true);

3) Verify that the Kkjsre is set to 1

Sql> Oradebug Setmypid
Statement processed.
sql> oradebug Dumpvar SGA kkjsre
Word kkjsre_ [20b7480, 20b7484) = 00000001


4) Confirm that the job starts itself.

If not, restart the db. And check the value of Kkjsre again, the value should be 1, and the job should be able to do it on its own initiative.

"Translated from MoS article" job does not work on its own initiative