DBMS_SCHEDULER logging level oddity - why?

I am trying to establish with new database 11 g to migrate across our 10 g databases, and I noticed that dbms_scheduler jobs have a logging_level of "RUNS" on 10 g but, despite being created with the same code, on 11 g the logging_level is 'OFF '. I've checked everything I can think of, but I do not understand why the recording level is different on 11g.

Here is my test scenario:

< h3 > 10g < / h3 >
select version
from   v$instance;

VERSION          
-----------------
10.2.0.4.0     

select job_class_name, logging_level
from   dba_scheduler_job_classes
where  job_class_name = 'DEFAULT_JOB_CLASS';

JOB_CLASS_NAME                 LOGGING_LEVEL
------------------------------ -------------
DEFAULT_JOB_CLASS              RUNS           

select dbms_scheduler.get_default_value('LOGGING_LEVEL') from dual;

DBMS_SCHEDULER.GET_DEFAULT_VALUE('LOGGING_LEVEL')                               
--------------------------------------------------------------------------------
64             

declare
  db_name varchar2(2);
begin
   dbms_scheduler.create_job( 
    job_name=>'test_job', 
    job_type => 'PLSQL_BLOCK',
    job_action=> 'begin 
  null;
end; ', 
  start_date => to_timestamp('01/16/2013 12:00:00', 'mm/dd/yyyy hh24:mi:ss'), 
  repeat_interval => 'SYSDATE + 12/24', 
  enabled => true, auto_drop=> false, 
  comments => 'test'
);
end;
/

select job_name, job_type, job_class, logging_level
from   user_scheduler_jobs
where  job_name = 'TEST_JOB';

JOB_NAME                       JOB_TYPE         JOB_CLASS                      LOGGING_LEVEL
------------------------------ ---------------- ------------------------------ -------------
TEST_JOB                       PLSQL_BLOCK      DEFAULT_JOB_CLASS              RUNS
< h3 > 11g < / h3 >
select version
from   v$instance;

VERSION          
-----------------
11.2.0.3.0  

select job_class_name, logging_level
from   dba_scheduler_job_classes
where  job_class_name = 'DEFAULT_JOB_CLASS';

JOB_CLASS_NAME                 LOGGING_LEVEL
------------------------------ -------------
DEFAULT_JOB_CLASS              RUNS        

select dbms_scheduler.get_default_value('LOGGING_LEVEL') from dual;

DBMS_SCHEDULER.GET_DEFAULT_VALUE('LOGGING_LEVEL')                               
--------------------------------------------------------------------------------
64           

declare
  db_name varchar2(2);
begin
   dbms_scheduler.create_job( 
    job_name=>'test_job', 
    job_type => 'PLSQL_BLOCK',
    job_action=> 'begin 
  null;
end; ', 
  start_date => to_timestamp('01/16/2013 12:00:00', 'mm/dd/yyyy hh24:mi:ss'), 
  repeat_interval => 'SYSDATE + 12/24', 
  enabled => true, auto_drop=> false, 
  comments => 'test'
);
end;
/

select job_name, job_style, job_type, job_class, logging_level
from   user_scheduler_jobs
where  job_name = 'TEST_JOB';

JOB_NAME                       JOB_STYLE   JOB_TYPE         JOB_CLASS                      LOGGING_LEVEL
------------------------------ ----------- ---------------- ------------------------------ -------------
TEST_JOB                       REGULAR     PLSQL_BLOCK      DEFAULT_JOB_CLASS              OFF
Someone at - it ideas as to what could be causing the logging level will be set to OFF on the 11 g database? I know that I can adjust the recording manually via the SET_ATTRIBUTE procedure level, but nothing I have google/read in the documentation explains why the level is not set on WORKS on 11g.

Am I missing something completely obvious?

Hi D,

I think that's probably a bug... When you create a task, oracle is the insertion of the 164400 in the sys.scheduler table $_job. And looking at his decoding, which is

DECODE (BITAND (j.flags, 32 + 64 + 128 + 256),  32, 'OFF',  64, 'RUNS',  128, 'FAILED RUNS',  256, 'FULL',  NULL)

which gives 32, so that it displays as OFF.

Based on the track, I think that it does not have the sys.scheduler logging level $_class when inserting new jobs. I suspect that this is a bug.

Hope everything goes well
Raj J

Tags: Database

Similar Questions

  • X7.2 VCS log levels - changed?

    Before the upgrade to x7.2 I could define the log levels ranging from 1 (least verbose) to (more detailed) 4, where "4"would give me all the details of calls - which is what I need - that after the x7.2 all I get is the equivalent of '1' - which is not very helpful at all.

    I missed something - or is this a bug?

    Edit: looks like it's a bug, so guess I'll be downgraded to x7.1

    Bravo jens

    Hi Jens,

    I reproduced it and lifted a bug. Once it finds its way in to CDETS I'll make the number available. I also had a brief discussion for developers on this subject.

    Thank you

    Guy

  • Re: Log level and Cache

    Hi Experts,

    Usually in the production, here there is no newspaper survey but for a report, I want to set the logging level to back-end application and I want to make this report to hit DB instead of hitting cache how do I do this together

    When I kept it like this SET VARIABLE LOGLEVEL = 5; SET VARIABLE DISABLE_CACHE_HIT = 1; It displays odbc error.

    How to achieve this please think.

    Kind regards

    SET LOGLEVEL VARIABLE = 5, DISABLE_CACHE_HIT = 1;


    Pls mark if it is correct.

  • SFTP Log levels

    See in the error logs... Is there a way to change the logging level as to where this won't keep fill newspapers?

    < failed validation of FTP adapter TEST_ProcessOutbFile SFTP Channel >

    = Safety =.

    = This system is restricted to authorized Oracle users.      =

    = Unauthorized access may lead to disciplinary action and/or =

    = of civil or criminal sanctions. To the extent permitted by law =

    = use of this system may be monitored in accordance with the =

    is the terms of Oracle's Acceptable use policy.            =

    = Safety =.

    < 23 June 2014 2:45:53 PM CDT > < opinion > < Stdout > < BEA-000000 > < please log in with the user ID and password.

    = Security Notice =.

    = This system is restrictive! Ted to Oracle authorized users.      =

    = Unauthorized access may lead to disciplinary action and/or =

    = civil or criminal sanctions. To the extent permitted by law =

    = use of this system may be monitored in accordance with the =

    is the terms of Oracle's Acceptable use policy.            =

    = Security Notice =.

    Please sign in with the user ID and password.

    = Security Notice =.

    = & nb! SP;   This system is restricted to authorized Oracle users.      =

    = Unauthorized access may lead to disciplinary action and/or =

    = civ! He or penal sanctions. To the extent permitted by law =

    = use of this system may be monitored in accordance with the =

    is the terms of Oracle's Acceptable use policy.            =

    What version of the SOA Suite do you use? Can you give us more excerpts from the log file, say 20-30 more lines on each side?

    With the prefix

    It would seem that messages arrive via stdout, which is probably (sshtools) mavericks of third party library we use for SFTP.

  • When I try to install Lr CC (2nd install, a laptop) the procedure goes into an infinite loop: log / level, level/sign in, etc. Actually, it does not download.

    When I try to install Lr CC (2nd install, a laptop) the procedure goes into an infinite loop: log / level, level/sign in screens, etc. Actually, it does not download.

    I have no problems with the first installation on a desktop.

    You can download at the bottom of the link:

    https://helpx.Adobe.com/Lightroom/KB/Lightroom-downloads.html

    If you had purchased a subscription, you will need to install via Adobe Creative Cloud app.

  • Disable the logging level for individual users

    Hello

    We want to stop individual users to record level. Usually, we go to identity and click on the user to set the log level '0', but we have LDAP security settings don't so have no idea how to do.

    All ideas

    Thxs

    SYK

    LDAP?

    Still, you can see the RPD users when

    IM-> Action-> Set Online user filter specific user

  • Log level obiee 11g for application roles

    Hi Experts,

    It is possible to activate the logging level for an entire application role? For example, I have 20 + users who are a BIAdministrator and rather than allowing the log for each user level (such as additional users will be added/removed to the BIAdministrator role) is it possible to activate the journal of leveling for the application BIAdministrator role?
    All of the documentation I read points to 'no '. It seems that the only options are:


    1) activate at the level of the newspaper for the BISystemUser through the tab manage repository in the RPD
    (2) check the log level in the reports by prefixing
    (3) grant rights log level to individual users

    Looks like you can't turn on the logging level at nqsconfig or at the level of the application role. anyone could do this?

    Thank you

    Create a new init block to validate the specific role to set the number of loglevel to what you want.
    ex: case when role = then else 2 0 end
    and use LOGLEVEL in the variable section.

    Score pls help if

  • THE LOG LEVEL

    Hello world

    I use authentication external table. But we do not get table logging level.
    (Initially we plan keep the same level of newspaper (2) for all).
    My question is how can I get log level value (2) in a session variable.
    I tried to write 2 Select double and give the default value 2. But no luck...

    Please some can help me on this issue?
    Thanks in advance

    Hello

    Have you tried to select in the 'SYSIBM. SYSDUMMY1 ' table? It seems that SYSIBM. SYSDUMMY1 is the equivalent of "DUAL" of DB2. 2. SELECT which OF SYSIBM. SYSDUMMY1

    -Joe

  • The ODI log level

    Hello

    I'm looking for a description of the levels of Log ODI.
    I know that the logging level controls the details of the log in operator ODI output, but that there is more detailed documentation?
    I need information such as what the details are displayed in what newspaper level.

    Thanks in advance!

    See you soon,.
    H.

    Hello

    There are five levels of monitoring:
    1 shows the beginning and the end of each session
    2 poster level 1 and the beginning and the end of each stage
    3. display of level 2 and each task performed
    4 shows the executed, SQL queries as well as level 4
    5. a full, often requested trace during a support call

    Thank you
    Fati

  • Operator of ODI log - level

    Hello

    What is the importance of the logging level in operator ODI. I have worked in ODI, but did not notice this time... .to default sound always * 5 *...
    how it will affect the details of newspapers if there is a change in the level +/- newspaper.

    What is the highest level of log in operator ODI.

    Thank you

    SG

    Hi SG.

    The default logging for the operator level is 5.
    This is the highest level of logging available in ODI.

    That you give all the steps involved in your interface/package/procedure etc.
    If you decrease the level of logging information in the operator will also decrease.

    Thank you
    Fati

  • the 0-7 syslog logging level

    Hello Sir,

    I want to set up a syslog server and switches will send the log file to the analyst syslog server.

    Please Veuileez share with me level 0 (emergency) to level 7 (debug mode).

    What level I put only then can trace changes of username and user on the switch configuration?

    or any configuration which able to follow it and send to syslog server?

    Hello

    Would the following that you are looking to have something?

    http://www.Cisco.com/en/us/docs/iOS/12_3t/12_3t4/feature/guide/gtconlog.html

  • Query sorting based on log level

    Hello.  I have a query like this:

    SELECT DISTINCT

    LOAD_PROF2,

    V_TIME,

    SUBSTATION_CODE,

    CIRCUIT_CODE,

    PROFILE_DAY,

    DECODE (UPPER (PROFILE_DAY),

    'MONDAY', 1,

    "TUESDAY", 2.

    'WEDNESDAY', 3.

    'THURSDAY', 4,.

    'FRIDAY', 5.

    'SATURDAY', 6,.

    "SUNDAY", 7,.

    'HOLIDAY', 8,

    "H_THURSDAY", 9,.

    ("H_FRIDAY", 10)

    ORDERBY

    OF LOAD_PROFILE_TEST

    WHERE SUBSTATION_CODE = V_SUBSTATION_CODE

    AND CIRCUIT_CODE = V_CIRCUIT_CODE

    AND SUPERIOR (PROFILE_DAY) IN (SELECT (TOP)

    TO_CHAR)

    T_DATE + (LEVEL - 1).

    "fmDAY'))

    OF THE DOUBLE

    CONNECT BY LEVEL < =.

    V_DATE_IN - T_DATE + 1).

    ORDER BY ORDERBY, V_TIME;

    If I use T_DATE like 10/10/2013 and V_DATE_IN as the 13/10/2013, I get output that is sorted based on ORDERBY (that I created), which will be

    Thursday, Friday, Saturday and Sunday.  However, when I use the 19/10/2013 as my V_DATE_IN, I get a result sorted as Monday, Tuesday... Sunday.  How can I sort it so that the first day where seems must be the day of my T_DATE, in this case, if I use the 10/10/2013 as my T_DATE and 19/10/2013 as V_DATE_IN, I should get an output sorted as Thursday, Friday... Wednesday.

    What should I replace my ORDERBY to achieve this kind of sorting?  Thank you

    Can you check if this query is what you wanted and meets your expectations. ??

    Not TESTED on my side...

    ----------------------------------------

    SELECT LOAD_PROF2,

    V_TIME,

    SUBSTATION_CODE,

    CIRCUIT_CODE,

    PROFILE_DAY

    LOAD_PROFILE_TEST a.,

    (SELECT T_DATE + (LEVEL - 1) dt, UPPER (TO_CHAR (T_DATE + (LEVEL - 1), 'fmDAY')) days)

    OF THE DOUBLE

    CONNECT BY LEVEL<= v_date_in="" -="" v_date="" +="" 1)="">

    WHERE SUBSTATION_CODE = V_SUBSTATION_CODE

    AND CIRCUIT_CODE = V_CIRCUIT_CODE

    AND SUPERIOR (a.PROFILE_DAY) = b.days

    LOAD_PROF2 GROUP,

    V_TIME,

    SUBSTATION_CODE,

    CIRCUIT_CODE,

    PROFILE_DAY

    ORDER BY b.dt, v_time;

    -------------------------------------------

    See you soon,.

    Manik.

  • Substitution of xml for logging configuration

    What I had initially tried to set the logging has been the addition of the following to the options - Dtangosol.coherence.cluster = contact-cluster - config.xml in start-cache - server.cmd

    This is my contact-cluster-config. XML

    <>cluster-config
    < cluster name > ContactCacheTesting < / cluster-name >
    < / cluster-config >
    <>logging-config
    < destination > X:\Oracle\CoherenceLogs\coherence.log < / destination >
    > < 9 severity level < / severity level >
    < message format > (thread = {thread}): {text} < / message format >
    > limit of < 8192 characters < / character limit >
    < / operational forest-config >

    I realized my config.xml file - contact-cluster was loaded at startup, but recording was not working.

    I found myself with logging server-side going by adding the following options of start-cache - server.cmd and it worked
    -Dtangosol.coherence.log=X:\Oracle\CoherenceLogs\coherence.log-Dtangosol.coherence.log.level=9

    Why my solution of the xml file did not work. Should I have a fundamental misunderstanding of the substitutions of xml?

    I am able to make substitutions to help xml - Dtangosol.coherence.cacheconfig = contact-cache - config.xml very well well.

    Hi sideout.

    Your override should look like this:

    
    
        
            ContactCacheTesting
        
    
    
        X:\Oracle\CoherenceLogs\coherence.log
        9
        8192

    Kind regards
    Dimitri

  • How to increase the level of logging of trace 32 SAW in OBIEE by EM?

    Hello

    can someone explain to me how to increase the level of logging of trace 32 SAW in OBIEE by EM?

    When I went to the newspapers of diagnostics > change newspapers to Finest... Activate the changes, it asks me to restart the services. After restart of the log levels are back to regular level that's information.

    Any help is appreciated.

    Thank you

    Vincent

    Check it cool - bi.com

  • Why not lemutri scopes show levels greater than 100 or less than 0?

    I got a call back of the Department on the airwaves, but the scopes in the first show all levels within 0 to 100, even cut. I have the video limiter effect and the effect of an adjustment layer levels, but when they receive it the video is over 100 and 0. When I do this in final cut pro, it shows out of reach of broadcast safe levels. Why aren't the expanses of lemutri showing me this? Am I missing something?

    As Jeff says... but here's a trick.

    Do not use the video limiter (or broadcasting) effect.

    Only apply effect LEVELS for the adjustment layer.

    This will automatically fix Luma, but I tend to drop at 250ish white as well. Check it by activating / deactivating it on and outside.)

    If your Chroma is hot... Use the parameter to whatever color of the drop.  Generally, red is the culprit...

    My stuff never fails QC issue with that.

Maybe you are looking for