I don't know whether this is a tangent, but I notice that on the windows
platform, compressed exports can still get 85% compression when zipping
them with WinZip.
Obviously Oracle compressed=y doesn't mean compress the export file, it
just means that it places all the segments contiguously in
Patrice - That would be correct. If you run export interactively, the prompt
that is provided is compress extents (y/n).
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Thursday, May 16, 2002 10:08 AM
To: Multiple recipients of list ORACLE-L
I don't know
|
|| |
|+-
|
||
| To: [EMAIL PROTECTED] |
| cc: (bcc: Rachel Carmichael) |
| Subject: RE: Compressing Export Dumps / |
| WinZip
Doesn't it mean that all rows are compressed into 1 extent?
-Original Message-
Sent: Thursday, May 16, 2002 12:08 PM
To: Multiple recipients of list ORACLE-L
Subject:RE: Compressing Export Dumps / WinZip
I don't know whether this is a tangent, but I notice
That's right. compress=y is the export default; it causes all
extents of an object to be combined into one.
--- Boivin, Patrice J [EMAIL PROTECTED] wrote:
I don't know whether this is a tangent, but I notice that on the
windows
platform, compressed exports can still get 85% compression when
The compress=y option doesn't have any effect on how data is stored in the
export dump file, only some of the metadata.
It directs the EXP program to recalculate the DDL for all of the tables and
indexes (instead of just using the settings in the data dictionary) so that
all space previously
Ok is this a joke?? If not, I think someone needs to crack
the Oracle Utilities manual...
RF
-Original Message-
Sent: Thursday, May 16, 2002 11:08 AM
To: Multiple recipients of list ORACLE-L
I don't know whether this is a tangent, but I notice that on the windows
platform,
Subject:RE: Compressing Export Dumps / WinZip
I don't know whether this is a tangent, but I notice that on the windows
platform, compressed exports can still get 85% compression when zipping
them with WinZip.
Obviously Oracle compressed=y doesn't mean compress the export file, it
just means
Large chunks of export files are entirely readable. You can open them in vi
and read it because character data is stored as plain text, hence the
potentially good compression rates.
I agree I wouldn't like to have to decipher a lot of numeric fields.
Regards,
Mike Hately
BTW Robert (Freeman),
Message-
Sent: Thursday, May 16, 2002 12:08 PM
To: Multiple recipients of list ORACLE-L
Subject:RE: Compressing Export Dumps / WinZip
I don't know whether this is a tangent, but I notice that on the windows
platform, compressed exports can still get 85% compression when zipping
them
Tim,
I may be wrong but I thought that compress=y just adds up the total space
allocation from SEG$ rather than calculating them from storage parameters. I
know this is a trivial point but I'd appreciate the info if it sets about
things differently.
regards,
Mike Hately
-Original
Export Dumps / WinZip
I don't know whether this is a tangent, but I notice that on the windows
platform, compressed exports can still get 85% compression when
zipping
them with WinZip.
Obviously Oracle compressed=y doesn't mean compress the export file,
it
just means that it places all the segments
It all depends which words you use -- sorry for the ambiguity...
As Cary replied earlier, EXP just queries sys.seg$ (i.e. DBA_SEGMENTS) to
find the bytes and uses that for the newly-calculated INITIAL. This can be
seen in a SQL Trace initiated on the EXP's server process...
- Original
13 matches
Mail list logo
