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:
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
