+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12

max_dump_file_size for session

  1. Re: max_dump_file_size for session

    On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:

    >what are some other reasons why the dump file would resort back to the
    >init setting?


    Max_dump_file_size is either in a certain range or unlimited.
    You may have exceeded the maximum upper limit.
    I wouldn't bother and set max_dump_file_size to 'unlimited'.

    --
    Sybrand Bakker, Senior Oracle DBA

  2. Re: max_dump_file_size for session

    On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:

    >what are some other reasons why the dump file would resort back to the
    >init setting?


    Max_dump_file_size is either in a certain range or unlimited.
    You may have exceeded the maximum upper limit.
    I wouldn't bother and set max_dump_file_size to 'unlimited'.

    --
    Sybrand Bakker, Senior Oracle DBA

  3. Re: max_dump_file_size for session


    Sybrand Bakker wrote:
    > On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:
    >
    > >what are some other reasons why the dump file would resort back to the
    > >init setting?

    >
    > Max_dump_file_size is either in a certain range or unlimited.
    > You may have exceeded the maximum upper limit.
    > I wouldn't bother and set max_dump_file_size to 'unlimited'.
    >
    > --
    > Sybrand Bakker, Senior Oracle DBA


    Thanks for the reply Sybrand, I saw your reply in a similar post but in
    my case I know that I entered the correct sid, serial#.

    Will that same call work with unlimited if I use quotes?

    so it would be like,

    execute
    dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    'unlimited');


  4. Re: max_dump_file_size for session


    Sybrand Bakker wrote:
    > On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:
    >
    > >what are some other reasons why the dump file would resort back to the
    > >init setting?

    >
    > Max_dump_file_size is either in a certain range or unlimited.
    > You may have exceeded the maximum upper limit.
    > I wouldn't bother and set max_dump_file_size to 'unlimited'.
    >
    > --
    > Sybrand Bakker, Senior Oracle DBA


    Thanks for the reply Sybrand, I saw your reply in a similar post but in
    my case I know that I entered the correct sid, serial#.

    Will that same call work with unlimited if I use quotes?

    so it would be like,

    execute
    dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    'unlimited');


  5. max_dump_file_size for session

    Running 9.2.0.5 Ent Ed, AIX5L
    I ran the following in preparation of tracing a users process but the
    trace stopped with the file size being restricted to the init.ora
    setting of 10000.

    execute
    dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    500000000);

    I would think that maybe i entered the wrong sid, serial# but I used
    the same values for setting the 10046 event and the trace file was
    created.

    execute dbms_system.set_ev(362,42675, 10046, 8, '');

    what are some other reasons why the dump file would resort back to the
    init setting?

    any help is appreciated.


  6. Re: max_dump_file_size for session

    On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:

    >what are some other reasons why the dump file would resort back to the
    >init setting?


    Max_dump_file_size is either in a certain range or unlimited.
    You may have exceeded the maximum upper limit.
    I wouldn't bother and set max_dump_file_size to 'unlimited'.

    --
    Sybrand Bakker, Senior Oracle DBA

  7. Re: max_dump_file_size for session


    Sybrand Bakker wrote:
    > On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:
    >
    > >what are some other reasons why the dump file would resort back to the
    > >init setting?

    >
    > Max_dump_file_size is either in a certain range or unlimited.
    > You may have exceeded the maximum upper limit.
    > I wouldn't bother and set max_dump_file_size to 'unlimited'.
    >
    > --
    > Sybrand Bakker, Senior Oracle DBA


    Thanks for the reply Sybrand, I saw your reply in a similar post but in
    my case I know that I entered the correct sid, serial#.

    Will that same call work with unlimited if I use quotes?

    so it would be like,

    execute
    dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    'unlimited');


  8. Re: max_dump_file_size for session

    On 26 Sep 2006 10:57:13 -0700, "Ben" wrote:

    >
    >Sybrand Bakker wrote:
    >> On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:
    >>
    >> >what are some other reasons why the dump file would resort back to the
    >> >init setting?

    >>
    >> Max_dump_file_size is either in a certain range or unlimited.
    >> You may have exceeded the maximum upper limit.
    >> I wouldn't bother and set max_dump_file_size to 'unlimited'.
    >>
    >> --
    >> Sybrand Bakker, Senior Oracle DBA

    >
    >Thanks for the reply Sybrand, I saw your reply in a similar post but in
    >my case I know that I entered the correct sid, serial#.
    >
    >Will that same call work with unlimited if I use quotes?
    >
    >so it would be like,
    >
    >execute
    >dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    >'unlimited');


    I usually do this using oradebug in sql*plus and don't need to use
    quotes, but one would assume this would work.

    --
    Sybrand Bakker, Senior Oracle DBA

  9. Re: max_dump_file_size for session

    On 26 Sep 2006 10:57:13 -0700, "Ben" wrote:

    >
    >Sybrand Bakker wrote:
    >> On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:
    >>
    >> >what are some other reasons why the dump file would resort back to the
    >> >init setting?

    >>
    >> Max_dump_file_size is either in a certain range or unlimited.
    >> You may have exceeded the maximum upper limit.
    >> I wouldn't bother and set max_dump_file_size to 'unlimited'.
    >>
    >> --
    >> Sybrand Bakker, Senior Oracle DBA

    >
    >Thanks for the reply Sybrand, I saw your reply in a similar post but in
    >my case I know that I entered the correct sid, serial#.
    >
    >Will that same call work with unlimited if I use quotes?
    >
    >so it would be like,
    >
    >execute
    >dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    >'unlimited');


    I usually do this using oradebug in sql*plus and don't need to use
    quotes, but one would assume this would work.

    --
    Sybrand Bakker, Senior Oracle DBA

  10. Re: max_dump_file_size for session

    On 26 Sep 2006 10:57:13 -0700, "Ben" wrote:

    >
    >Sybrand Bakker wrote:
    >> On 26 Sep 2006 10:17:38 -0700, "Ben" wrote:
    >>
    >> >what are some other reasons why the dump file would resort back to the
    >> >init setting?

    >>
    >> Max_dump_file_size is either in a certain range or unlimited.
    >> You may have exceeded the maximum upper limit.
    >> I wouldn't bother and set max_dump_file_size to 'unlimited'.
    >>
    >> --
    >> Sybrand Bakker, Senior Oracle DBA

    >
    >Thanks for the reply Sybrand, I saw your reply in a similar post but in
    >my case I know that I entered the correct sid, serial#.
    >
    >Will that same call work with unlimited if I use quotes?
    >
    >so it would be like,
    >
    >execute
    >dbms_system.set_int_param_in_session(362,42675,'max_dump_file_size' ,
    >'unlimited');


    I usually do this using oradebug in sql*plus and don't need to use
    quotes, but one would assume this would work.

    --
    Sybrand Bakker, Senior Oracle DBA

+ Reply to Thread
Page 1 of 2 1 2 LastLast