| Oracle7 Server Utilities User's Guide |  Library |
 Product |
 Contents |
 Index |
| Oracle7 Server Utilities User's Guide | Library |
Product |
Contents |
Index |
This appendix describes changes in the Oracle7 Server utility programs. It covers:
This section describes changes to the Oracle7 Import/Export utility.
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.
These are the changes to Export in Release 7.1.
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 can be exported.
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.
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.
Release 7.1 of the Export/Import utilities supports these new Oracle7 objects:
The new features of Oracle7 export utility are described below.
New objects in Oracle7 (roles, profiles, triggers, stored procedures, and snapshots) can be exported. See page 1 - 6.
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 page 1 - 15.
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 page 1 - 5 for more information.
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 page 1 - 13.
The default for GRANTS export parameter is Y. In Version 6, it was N. See page 1 - 15.
The default for the CONSTRAINTS export parameter is Y. In Version 6, it was N. See page 1 - 14.
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 page 1 - 2.
The Trusted Oracle7 Server parameters MLS and MLS_LABEL_FORMAT have been added. See page 1 - 16.
The new features of Oracle7 Import are described below.
New objects in Oracle7 (roles, profiles, triggers, stored procedures, and snapshots) can be imported. See pages 2 - 9 to 2 - 10.
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 page 2 - 19.
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 page 2 - 23.
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 page 2 - 5 for more information.
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.
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.
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 page 2 - 21.
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 page 2 - 22.
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 page 2 - 12.
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.
The Trusted Oracle7 Server parameter MLS has been added. For details. See page 1 - 16 and page 2 - 23.
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 page 1 - 24.
Similarly, any user who has been granted the IMP_FULL_DATABASE role can perform an incremental import. See page 2 - 29.
This section describes the changes to SQL*Loader and the releases in which they became effective.
As before, the control file must be in the same character set as the session so that the session can interpret it. And, as before, the database character set can be different -- data conversion happens automatically.
In Oracle7, SQL*Loader is part of the standard Oracle Server release. As a result, its release number jumps from "1.1" to "7.0". New features include:
Changes for Direct Path Loads:
Changes in File Management:
Changes in Data Management:
Changes in the Command Line:
In addition, the old syntax
[ STREAM | RECORD | FIXED len [BLOCKSIZE size] | VARIABLE [len] ]
does not affect the way SQL*Loader reads the datafile, although the syntax is recognized to maintain upward compatibility.
Changes in Release 1.0.26:
Changes in Release 1.0.22:
|
Prev Next |
 Copyright © 1996 Oracle Corporation. All Rights Reserved. |
Library |
 Product |
 Contents |
 Index |