DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: job

  1. #1
    Join Date
    Jan 2001
    Posts
    20

    Unhappy

    Hi

    I have a problem with jobs that I schedule to run - they dont seem to be executed at all. How do I check what's gone wrong?

    The process ora_snp0_ is running.

    If I execute the job manually using dbms_job.run(job#) it works fine. This is the job I was talking about:

    SQL> r
    1* select * from user_jobs

    JOB LOG_USER PRIV_USER
    ---------- ------------------------------ ------------------------------
    SCHEMA_USER LAST_DATE LAST_SEC THIS_DATE THIS_SEC NEXT_DATE
    ------------------------------ --------- -------- --------- -------- ---------
    NEXT_SEC TOTAL_TIME B
    -------- ---------- -
    INTERVAL
    --------------------------------------------------------------------------------
    FAILURES
    ----------
    WHAT
    --------------------------------------------------------------------------------
    CURRENT_SESSION_LABEL
    --------------------------------------------------------------------------------
    CLEARANCE_HI
    --------------------------------------------------------------------------------
    CLEARANCE_LO
    --------------------------------------------------------------------------------
    NLS_ENV
    --------------------------------------------------------------------------------
    MISC_ENV
    ----------------------------------------------------------------
    15 REPTEST REPTEST
    REPTEST 13-APR-01 17:42:59 00-DECEMB
    00:00:00 1 N
    sysdate+1/(1440)
    0
    dbms_refresh.refresh('"REPTEST"."RG_REPTEST"');



    NLS_LANGUAGE='AMERICAN' NLS_TERRITORY='AMERICA' NLS_CURRENCY='$' NLS_ISO_CURRENC
    Y='AMERICA' NLS_NUMERIC_CHARACTERS='.,' NLS_DATE_FORMAT='DD-MON-YY' NLS_DATE_LAN
    GUAGE='AMERICAN' NLS_SORT='BINARY'
    0102000200000000

  2. #2
    Join Date
    Nov 2000
    Posts
    245

    your job schedule run every hour, check your init file
    job_queue_interval if should less than hour.

    suggestion, if you are testing replication, make both value
    very small (few seconds) otherwise you have a long long
    test peiord. (impact - watch disk for your archive log files)

  3. #3
    Join Date
    Feb 2001
    Posts
    389
    Check ur alert file if there are any error messages.
    check job_queue_interval..

    I am not able to understand,may be i am reading it wrong , why is your this_date 00-DECEMBER.

  4. #4
    Join Date
    Jan 2001
    Posts
    20
    Hi all

    Now, the jobs in the queue are getting executed after I changed the interval to 5secs. But, I have one more problem. When the job gets executed it gives error -
    ORA-12012: error on auto execute of job 15
    ORA-01001: invalid cursor
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 386
    ORA-06512: at "SYS.DBMS_IREFRESH", line 450
    ORA-06512: at "SYS.DBMS_REFRESH", line 182
    ORA-06512: at line 1

    After it got executed a number of times, the job was marked as BROKEN. Does anyone know why I am getting that invalid cursor problem. It works fine if I do dbms_job.run(15).

    BTW, how many times does a job get executed with error before it is marked as broken?

    Thanks for all the help so far - everyone.

    regards
    Daud

  5. #5
    Join Date
    May 2001
    Location
    Washington DC
    Posts
    3

    16 times and it is broken

    IF the job failures reach 16 then it will become broken.

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