Oracle Database Export (exp) import (IMP) Description _oracle

Buffer: Download data buffer, in bytes, default dependent on operating system
Consistent: The data involved during the download remains read only, and the default is n
Direct: Using Passthrough method, the default is n
Feeback: Displays the number of processing records, the default is 0, which is not displayed
File: Output files, defaults to Expdat.dmp
FileSize: Output file size, default to operating system maximum value
Indexes: Whether to download the index, the default is N, which refers to the definition of the index rather than the data, exp does not load the index data
Log:log file, default to None, display in standard output
Owner: Indicates the user name of the download
Query: Select a subset of records
Rows: Whether to download table records
Tables: List of output table names
Export an entire instance
Exp dbuser/oracle file=oradb.dmp log=oradb.log full=y consistent=y direct=y
User should have DBA authority
Export all objects for a user
Exp dbuser/oracle file=dbuser.dmp log=dbuser.log owner=dbuser buffer=4096000 feedback=10000
Export one or more tables
Exp dbuser/oracle file=dbuser.dmp log=dbuser.log tables=table1,table2 buffer=4096000 feedback=10000
Export some data from a table
Exp dbuser/oracle file=dbuser.dmp log=dbuser.log tables=table1 buffer=4096000 feedback=10000 "where query=\" ... \ and col2 \<...\ "
Not available for nested tables
Export a table in multiple fixed size files
Exp dbuser/oracle file=1.dmp,2.dmp,3.dmp,... filesize=1000m tables=emp buffer=4096000 feedback=10000
This practice is typically used when a single dump file may exceed the file system limit for a large amount of table data
Passthrough path mode
Direct=y, replace the buffer option, the query option is not available
Help to improve download speed
Consistent options
Since export startup, consistent=y freezes the update of the data object from other sessions to the export operation, which guarantees the consistency of the dump results. However, this process cannot be too long so that the rollback segment and the online log are exhausted
Imp
Upload the dmp file for exp download to the database.
Buffer: Upload data buffer, in bytes, default dependent on operating system
Commit: Whether the commit is performed after the record in the upload data buffer is uploaded
Feeback: Displays the number of processing records, the default is 0, which is not displayed
File: Input files, defaults to Expdat.dmp
FileSize: Input file size, defaults to operating system maximum value
Fromuser: Indicates the source user side
Ignore: Whether to ignore object creation errors, the default is N, the object has been established before uploading is often a normal phenomenon, so this option is recommended to Y
Indexes: Whether to upload the index, the default is N, which refers to the definition of the index rather than the data, if the index was established when uploading, and even if it is N, IMP automatically updates the index data
Log:log file, default to None, display in standard output
Rows: Whether to upload table records
Tables: List of table names entered
Touser: Specify the destination user side
Import an entire instance
Imp dbuser/oracle file=oradb.dmp log=oradb.log full=y buffer=4096000 commit=y ignore=y feedback=10000
Import all objects for a user
Imp dbuser/oracle file=dbuser.dmp log=dbuser.log fromuser=dbuser touser=dbuser2 buffer=2048000 commit=y ignore=y feedback=10000
Import one or several tables
Imp dbuser2/oracle file=user.dmp log=user.log tables=table1,table2 fromuser=dbuser touser=dbuser2 buffer=2048000 Commit=y Ignore=y feedback=10000
Import a table in more than one fixed size file
Imp dbuser/oracle file=\ (1.dmp,2.dmp,3.dmp,... \) filesize=1000m tables=emp fromuser=dbuser touser=dbuser2 buffer= 4096000 commit=y ignore=y feedback=10000