Different time zones in all_scheduler_job_run_details columns





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I'm currently looking into an issue where an hour time mismatch is reported in a job log report. Querying the all_scheduler_job_run_details for a particular job I get the following results:



select log_date
,actual_start_date
from all_scheduler_job_run_details
where ...

log_date = 03-JAN-19 02.45.11.116000 PM +01:00
actual_start_date = 03-JAN-19 03.45.11.116000 PM +02:00


Note that log_date is with timezone + 1 and actual_start_date is with time_zone + 2.



What would cause these times to be stored with different time_zones in the job_run_detail log?










share|improve this question


















  • 1





    Please provide values for DBMS_SCHEDULER.GET_SCHEDULER_ATTRIBUTE('default_timezone', val), DBMS_SCHEDULER.GET_ATTRIBUTE(job_name, 'follow_default_timezone', bool) and START_DATE

    – Wernfried Domscheit
    Jan 3 at 14:48


















1















I'm currently looking into an issue where an hour time mismatch is reported in a job log report. Querying the all_scheduler_job_run_details for a particular job I get the following results:



select log_date
,actual_start_date
from all_scheduler_job_run_details
where ...

log_date = 03-JAN-19 02.45.11.116000 PM +01:00
actual_start_date = 03-JAN-19 03.45.11.116000 PM +02:00


Note that log_date is with timezone + 1 and actual_start_date is with time_zone + 2.



What would cause these times to be stored with different time_zones in the job_run_detail log?










share|improve this question


















  • 1





    Please provide values for DBMS_SCHEDULER.GET_SCHEDULER_ATTRIBUTE('default_timezone', val), DBMS_SCHEDULER.GET_ATTRIBUTE(job_name, 'follow_default_timezone', bool) and START_DATE

    – Wernfried Domscheit
    Jan 3 at 14:48














1












1








1








I'm currently looking into an issue where an hour time mismatch is reported in a job log report. Querying the all_scheduler_job_run_details for a particular job I get the following results:



select log_date
,actual_start_date
from all_scheduler_job_run_details
where ...

log_date = 03-JAN-19 02.45.11.116000 PM +01:00
actual_start_date = 03-JAN-19 03.45.11.116000 PM +02:00


Note that log_date is with timezone + 1 and actual_start_date is with time_zone + 2.



What would cause these times to be stored with different time_zones in the job_run_detail log?










share|improve this question














I'm currently looking into an issue where an hour time mismatch is reported in a job log report. Querying the all_scheduler_job_run_details for a particular job I get the following results:



select log_date
,actual_start_date
from all_scheduler_job_run_details
where ...

log_date = 03-JAN-19 02.45.11.116000 PM +01:00
actual_start_date = 03-JAN-19 03.45.11.116000 PM +02:00


Note that log_date is with timezone + 1 and actual_start_date is with time_zone + 2.



What would cause these times to be stored with different time_zones in the job_run_detail log?







oracle scheduled-tasks






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 3 at 13:59









ReneRene

8,80242242




8,80242242








  • 1





    Please provide values for DBMS_SCHEDULER.GET_SCHEDULER_ATTRIBUTE('default_timezone', val), DBMS_SCHEDULER.GET_ATTRIBUTE(job_name, 'follow_default_timezone', bool) and START_DATE

    – Wernfried Domscheit
    Jan 3 at 14:48














  • 1





    Please provide values for DBMS_SCHEDULER.GET_SCHEDULER_ATTRIBUTE('default_timezone', val), DBMS_SCHEDULER.GET_ATTRIBUTE(job_name, 'follow_default_timezone', bool) and START_DATE

    – Wernfried Domscheit
    Jan 3 at 14:48








1




1





Please provide values for DBMS_SCHEDULER.GET_SCHEDULER_ATTRIBUTE('default_timezone', val), DBMS_SCHEDULER.GET_ATTRIBUTE(job_name, 'follow_default_timezone', bool) and START_DATE

– Wernfried Domscheit
Jan 3 at 14:48





Please provide values for DBMS_SCHEDULER.GET_SCHEDULER_ATTRIBUTE('default_timezone', val), DBMS_SCHEDULER.GET_ATTRIBUTE(job_name, 'follow_default_timezone', bool) and START_DATE

– Wernfried Domscheit
Jan 3 at 14:48












1 Answer
1






active

oldest

votes


















2














log_date is always in system timezone
actual_start_date is taking the timezone fromstart date if not exist it is taken from scheduler's parameter default_timezone



BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'Test',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN null; END;',
enabled => TRUE,
comments => 'xxx');
END;
/

BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'Test',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN null; END;',
start_date => current_timestamp, -- tz from session
enabled => TRUE,
comments => 'xxx');
END;
/

select * from user_SCHEDULER_JOB_RUN_DETAILS





share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54023773%2fdifferent-time-zones-in-all-scheduler-job-run-details-columns%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    log_date is always in system timezone
    actual_start_date is taking the timezone fromstart date if not exist it is taken from scheduler's parameter default_timezone



    BEGIN
    DBMS_SCHEDULER.CREATE_JOB (
    job_name => 'Test',
    job_type => 'PLSQL_BLOCK',
    job_action => 'BEGIN null; END;',
    enabled => TRUE,
    comments => 'xxx');
    END;
    /

    BEGIN
    DBMS_SCHEDULER.CREATE_JOB (
    job_name => 'Test',
    job_type => 'PLSQL_BLOCK',
    job_action => 'BEGIN null; END;',
    start_date => current_timestamp, -- tz from session
    enabled => TRUE,
    comments => 'xxx');
    END;
    /

    select * from user_SCHEDULER_JOB_RUN_DETAILS





    share|improve this answer




























      2














      log_date is always in system timezone
      actual_start_date is taking the timezone fromstart date if not exist it is taken from scheduler's parameter default_timezone



      BEGIN
      DBMS_SCHEDULER.CREATE_JOB (
      job_name => 'Test',
      job_type => 'PLSQL_BLOCK',
      job_action => 'BEGIN null; END;',
      enabled => TRUE,
      comments => 'xxx');
      END;
      /

      BEGIN
      DBMS_SCHEDULER.CREATE_JOB (
      job_name => 'Test',
      job_type => 'PLSQL_BLOCK',
      job_action => 'BEGIN null; END;',
      start_date => current_timestamp, -- tz from session
      enabled => TRUE,
      comments => 'xxx');
      END;
      /

      select * from user_SCHEDULER_JOB_RUN_DETAILS





      share|improve this answer


























        2












        2








        2







        log_date is always in system timezone
        actual_start_date is taking the timezone fromstart date if not exist it is taken from scheduler's parameter default_timezone



        BEGIN
        DBMS_SCHEDULER.CREATE_JOB (
        job_name => 'Test',
        job_type => 'PLSQL_BLOCK',
        job_action => 'BEGIN null; END;',
        enabled => TRUE,
        comments => 'xxx');
        END;
        /

        BEGIN
        DBMS_SCHEDULER.CREATE_JOB (
        job_name => 'Test',
        job_type => 'PLSQL_BLOCK',
        job_action => 'BEGIN null; END;',
        start_date => current_timestamp, -- tz from session
        enabled => TRUE,
        comments => 'xxx');
        END;
        /

        select * from user_SCHEDULER_JOB_RUN_DETAILS





        share|improve this answer













        log_date is always in system timezone
        actual_start_date is taking the timezone fromstart date if not exist it is taken from scheduler's parameter default_timezone



        BEGIN
        DBMS_SCHEDULER.CREATE_JOB (
        job_name => 'Test',
        job_type => 'PLSQL_BLOCK',
        job_action => 'BEGIN null; END;',
        enabled => TRUE,
        comments => 'xxx');
        END;
        /

        BEGIN
        DBMS_SCHEDULER.CREATE_JOB (
        job_name => 'Test',
        job_type => 'PLSQL_BLOCK',
        job_action => 'BEGIN null; END;',
        start_date => current_timestamp, -- tz from session
        enabled => TRUE,
        comments => 'xxx');
        END;
        /

        select * from user_SCHEDULER_JOB_RUN_DETAILS






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 3 at 15:11









        Arkadiusz ŁukasiewiczArkadiusz Łukasiewicz

        5,0591614




        5,0591614
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54023773%2fdifferent-time-zones-in-all-scheduler-job-run-details-columns%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            The term 'EXEC' is not recognized as the name of a cmdlet Powershell

            NPM command prompt closes immediately [closed]

            Error binding properties and functions in emscripten