Home » RDBMS Server » Server Utilities » Why did the dump file extracted too large?
Why did the dump file extracted too large? [message #255298] Tue, 31 July 2007 05:35 Go to next message
trantuananh24hg
Messages: 668
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Dear all!

I've exported completely one dump file which contained only the tables, constraints, but without any record from my DB_CAS on machine 1 . Its size is 2MB. Then, I've imported it on the second machine, but its tablespace USER increased, it's too large - 7GB.

The tablespace USER in my machine 1 was 7BG, truthly, but contained records.

I did not understand how the tablespace USER in the second machine was same to this one on machine 1?

How do I resolve it?

Thank you very much!
Re: Why did the dump file extracted too large? [message #255304 is a reply to message #255298] Tue, 31 July 2007 05:49 Go to previous messageGo to next message
Arju
Messages: 1554
Registered: June 2007
Location: Dhaka,Bangladesh. Mobile:...
Senior Member

Did you use full=y parameter to import? If yes then its logical size of tablespace will be same as of database 1.
Re: Why did the dump file extracted too large? [message #255333 is a reply to message #255298] Tue, 31 July 2007 08:20 Go to previous messageGo to next message
joy_division
Messages: 4644
Registered: February 2005
Location: East Coast USA
Senior Member
This is the expected results.
Tables and indexes get created with sizes based upon extents from their source.
If you want them smaller, pre-create the objects with the sizes you want.
Re: Why did the dump file extracted too large? [message #255856 is a reply to message #255298] Thu, 02 August 2007 02:48 Go to previous messageGo to next message
trantuananh24hg
Messages: 668
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Thank you for your reply!

But, I did not chose the option that help=y. I just only wanted to dump my Database with table, indexes, procedure, function and package, without anything else.

How do I invoke the Export Utility?

Thanks!
Re: Why did the dump file extracted too large? [message #255861 is a reply to message #255856] Thu, 02 August 2007 03:05 Go to previous message
Michel Cadot
Messages: 64152
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
C:\>exp help=y

Export: Release 10.2.0.3.0 - Production on Jeu. Aošt 2 10:05:18 2007

Copyright (c) 1982, 2005, Oracle.  All rights reserved.



You can let Export prompt you for parameters by entering the EXP
command followed by your username/password:

     Example: EXP SCOTT/TIGER

Or, you can control how Export runs by entering the EXP command followed
by various arguments. To specify parameters, you use keywords:

     Format:  EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
     Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)
               or TABLES=(T1:P1,T1:P2), if T1 is partitioned table

USERID must be the first parameter on the command line.

Keyword    Description (Default)      Keyword      Description (Default)
--------------------------------------------------------------------------
USERID     username/password          FULL         export entire file (N)
BUFFER     size of data buffer        OWNER        list of owner usernames
FILE       output files (EXPDAT.DMP)  TABLES       list of table names
COMPRESS   import into one extent (Y) RECORDLENGTH length of IO record
GRANTS     export grants (Y)          INCTYPE      incremental export type
INDEXES    export indexes (Y)         RECORD       track incr. export (Y)
DIRECT     direct path (N)            TRIGGERS     export triggers (Y)
LOG        log file of screen output  STATISTICS   analyze objects (ESTIMATE)
ROWS       export data rows (Y)       PARFILE      parameter filename
CONSISTENT cross-table consistency(N) CONSTRAINTS  export constraints (Y)

OBJECT_CONSISTENT    transaction set to read only during object export (N)
FEEDBACK             display progress every x rows (0)
FILESIZE             maximum size of each dump file
FLASHBACK_SCN        SCN used to set session snapshot back to
FLASHBACK_TIME       time used to get the SCN closest to the specified time
QUERY                select clause used to export a subset of a table
RESUMABLE            suspend when a space related error is encountered(N)
RESUMABLE_NAME       text string used to identify resumable statement
RESUMABLE_TIMEOUT    wait time for RESUMABLE
TTS_FULL_CHECK       perform full or partial dependency check for TTS
TABLESPACES          list of tablespaces to export
TRANSPORT_TABLESPACE export transportable tablespace metadata (N)
TEMPLATE             template name which invokes iAS mode export

Export terminated successfully without warnings.

These are all available options.

Regards
Michel

[Updated on: Thu, 02 August 2007 03:06]

Report message to a moderator

Previous Topic: SQL*Loader: constraints and PL/SQL function (merged by LF)
Next Topic: sqlldr and To_date function not working
Goto Forum:
  


Current Time: Sat Dec 10 11:06:39 CST 2016

Total time taken to generate the page: 0.07942 seconds