RE: Overriding default max_dump_file_size
- From: "Poras, Henry R." <Henry_Poras@xxxxxxxxxxxxxxxx>
- To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 4 May 2004 09:58:47 -0400
Jeff,
I remember having a similar problem on an AIX system. I tried unlimited, put in
a max #, but couldn't get the dump file above the default. I ended up changing
jobs before I could track down the problem. (I'm pretty sure this was on 8.1.7).
Maybe a bug???
Henry
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Thomas Jeff
Sent: Tuesday, May 04, 2004 9:42 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Overriding default max_dump_file_size
Thanks for the reply -- but it still does not work. Only alter
system set will work, something
I hate to do.
The script is like this (bummed from Tim Gorman/Cary M):
UNDEF sid
UNDEF serial
ACCEPT sid NUMBER prompt 'Enter SID of process to trace: '
ACCEPT serial NUMBER prompt 'Enter Serial# of process to trace: '
EXEC sys.dbms_system.set_int_param_in_session (&&sid, &&serial,
'max_dump_file_size', 1073741824);
EXEC sys.dbms_system.set_ev(&&sid, &&serial, 10046, 12, '');
SELECT RTRIM(c.value,'/') || '/' || LOWER(d.instance_name) || '_ora_' ||
to_char(a.spid,'fm00000000') || '.trc' "Trace File Name"
FROM v$process a,
v$session b,
v$parameter c,
v$instance d
WHERE a.addr =3D b.paddr
AND b.audsid =3D sys_context('userenv', 'sessionid')
AND c.name =3D 'user_dump_dest'; =20
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of zhu chao
Sent: Monday, May 03, 2004 7:54 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Overriding default max_dump_file_size
Hi,
Just try to Change it to MAX_DUMP_FILE_SIZE and maybe it works.
I tested it on solaris/8174.
Another point, in one long running SQL, you changed the init
parameter using dbms_system, it won't change. You have to wait for the
session doing other SQL so that the change take effect. Regards Zhu
Chao.
----- Original Message -----=20
From: "Thomas Jeff" <jeff.thomas@xxxxxxxxxxx>
To: <oracle-l@xxxxxxxxxxxxx>
Sent: Tuesday, May 04, 2004 8:22 AM
Subject: Overriding default max_dump_file_size
> Any ideas why the following does not work? I don't get an error=20
> message, but the trace file size will always max out at the database=20
> default of 5M. EXEC sys.dbms_system.set_int_param_in_session (&&sid,=20
> &&serial, 'max_dump_file_size', 1073741824);
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put
'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
