Académique Documents
Professionnel Documents
Culture Documents
************************************************************************ *****************************************************************************
The default, COMPRESS=y, causes Export to flag table data for consolidation into one initial extent upon import. If extent sizes are large (for example, because of the PCTINCREASE parameter), the allocated space will be larger than the space required to hold the data. If you specify COMPRESS=n, Export uses the current storage parameters, including the values of initial extent size and next extent size. The values of the parameters may be the values specified in the CREATE TABLE or ALTER TABLE statements or the values modified by the database system. For example, the NEXT extent size value may be modified if the table grows and if the PCTINCREASE parameter is nonzero. If we specify COMPRESS=y during export then at the time of table creation while importing, the INITIAL extent of the table would be as large as the sum of all the extents allocated to the table in the original database. If we specify COMPRESS=n during export then while creating table in the import, it will use the same values of INITIAL extent as in the original database.
http://oracleadmins.wordpress.com/2008/08/05/understanding-compress-parameter-in-export/
http://tahiti.oracle.com
**************************************************************************
What is the difference between Traditional Export and Datapump? Datapump operates on a group of files called dump file sets. However, normal export operates on a single file. Datapump access files in the server (using ORACLE directories). Traditional export can access files in client and server both (not using ORACLE directories). exp/imp can utilize the client machine resource for taking the backups but, the datapump works only in server. Exports (exp/imp) represent database metadata information as DDLs in the dump file, but in datapump, it represents in XML document format. Datapump has parallel execution but in exp/imp single stream execution. Table Extent compression can be done using COMPRESS option whereas in datapump COMPRESSION does the dumpfile compression. Datapump has better control than exp/imp on the backup job with START, STOP and RESTART options. Export and import can be taken over the network using database links even without generating the dump file using NETWORK_LINK parameter.
Datapump does not support sequential media like tapes, but traditional export supports.
http://www.acehints.com/2012/02/datapump-vs-expimp-difference-or.html
One way to determine the objects that will or can be exported for the different modes is to look at the three DBA views DATABASE_EXPORT_OBJECTS, SCHEMA_EXPORT_OBJECTS, and TABLE_EXPORT_OBJECTS. Each of these views, if queried, will give you a list and short description on the specific paths to object types that you can expect INCLUDE or EXCLUDE to be dependent on the object you are exporting or importing.
SQL> SELECT object_path, comments FROM table_export_objects where object_path like 'TABLE%';
https://blogs.oracle.com/sysdba/entry/how_to_dump_oracle_data_block
*********************************
http://www.orafaq.com/node/4
On-line Table Redefinition can be used for: o o Add, remove, or rename columns from a table Converting a non-partitioned table to a partitioned table and vice versa
o o o o o
Switching a heap table to an index organized and vice versa Modifying storage parameters Adding or removing parallel support Reorganize (defragmenting) a table Transform data in a table