Hi Guys,
We are currently unable to do a full database export as it fails due to dump
file being over 2GB.
Will setting this parameter to unlimited get round the problem?
TIA,
Lisa.
-Original Message-
Sent: 29 October 2003 21:15
To: Multiple recipients of list ORACLE-L
Thanks to
Sorry Lisa,
This doesn't work for export files. Sounds like you are hitting an OS limit.
What are you running Oracle on. You can export to a compressed file via a
UNIX pipe. (if indeed it is UNIX you are running on).
Regards
Lee
-Original Message-
Sent: 30 October 2003 14:39
To:
Lisa,
Have you're SA set the ulimit to unlimited, or you can use the filesize
parameter in export to break the export into several files.
hth
..JIM...
[EMAIL PROTECTED] 10/30/03 8:39:26 AM
Hi Guys,
We are currently unable to do a full database export as it fails due to
dump
file being over
I think if you are having 32 bit Oracle software, this is the limit. There
is a document on Metalink specifying export dump size limits with 32 and 64
bit software. Other listers already suggested you couple of options to
resolve this issue.
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To:
I'm tracing a session with 10046 event level 8. Here's the method I
use:
sys.dbms_system.set_sql_trace_in_session( p_sid, p_serial#, TRUE );
sys.dbms_system.set_bool_param_in_session(p_sid, p_serial#,
'timed_statistics', true);
/* Max dump file size is 2G */
set mdfs=unlimited
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !
-Original
Sounds like an OS limit.
What OS is this on?
Quintin, Richard [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
10/29/2003 10:49 AM
Please respond to ORACLE-L
To:Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:2G trace files
I'm tracing
Set the dump file size to unlimited.
-Original Message-
Sent: Wednesday, October 29, 2003 10:49 AM
To: Multiple recipients of list ORACLE-L
I'm tracing a session with 10046 event level 8. Here's the method I
use:
sys.dbms_system.set_sql_trace_in_session( p_sid, p_serial#, TRUE );
Richard,
Are you sure that you are targeting your diagnostic efforts appropriately?
If all users are using dedicated servers, then each trace file should only have the info for one session. If your interval for a statspack report is an entire week, its going to be pretty tough to find the
If I set max_dump_file_size greater than 2G I get an error.
Perhaps I should be more specific:
sys.dbms_system.set_int_param_in_session(p_sid, p_serial#,
'max_dump_file_size', 'unlimited');
gives:
ORA-06502: PL/SQL: numeric or value error: character to number
conversion error
Yes. I'm tracing a single session. What made you think I wasn't? What
does statspack have to do with this? 2G is not such a large amount...
On Wed, 2003-10-29 at 14:44, Paul Drake wrote:
Richard,
Are you sure that you are targeting your diagnostic efforts
appropriately?
If all
I believe that is a limitation with that procedure.
If you are tracing your own session, use
Alter session set max_dump_file_size=unlimited;
Otherwise set it at the system level during your trace
Alter system set max_dump_file_size=unlimited;
If necessary, reset it after your large trace has
Thanks to everyone who responded. It turns out initialization parameter
max_dump_file_size was set to *20M* and the trace files were getting cut
off at that point.
I didn't look at the ls closely enough and thought it was getting cut
off at 2G. Apparently the init parameter overrides the
13 matches
Mail list logo
