This section describes how to use the Export utility, including what you need to do before you begin exporting and how to invoke Export.
Before Using Export
To use Export, you must run the script CATEXP.SQL or CATALOG.SQL (which runs CATEXP.SQL) after the database has been created.
Note: The actual names of the script files depend on your operating system. The script file names and the method for running them are described in your Oracle operating system-specific documentation.
CATEXP.SQL or CATALOG.SQL needs to be run only once on a database. You do not need to run it again before you perform the export. The script performs the following tasks to prepare the database for Export:
Before you run Export, ensure that there is sufficient disk or tape storage space to write the export file. If there is not enough space, Export terminates with a write-failure error.
You can use table sizes to estimate the maximum space needed. Table sizes can be found in the USER_SEGMENTS view of the Oracle data dictionary. The following query displays disk usage for all tables:
select sum(bytes) from user_segments where segment_type=’TABLE’;
The result of the query does not include disk space used for data stored in LOB (large object) or VARRAY columns or partitions.
You can invoke Export in one of the following ways:
exp username/password PARFILE=filename
PARFILE is a file containing the export parameters you typically use. If you use different parameters for different databases, you can have multiple parameter files. This is the recommended method.
Note: The number of parameters cannot exceed the maximum length of a command line on the system.
You can use a combination of the first and second options. That is, you can list parameters both in the parameters file and on the command line. In fact, you can specify the same parameter in both places. The position of the PARFILE parameter and other parameters on the command line determines what parameters override others. For example, assume the parameters file params.dat contains the parameter INDEXES=Y and Export is invoked with the following line:
exp system/manager PARFILE=params.dat INDEXES=N
In this case, because INDEXES=N occurs after PARFILE=params.dat, INDEXES=N overrides the value of the INDEXES parameter in the PARFILE.
You can specify the username and password in the parameter file, although, for security reasons, this is not recommended. If you omit the username/password combination, Export prompts you for it.
Invoking Export As SYSDBA
SYSDBA is used internally and has specialized functions; its behavior is not the same as for generalized users. Therefore, you should not typically need to invoke Export as SYSDBA. However, there may be a few situations in which you need to do so, usually at the request of Oracle technical support.
To invoke Export as SYSDBA, use the following syntax:
Note: Because the string "AS SYSDBA" contains a blank, most operating systems require that entire string ’username/password AS SYSDBA’ be placed in quotation marks or marked as a literal by some method. Some operating systems also require that quotation marks on the command line be preceded by an escape character. Please see your operating system-specific documentation for information about special and reserved characters on your system. If either the username or password is omitted, Export will prompt you for it.
Getting Online Help
Export provides online help. Enter exp help=y on the command line to invoke it.
Export: Release 184.108.40.206.0 - Production on Wed Oct 6 15:23:43 1999
(c) Copyright 1999 Oracle Corporation. 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.
The following keywords only apply to transportable tablespaces TRANSPORT_ TABLESPACE export transportable tablespace metadata (N) TABLESPACES list of tablespaces to transport
Export terminated successfully without warnings.
Specifying Export Parameters on the Command Line or in the Parameter File
You can specify Export parameters in three ways: from a command-line entry, by allowing Export to prompt you for parameter values, or in the parameter file.
Command-Line Parameter Entry
You can specify all valid parameters and their values from the command line using the following syntax:
Export Parameter Prompts
If you prefer to let Export prompt you for the value of each parameter, you can use the following syntax:
Export will display each parameter with a request for you to enter a value.
The Parameter File
The parameter file allows you to specify Export parameters in a file where they can easily be modified or reused. Create the parameter file using any flat file text editor. The command-line option PARFILE=filename tells Export to read the parameters from the specified file rather than from the command line. For example:
exp username/password PARFILE=filename
The syntax for parameter file specifications is one of the following:
The following example shows a partial parameter file listing:
Additional Information: The maximum size of the parameter file may be limited by the operating system. The name of the parameter file is subject to the file naming conventions of the operating system.
You can add comments to the parameter file by preceding them with the pound (#) sign. Export ignores all characters to the right of the pound (#) sign.
Oracle 8i Related Interview Questions
|Oracle 10g Interview Questions||Oracle 9i Interview Questions|
|Oracle 8i Interview Questions||Informatica Interview Questions|
|PL/SQL Interview Questions||Oracle 11g Interview Questions|
|SQL Interview Questions||Oracle apps Interview Questions|
|Sybase Interview Questions||Oracle Apps ERP Interview Questions|
|Oracle 7.3 Interview Questions||Oracle Access Manager Interview Questions|
|Oracle Application Framework Interview Questions||Oracle Apps DBA Interview Questions|
Oracle 8i Related Practice Tests
|Oracle 10g Practice Tests||Oracle 9i Practice Tests|
|Oracle 8i Practice Tests||Informatica Practice Tests|
|PL/SQL Practice Tests||Oracle 11g Practice Tests|
|SQL Practice Tests||Oracle apps Practice Tests|
|Sybase Practice Tests||Oracle Apps ERP Practice Tests|
|Oracle 7.3 Practice Tests|
Oracle 8i Tutorial
Sql*loader Case Studies
Sql*loader Control File Reference
Sql*loader Command-line Reference
Sql*loader: Log File Reference
Sql*loader: Conventional And Direct Path Loads
Dbverify: Offline Database Verification Utility
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.