Oracle7 Server Utilities
Export/Import Changes
This section describes changes to the Oracle7 Import/Export utility.
Release 7.2 Changes
These are the changes to Export in Release 7.2.
FEEDBACK parameter added to Import/Export to display an onscreen progress meter during imports and exports.
Release 7.1 Changes
These are the changes to Export in Release 7.1.
Change in Export File Format
In Release 7.1, the export file format was changed to accommodate stored procedures, functions, and packages that have comments embedded among the creation-statement keywords. In some cases, a patch is required to successfully migrate these code objects between a Release 7.0 database and a Release 7.1 database.
Read-Only Tablespaces
Read-only tablespaces can be exported.
Trusted Oracle Label Mapping
Trusted Oracle7 Import allows you to list the labels in the export file and specify a mapping that converts them into the labels used by the target Trusted Oracle7 database. For details, see the Trusted Oracle7 Server Administrator's Guide.
Version Incompatibility Error Message
When a higher level version of the Export utility is used with a lower level version of the Oracle7 Server with which it is incompatible, an EXP-37 error results.
New 7.1 Objects Supported
Release 7.1 of the Export/Import utilities supports these new Oracle7 objects:
Changes in Export for Release 7.0
The new features of Oracle7 export utility are described below.
Oracle7 Objects
New objects in Oracle7 (roles, profiles, triggers, stored procedures, and snapshots) can be exported. See ![[*]](jump.gif)
.
Log Files
Log files are supported in Oracle7. Systems that do not support I/O redirection can have a record of errors and warnings that occur during the export. See .
Final Message
In Version 6, any export that completed displayed the message "Export completed successfully". In Oracle7, export ends with one of three messages:
Export terminated successfully without warnings
Export terminated successfully with warnings
Export terminated unsuccessfully
See for more information.
CONSISTENT
The Oracle7 parameter CONSISTENT allows the creation of read-consistent exports. A read-consistent export is guaranteed not to include any partially completed transactions. It is used when exports and database updates must occur simultaneously. See .
GRANTS=Y
The default for GRANTS export parameter is Y. In Version 6, it was N. See .
CONSTRAINTS=Y
The default for the CONSTRAINTS export parameter is Y. In Version 6, it was N. See 1 - 14.
Setting Up Export Views
In Oracle7, the script EXPVEW.SQL must be run after CATALOG.SQL to establish the export views. In Version 6, the order made no difference. See .
Trusted Oracle7 Server Parameters
The Trusted Oracle7 Server parameters MLS and MLS_LABEL_FORMAT have been added. See .
Changes in Import for Release 7.0
The new features of Oracle7 Import are described below.
Oracle7 Objects
New objects in Oracle7 (roles, profiles, triggers, stored procedures, and snapshots) can be imported. See on pages 2 - 9 to 2 - 10.
DESTROY Parameter
The ALTER TABLESPACE statement stored in the Oracle7 export file sets REUSE=NO so that the default action on import is not to reuse the datafiles defined for the database. In Version 6, the default was REUSE=YES. This change minimizes the chance that a database can be inadvertently replaced when attempting to create a copy of it for testing or other purposes. This change resulted from the fact that the full pathname of datafiles in the database is included in the export file.
A new import parameter allows you to specify DESTROY=YES, instructing Import to erase the existing datafiles and reuse them. This option allows you to re-create your database from backups, when necessary. The default value for DESTROY is NO. See .
Log Files
Log files are supported in Oracle7 so that systems that do not support I/O redirection can have a record of errors and warnings that occur during the import. See .
Final Message
In Version 6, any import that completed displayed the message "Import completed successfully". In Oracle7, import ends with one of three messages:
Import terminated successfully without warnings
Import terminated successfully with warnings
Import terminated unsuccessfully
See for more information.
User Definitions
In Version 6, user definitions did not exist separately from their GRANTS. User definitions were therefore imported by importing GRANT statements. In Oracle7, importing a user definition does not automatically grant connect access.
Importing Objects for Other Users
Version 6 import adopted the target user's privileges when importing objects. If the user did not have CREATE TABLE privilege, for example, a DBA might find that a user's tables could not be imported--although the DBA had successfully exported them.
Oracle Import uses the importer's privileges to import objects into another user's schema. This method preserves the importer's privileges, allowing a fully privileged user to import objects for a limited-privilege user.
IGNORE=N
In Oracle7, the default is to report all object creation errors. Previously they were ignored by default. To suppress the reporting of error messages that occur when tables and other objects already exist, specify IGNORE=Y. See .
INDEXFILE Parameter
The Oracle7 parameter INDEXFILE makes it possible to siphon off index-creation statements, so they are placed in a file instead of being applied to the database. This procedure is more efficient and makes it possible to change index storage attributes. See .
Character Set Conversion
In Version 6, Import/Export provided a limited capability to convert data between ASCII-based and EBCDIC-based systems. In Oracle7, that capacity has been extended to translate data between two systems using different character encoding schemes. See .
CHARSET parameter
In Version 6, the CHARSET parameter was used in limited ways to control the conversion from the character set used in the export file to the database character set. In Oracle7, the Export file records the character set used when the file was created. Oracle Import then automatically converts that character set to the database character set.
In Oracle7, this parameter only checks that the Export file's character set matches the expected value. Use of the CHARSET parameter is no longer recommended as it will eventually become obsolete.
Trusted Oracle7 Server Parameter
The Trusted Oracle7 Server parameter MLS has been added. For details. See and .
Incremental Import and Export
In Oracle7, an incremental import or export can be performed by any user who has been granted the EXP_FULL_DATABASE role. Previously, only SYS or SYSTEM could do an incremental import or export. See .
Similarly, any user who has been granted the IMP_FULL_DATABASE role can perform an incremental import. See .