Re: Overriding default max_dump_file_size
- From: "zhu chao" <chao_ping@xxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 4 May 2004 08:53:48 +0800
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 -----
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
> message, but the trace
> file size will always max out at the database default of 5M.
> EXEC sys.dbms_system.set_int_param_in_session (&&sid, &&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
-----------------------------------------------------------------
Other related posts:
