DBA_JOBS vs DBA_RUNNING_JOBS
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: DBA_JOBS vs DBA_RUNNING_JOBS

  1. #1
    Join Date
    Dec 2001
    Location
    Keene, NH
    Posts
    510
    (Oracle 9i)

    Why on earth would SELECT against dba_jobs return 3 rows and a SELECT against dba_running_jobs return 0 rows?


    More info:

    1. all three jobs are NOT broken (broken=N)
    2. There is no WHERE CLAUSE in both queries!
    3 PFILE:
    # Number of jobs in dba_jobs concurrently + 1
    JOB_QUEUE_PROCESSES=4
    Don't blame me, I'm from Red Sox Nation.

  2. #2
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    running is to check running jobs... if there are no jobs running you don see any rows

  3. #3
    Join Date
    Feb 2001
    Posts
    290
    DBA_JOBS:
    shows all the jobs you have scheduled at different intervals.

    DBA_JOBS_RUNNING
    Just shows the jobs which are running currently..

    so You can get the JOB from dba_job_running and with this Job , you can select WHAT from dba_jobs , which finally what exactly running now...

    try that now !!!!
    Madhu Reddy
    xdollor@yahoo.com

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width