Re: max_dump_file_size for session

On 26 Sep 2006 10:57:13 -0700, "Ben" <balvey_at_comcast.net> wrote:

>
>Sybrand Bakker wrote:
>> On 26 Sep 2006 10:17:38 -0700, "Ben" <balvey_at_comcast.net> 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