Importacion
Necesito exportar una base que esta en oracle 8.1.7 e importarla desde un personal oracle 7. ¿Se puede?¿Cómo?
Muchas gracias.
Muchas gracias.
1 respuesta
Respuesta de caim
1
1
Según mi conocimiento, esto debe evaluarse cuidadosamente, pero teóricamente es aplicable. Te adjunto tabla de compatibilidad para los efectos. Revísala y cuéntame como te va.
Saludos,
CAIM.
¿De dónde eres?
Bookmark Fixed font Go to End
Doc ID: Note:132904.1
Subject: Compatibility Matrix for Export & Import Between Different Oracle Versions
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 19-JAN-2001
Last Revision Date: 12-MAY-2003
PURPOSE ------- This article describes several issues related with the compatibility of the different versions of the Oracle EXPORT and IMPORT utilities. SCOPE & APPLICATION ------------------- The article is intended for users of the Oracle7, Oracle8, Oracle8i and Oracle9i databases who wish to use the EXPORT and IMPORT utilities to export data from an Oracle database release x and importing this data into an Oracle database release y. The article gives information which version of the utility to use when performing the export and import, and how to prepare the Oracle data dictionary before exporting the data. SUMMARY ------- 1. Export the data with the Export utility of the lowest database version involved. 2. Import the data with the Import utility of the target database. 3. Running an Oracle7 Export utility against an Oracle9i database is not supported. COMPATIBILITY MATRIX FOR EXPORT & IMPORT BETWEEN DIFFERENT ORACLE VERSIONS -------------------------------------------------------------------------- Introduction. ------------- With the Oracle EXPORT and IMPORT utilities you can transfer data objects between Oracle databases, even if they reside on platforms with different hardware and software configurations. The Oracle EXPORT utility extracts the object definitions and table data from an Oracle database and stores them in an Oracle binary-format export dump file located typically on disk or tape. The files can then be transferred using FTP or physically transported (in the case of tape) to a different site. When transferring the export dump file over a network, the file has to be transmitted in binary mode. Transmitting export files in character mode (ASCII) causes errors when the file is imported, resulting most likely in: IMP-9 or IMP-10, followed by IMP-0. The Oracle IMPORT utility reads the object definitions and table data from the export dump file and then inserts the information into the Oracle database. Data Dictionary Views. ---------------------- Before using the EXPORT or IMPORT utility, the Data Dictionary has to be prepared with the views that are needed by these utilities. This can be done by running the script: UNIX : SQL> @$ORACLE_HOME/rdbms/admin/catexp.sql Windows: SQL> @%ORACLE_HOME%\rdbms\admin\catexp.sql This script CATEXP.SQL has to be run by the user SYS. The script is called automatically by the CATALOG.SQL script. Both scripts CATEXP.SQL and CATALOG.SQL need to be run only once on a database. Normally, you never need to run it again before you perform an export or import (the errors EXP-24 or IMP-23 indicate that the views are not correct anymore). The script CATEXP.SQL performs the following tasks to prepare the database for an export and/or import: - create the required export and import views in the data dictionary; - create the EXP_FULL_DATABASE role and the IMP_FULL_DATABASE role; - assign all necessary privileges to the EXP_FULL_DATABASE role and the IMP_FULL_DATABASE role; - assign EXP_FULL_DATABASE and IMP_FULL_DATABASE to the DBA role; - update table sys.props$ with the version of the export and import views (see the notes at the end of the article). When creating an Oracle7 export file from an Oracle8/8i database by running the Oracle7 EXPORT utility against the Oracle8/8i server (see details below), the user SYS must have run the CATEXP7.SQL script on the Oracle8/8i database: UNIX : SQL> @$ORACLE_HOME/rdbms/admin/catexp7.sql Windows: SQL> @%ORACLE_HOME%\rdbms\admin\catexp7.sql This script creates the export views that make the database look, to EXPORT, like an Oracle7 release database. This means that the views will not see any new Oracle8/8i specific objects, so the export file can be imported without problems in the Oracle7 database. Keep in mind that both the scripts CATEXP.SQL and CATEXP7.SQL only need to be run once: CATEXP.SQL creates the exu8% views which are used by the Oracle8/8i/9i EXPORT utilities, and CATEXP7.SQL creates the exu7% views which are used by the Oracle7 EXPORT utilities. So if both scripts have been run by SYS, you do not need to run them again. The procedure mentioned above, also applies for creating an Oracle6 export dump file from an Oracle7 database. In this case the user SYS must have run the CATEXP6.SQL script on the Oracle7 database. Note that running an Oracle7 Export utility against Oracle9i database is not supported: in a downgrade scenario, we only support one functional release back. Basic Compatibility. -------------------- Definition Source database = the database where the data is exported from. Definition Target database = the database where the data is imported into. 1) Always use a version of the EXPORT utility that is equal to the lowest version of either the source or the target database. This means: a) When creating an export dump file for an import into a higher release database (e.g.: from Oracle8i to Oracle9i), use a version of the EXPORT utility that is equal to the version of the source database (= lowest version = Oracle8i in this case). The export fails if you use a higher release export version. For example, if you use the export 9.0.1 utility the export data from an 8.1.7 database, you will get the errors: EXP-56 Oracle error 942 encountered ORA-942 table or view does not exist EXP-0 Export terminated unsuccessfully Solution: use the lowest release export utility (8.1.7 in this case). b) When creating an export dump file for an import into a lower release database (e.g.: from Oracle9i to Oracle8i), use a version of the EXPORT utility that is equal to the version of the target database (= lowest version = Oracle8i in this case). (1) When creating an Oracle6 export file from an Oracle7 database by running the Oracle6 EXPORT utility against the Oracle7 server, the user SYS must first run the CATEXP6.SQL script on the Oracle7 database. This script creates the export views that make the database look, to EXPORT, like an Oracle6 release database. (2) When creating an Oracle7 export file from an Oracle8/8i database by running the Oracle7 EXPORT utility against the Oracle8/8i server, the user SYS must first run the CATEXP7.SQL script on the Oracle8/8i database. This script creates the export views that make the database look, to EXPORT, like an Oracle7 release database. (3) When creating an Oracle8/8i export file from an Oracle9i database by running the Oracle8/8i EXPORT utility against the Oracle9i server, you do not have to take any special steps. I.e., you do not need to run the 8i version of catexp.sql against the 9i database. You only need to run the 8i exp executable against the 9i database. Be aware that several Oracle9i specific features are not supported/exported (e.g. no LOBs and objects are exported when using DIRECT=YES). See the "Oracle9i Database Utilities" manual for a complete list of these restrictions). 2) Always use a version of the IMPORT utility that is equal to the version of the target database. Limitations. ------------ The following limitations apply to the EXPORT and IMPORT utilities (see details in the matrix below): 1. Oracle export dump files can only be read by the Oracle IMPORT utility because these dump files are stored in a special Oracle-binary format. 2. Every export dump file is importable into all future major, patch, and maintenance releases of Oracle. 3. The export dump files cannot be read by IMPORT utilities of previous maintenance releases and versions. So, a version 9 export dump file cannot be imported by a version 8i IMPORT utility (possible errors: IMP-10 and IMP-21), and a version 8 export dump file cannot be imported by a version 7 IMPORT utility (possible errors: IMP-69 and IMP-21). In both cases, the import will terminate with the error IMP-0 "Import terminated unsuccessfully". 4. IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version). 5. IMPORT cannot read export dump files created by the EXPORT utility of a higher maintenance releases or versions. So, a release 8.1 export dump file cannot be imported by a release 8.0 IMPORT utility, and a version 8 export dump file cannot be imported by a version 7 IMPORT utility. 6. The Oracle6 (or earlier) EXPORT utility cannot be used against an Oracle8 or Oracle8i or higher release database. 7. Whenever a lower version EXPORT utility runs with a higher version of the Oracle Server, any categories of database objects that did not exist in the lower version are excluded from the export. For example, partitioned tables are not exported by the version 7 EXPORT utility. If you need to move a version 8 partitioned table to a version 7 database, then first reorganize the table into a non-partitioned table. Matrix 1: Which EXPORT utility to use when importing into an Oracle7 or a lower database release (always use IMPORT utility of the target database): +----------+-----------------------------------------------------+ | EXPORT | IMPORT into: | | from +--------+--------+--------+--------+--------+--------+ | \/ | 5.x | 6.x | 7.0.x | 7.1.x | 7.2.x | 7.3.x | +----------+--------+--------+--------+--------+--------+--------+ | 5.x 1) 2)| EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | | 6.x 2)| N/S | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | +----------+--------+--------+--------+--------+--------+--------+ | 7.0.x 3)| N/S | EXP6x | EXP70x | EXP70x | EXP70x | EXP70x | | 7.1.x 3)| N/S | EXP6x | EXP70x | EXP71x | EXP71x | EXP71x | | 7.2.x 3)| N/S | EXP6x | EXP70x | EXP71x | EXP72x | EXP72x | | 7.3.x 3)| N/S | EXP6x | EXP70x | EXP71x | EXP72x | EXP73x | +----------+--------+--------+--------+--------+--------+--------+ | 8.0.x 4)| not supported | EXP70x | EXP71x | EXP72x | EXP73x | | 8.1.x 4)| not supported | EXP70x | EXP71x | EXP72x | EXP73x | +----------+--------+--------+--------+--------+--------+--------+ | 9.0.x | not supported | | 9.2.x | not supported | +----------+-----------------------------------------------------+ Remarks: 1) IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version). 2) An Oracle5 or Oracle6 export dump and an Oracle7 IMPORT: see the Oracle Utilities Manual, Chapter 2 "Import" for special considerations to keep in mind. 3) To export from Oracle7 into an Oracle6 database: user SYS must run script CATEXP6.SQL on the Oracle7 database first (this script needs to be run only once in order to have the version6 views been created). 4) To export from Oracle8, Oracle8i into an Oracle7 database: user SYS must run script CATEXP7.SQL on the Oracle8/8i/9i database first (this script needs to be run only once in order to create the version7 views). Matrix 2: Which EXPORT utility to use when importing into an Oracle8 or a higher database release (always use IMPORT utility of the target database): +----------+--------------------------------------------------------------+ | EXPORT | IMPORT into: | | from +--------+--------+--------+--------+--------+--------+--------+ | \/ | 8.0.5 | 8.0.6 | 8.1.5 | 8.1.6 | 8.1.7 | 9.0.1 | 9.2.0 | +----------+--------+--------+--------+--------+--------+--------+--------+ | 5.x 1) 2)| EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | | 6.x 2)| EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | | 7.x 3)| EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | +----------+--------+--------+--------+--------+--------+--------+--------+ | 8.0.4 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | | 8.0.5 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | | 8.0.6 | EXP805 | EXP806 | EXP806 | EXP806 | EXP806 | EXP806 | EXP806 | +----------+--------+--------+--------+--------+--------+--------+--------+ | 8.1.5 | EXP805 | EXP806 | EXP815 | EXP815 | EXP815 | EXP815 | EXP815 | | 8.1.6 | EXP805 | EXP806 | EXP815 | EXP816 | EXP816 | EXP816 | EXP816 | | 8.1.7 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP817 | EXP817 | +----------+--------+--------+--------+--------+--------+--------+--------+ | 9.0.1 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP901 | EXP901 | | 9.2.0 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP901 | EXP920 | +----------+--------+--------+--------+--------+--------+--------+--------+ Remarks: 1) IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version). 2) An Oracle5 or Oracle6 export dump and an Oracle8 or Oracle8i or Oracle9i IMPORT: see the Oracle Utilities Manual, Chapter 2 "Import" for special considerations to keep in mind. 3) An Oracle7 export dump and an Oracle8 or Oracle8i or Oracle9i IMPORT: constraints on the DATE columns become invalid when TO_DATE function has not been used in the constraint (this was not required in earlier Oracle versions). Examples. --------- 1. From 7.3.3 to 8.1.6 => Use the EXPORT 7.3.3 to export the data from the 7.3.3 database and IMPORT 8.1.6 to import the data into the 8.1.6 database. 2. From 8.1.6 to 8.1.6 => Use the EXPORT 8.1.6 to export the data from the 8.1.6 database and IMPORT 8.1.6 to import the data into the 8.1.6 database. 3. From 8.1.5 to 8.0.6 => Use the EXPORT 8.0.6 to export the data from the 8.1.5 database and IMPORT 8.0.6 to import the data into the 8.0.6 database. 4. From 9.0.1 to 8.1.7 => Use the EXPORT 8.1.7 to export the data from the 9.0.1 database and IMPORT 8.1.7 to import the data into the 8.1.7 database. 5. From 8.1.7 to 9.2.0 => Use the EXPORT 8.1.7 to export the data from the 8.1.7 database and IMPORT 9.2.0 to import the data into the 9.2.0 database. 6. From 9.0.1 to 9.2.0 => Use the EXPORT 9.0.1 to export the data from the 9.0.1 database and IMPORT 9.2.0 to import the data into the 9.2.0 database. 7. From 8.1.7 to 7.3.4 => Only if never run before, first run CATEXP7.SQL on the 8.1.7 database in order to create the Oracle7 data dictionary views; then use the EXPORT 7.3.4 to export the data from the 8.1.7 database and IMPORT 7.3.4 to import the data into the 7.3.4 database. 8. From 9.0.1 to 7.3.4 => Not supported. Possible error messages. ------------------------ EXP-24 : Export views not installed, please notify your DBA Cause : The necessary export views were not installed. Action : Ask the database administrator to install the required export views. IMP-23 : Import views not installed, please notify your DBA Cause : Import views not installed. Action : Notify DBA to install import views. EXP-37 : Export views not compatible with database version Cause : The EXPORT utility is at a higher version than the database version and is thereby incompatible. Action : Use the same version of EXPORT utility as the database. IMP-9 : Abnormal end of export file Cause : This is usually caused by an export file generated by an aborted export session. Action : Check if file was transferred in Binary-mode. If the export file was generated by an aborted export session, retry the export followed by the import, else report this as an Import bug. IMP-10 : Not a valid export file, header failed verification Cause : Either it is not a file generated by the Export utility or that the file is corrupted. Action : Check if file was transferred in Binary-mode. If the file was indeed generated by the Export utility, and no compatibility issue is related, report this as an Import bug. IMP-21 : operating system error - error code (dec %lu, hex 0x%X) Cause : Operating system error. Can occur together with IMP-10 or IMP-69. Action : Check the OS manual for the error code and take appropriate action. Check for compatibility issues when next errors are IMP-10 or IMP-69. IMP-69 : Could not convert to environment national character set's handle Cause : Internal error. Action : Contact Worldwide support. IMP-0 : Import terminated unsuccessfully Cause : Error encountered. Action : Check the preceding error message and take appropriate actions. Notes. ------ 1. To use EXPORT, you must have the CREATE SESSION privilege on an Oracle database. To export tables owned by another user, you must have the EXP_FULL_DATABASE role enabled. This role is granted to all DBAs. 2. To use an older EXPORT release on a newer database release, you have to use SQL*Net or Net8 to access this database: EXP <username>/<password>@<instance_alias> ... 3. When using an older EXPORT release on a newer database release, you have to use the default CONVENTIONAL path export (i.e.: do not specify DIRECT=YES in the export command statement). A conventional path export uses the SQL SELECT statement to extract data from tables. A direct path export reads the data directly, bypassing the SQL Command Processing layer (evaluating buffer). 4. In order to check the revision of the export and import views, you can query the table sys.props$ with the following statement: SQL> SELECT * FROM sys.props$ WHERE name LIKE 'EXPORT%'; NAME VALUE$ COMMENT$ ------------------------- ----------- ------------------------ EXPORT_VIEWS_VERSION 8 Export views revision # The value of the property EXPORT_VIEWS_VERSION has the following meaning: +-------------------------------+ | EXPORT_VIEWS_VERSION | +-------+-----------------------+ | Value | Introduced in Release | +-------+-----------------------+ | *)| 7.0.* | *) no compatibility - assume zero | 1 | 7.1.3 | | 2 | 7.2.1 | | 3 | 7.2.3 | | 4 | 8.0.1 | | 5 | 8.0.2 | | 6 | 8.0.3 | | 7 | 8.0.4 | | 8 | 8.1.6 | +-------+-----------------------+ RELATED DOCUMENTS ----------------- [NOTE:61949.1] Overview of Export and Import in Oracle7 [NOTE:76542.1] NT: Exporting from Oracle8, Importing Into Oracle7 [NOTE:1012189.6] Errors trying to Import Transferred Export File [NOTE:155477.1] Parameter DIRECT: Conventional Path Export Versus Direct Path A32541-01 "Oracle7 Server Utilities Release 7.3", Chapter 1 "Export" and Chapter 2 "Import". A58244-01 "Oracle8 Utilities Release 8.0", Chapter 1 "Export" and Chapter 2 "Import". A76955-01 "Oracle8i Utilities Release 2 (8.1.6)", Chapter 1 "Export" and Chapter 2 "Import". A90192-01 "Oracle9i Database Utilities Release 1 (9.0.1)", Chapter 1 "Export" and Chapter 2 "Import". A96652-01 "Oracle9i Database Utilities Release 2 (9.2)", Chapter 1 "Export" and Chapter 2 "Import". A86632-01 "Oracle8i Migration Release 3 (8.1.7)", Chapter 9 "Compatibility".
.
--------------------------------------------------------------------------------
Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
Saludos,
CAIM.
¿De dónde eres?
Bookmark Fixed font Go to End
Doc ID: Note:132904.1
Subject: Compatibility Matrix for Export & Import Between Different Oracle Versions
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 19-JAN-2001
Last Revision Date: 12-MAY-2003
PURPOSE ------- This article describes several issues related with the compatibility of the different versions of the Oracle EXPORT and IMPORT utilities. SCOPE & APPLICATION ------------------- The article is intended for users of the Oracle7, Oracle8, Oracle8i and Oracle9i databases who wish to use the EXPORT and IMPORT utilities to export data from an Oracle database release x and importing this data into an Oracle database release y. The article gives information which version of the utility to use when performing the export and import, and how to prepare the Oracle data dictionary before exporting the data. SUMMARY ------- 1. Export the data with the Export utility of the lowest database version involved. 2. Import the data with the Import utility of the target database. 3. Running an Oracle7 Export utility against an Oracle9i database is not supported. COMPATIBILITY MATRIX FOR EXPORT & IMPORT BETWEEN DIFFERENT ORACLE VERSIONS -------------------------------------------------------------------------- Introduction. ------------- With the Oracle EXPORT and IMPORT utilities you can transfer data objects between Oracle databases, even if they reside on platforms with different hardware and software configurations. The Oracle EXPORT utility extracts the object definitions and table data from an Oracle database and stores them in an Oracle binary-format export dump file located typically on disk or tape. The files can then be transferred using FTP or physically transported (in the case of tape) to a different site. When transferring the export dump file over a network, the file has to be transmitted in binary mode. Transmitting export files in character mode (ASCII) causes errors when the file is imported, resulting most likely in: IMP-9 or IMP-10, followed by IMP-0. The Oracle IMPORT utility reads the object definitions and table data from the export dump file and then inserts the information into the Oracle database. Data Dictionary Views. ---------------------- Before using the EXPORT or IMPORT utility, the Data Dictionary has to be prepared with the views that are needed by these utilities. This can be done by running the script: UNIX : SQL> @$ORACLE_HOME/rdbms/admin/catexp.sql Windows: SQL> @%ORACLE_HOME%\rdbms\admin\catexp.sql This script CATEXP.SQL has to be run by the user SYS. The script is called automatically by the CATALOG.SQL script. Both scripts CATEXP.SQL and CATALOG.SQL need to be run only once on a database. Normally, you never need to run it again before you perform an export or import (the errors EXP-24 or IMP-23 indicate that the views are not correct anymore). The script CATEXP.SQL performs the following tasks to prepare the database for an export and/or import: - create the required export and import views in the data dictionary; - create the EXP_FULL_DATABASE role and the IMP_FULL_DATABASE role; - assign all necessary privileges to the EXP_FULL_DATABASE role and the IMP_FULL_DATABASE role; - assign EXP_FULL_DATABASE and IMP_FULL_DATABASE to the DBA role; - update table sys.props$ with the version of the export and import views (see the notes at the end of the article). When creating an Oracle7 export file from an Oracle8/8i database by running the Oracle7 EXPORT utility against the Oracle8/8i server (see details below), the user SYS must have run the CATEXP7.SQL script on the Oracle8/8i database: UNIX : SQL> @$ORACLE_HOME/rdbms/admin/catexp7.sql Windows: SQL> @%ORACLE_HOME%\rdbms\admin\catexp7.sql This script creates the export views that make the database look, to EXPORT, like an Oracle7 release database. This means that the views will not see any new Oracle8/8i specific objects, so the export file can be imported without problems in the Oracle7 database. Keep in mind that both the scripts CATEXP.SQL and CATEXP7.SQL only need to be run once: CATEXP.SQL creates the exu8% views which are used by the Oracle8/8i/9i EXPORT utilities, and CATEXP7.SQL creates the exu7% views which are used by the Oracle7 EXPORT utilities. So if both scripts have been run by SYS, you do not need to run them again. The procedure mentioned above, also applies for creating an Oracle6 export dump file from an Oracle7 database. In this case the user SYS must have run the CATEXP6.SQL script on the Oracle7 database. Note that running an Oracle7 Export utility against Oracle9i database is not supported: in a downgrade scenario, we only support one functional release back. Basic Compatibility. -------------------- Definition Source database = the database where the data is exported from. Definition Target database = the database where the data is imported into. 1) Always use a version of the EXPORT utility that is equal to the lowest version of either the source or the target database. This means: a) When creating an export dump file for an import into a higher release database (e.g.: from Oracle8i to Oracle9i), use a version of the EXPORT utility that is equal to the version of the source database (= lowest version = Oracle8i in this case). The export fails if you use a higher release export version. For example, if you use the export 9.0.1 utility the export data from an 8.1.7 database, you will get the errors: EXP-56 Oracle error 942 encountered ORA-942 table or view does not exist EXP-0 Export terminated unsuccessfully Solution: use the lowest release export utility (8.1.7 in this case). b) When creating an export dump file for an import into a lower release database (e.g.: from Oracle9i to Oracle8i), use a version of the EXPORT utility that is equal to the version of the target database (= lowest version = Oracle8i in this case). (1) When creating an Oracle6 export file from an Oracle7 database by running the Oracle6 EXPORT utility against the Oracle7 server, the user SYS must first run the CATEXP6.SQL script on the Oracle7 database. This script creates the export views that make the database look, to EXPORT, like an Oracle6 release database. (2) When creating an Oracle7 export file from an Oracle8/8i database by running the Oracle7 EXPORT utility against the Oracle8/8i server, the user SYS must first run the CATEXP7.SQL script on the Oracle8/8i database. This script creates the export views that make the database look, to EXPORT, like an Oracle7 release database. (3) When creating an Oracle8/8i export file from an Oracle9i database by running the Oracle8/8i EXPORT utility against the Oracle9i server, you do not have to take any special steps. I.e., you do not need to run the 8i version of catexp.sql against the 9i database. You only need to run the 8i exp executable against the 9i database. Be aware that several Oracle9i specific features are not supported/exported (e.g. no LOBs and objects are exported when using DIRECT=YES). See the "Oracle9i Database Utilities" manual for a complete list of these restrictions). 2) Always use a version of the IMPORT utility that is equal to the version of the target database. Limitations. ------------ The following limitations apply to the EXPORT and IMPORT utilities (see details in the matrix below): 1. Oracle export dump files can only be read by the Oracle IMPORT utility because these dump files are stored in a special Oracle-binary format. 2. Every export dump file is importable into all future major, patch, and maintenance releases of Oracle. 3. The export dump files cannot be read by IMPORT utilities of previous maintenance releases and versions. So, a version 9 export dump file cannot be imported by a version 8i IMPORT utility (possible errors: IMP-10 and IMP-21), and a version 8 export dump file cannot be imported by a version 7 IMPORT utility (possible errors: IMP-69 and IMP-21). In both cases, the import will terminate with the error IMP-0 "Import terminated unsuccessfully". 4. IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version). 5. IMPORT cannot read export dump files created by the EXPORT utility of a higher maintenance releases or versions. So, a release 8.1 export dump file cannot be imported by a release 8.0 IMPORT utility, and a version 8 export dump file cannot be imported by a version 7 IMPORT utility. 6. The Oracle6 (or earlier) EXPORT utility cannot be used against an Oracle8 or Oracle8i or higher release database. 7. Whenever a lower version EXPORT utility runs with a higher version of the Oracle Server, any categories of database objects that did not exist in the lower version are excluded from the export. For example, partitioned tables are not exported by the version 7 EXPORT utility. If you need to move a version 8 partitioned table to a version 7 database, then first reorganize the table into a non-partitioned table. Matrix 1: Which EXPORT utility to use when importing into an Oracle7 or a lower database release (always use IMPORT utility of the target database): +----------+-----------------------------------------------------+ | EXPORT | IMPORT into: | | from +--------+--------+--------+--------+--------+--------+ | \/ | 5.x | 6.x | 7.0.x | 7.1.x | 7.2.x | 7.3.x | +----------+--------+--------+--------+--------+--------+--------+ | 5.x 1) 2)| EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | | 6.x 2)| N/S | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | +----------+--------+--------+--------+--------+--------+--------+ | 7.0.x 3)| N/S | EXP6x | EXP70x | EXP70x | EXP70x | EXP70x | | 7.1.x 3)| N/S | EXP6x | EXP70x | EXP71x | EXP71x | EXP71x | | 7.2.x 3)| N/S | EXP6x | EXP70x | EXP71x | EXP72x | EXP72x | | 7.3.x 3)| N/S | EXP6x | EXP70x | EXP71x | EXP72x | EXP73x | +----------+--------+--------+--------+--------+--------+--------+ | 8.0.x 4)| not supported | EXP70x | EXP71x | EXP72x | EXP73x | | 8.1.x 4)| not supported | EXP70x | EXP71x | EXP72x | EXP73x | +----------+--------+--------+--------+--------+--------+--------+ | 9.0.x | not supported | | 9.2.x | not supported | +----------+-----------------------------------------------------+ Remarks: 1) IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version). 2) An Oracle5 or Oracle6 export dump and an Oracle7 IMPORT: see the Oracle Utilities Manual, Chapter 2 "Import" for special considerations to keep in mind. 3) To export from Oracle7 into an Oracle6 database: user SYS must run script CATEXP6.SQL on the Oracle7 database first (this script needs to be run only once in order to have the version6 views been created). 4) To export from Oracle8, Oracle8i into an Oracle7 database: user SYS must run script CATEXP7.SQL on the Oracle8/8i/9i database first (this script needs to be run only once in order to create the version7 views). Matrix 2: Which EXPORT utility to use when importing into an Oracle8 or a higher database release (always use IMPORT utility of the target database): +----------+--------------------------------------------------------------+ | EXPORT | IMPORT into: | | from +--------+--------+--------+--------+--------+--------+--------+ | \/ | 8.0.5 | 8.0.6 | 8.1.5 | 8.1.6 | 8.1.7 | 9.0.1 | 9.2.0 | +----------+--------+--------+--------+--------+--------+--------+--------+ | 5.x 1) 2)| EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | | 6.x 2)| EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | | 7.x 3)| EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | +----------+--------+--------+--------+--------+--------+--------+--------+ | 8.0.4 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | | 8.0.5 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | | 8.0.6 | EXP805 | EXP806 | EXP806 | EXP806 | EXP806 | EXP806 | EXP806 | +----------+--------+--------+--------+--------+--------+--------+--------+ | 8.1.5 | EXP805 | EXP806 | EXP815 | EXP815 | EXP815 | EXP815 | EXP815 | | 8.1.6 | EXP805 | EXP806 | EXP815 | EXP816 | EXP816 | EXP816 | EXP816 | | 8.1.7 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP817 | EXP817 | +----------+--------+--------+--------+--------+--------+--------+--------+ | 9.0.1 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP901 | EXP901 | | 9.2.0 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP901 | EXP920 | +----------+--------+--------+--------+--------+--------+--------+--------+ Remarks: 1) IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version). 2) An Oracle5 or Oracle6 export dump and an Oracle8 or Oracle8i or Oracle9i IMPORT: see the Oracle Utilities Manual, Chapter 2 "Import" for special considerations to keep in mind. 3) An Oracle7 export dump and an Oracle8 or Oracle8i or Oracle9i IMPORT: constraints on the DATE columns become invalid when TO_DATE function has not been used in the constraint (this was not required in earlier Oracle versions). Examples. --------- 1. From 7.3.3 to 8.1.6 => Use the EXPORT 7.3.3 to export the data from the 7.3.3 database and IMPORT 8.1.6 to import the data into the 8.1.6 database. 2. From 8.1.6 to 8.1.6 => Use the EXPORT 8.1.6 to export the data from the 8.1.6 database and IMPORT 8.1.6 to import the data into the 8.1.6 database. 3. From 8.1.5 to 8.0.6 => Use the EXPORT 8.0.6 to export the data from the 8.1.5 database and IMPORT 8.0.6 to import the data into the 8.0.6 database. 4. From 9.0.1 to 8.1.7 => Use the EXPORT 8.1.7 to export the data from the 9.0.1 database and IMPORT 8.1.7 to import the data into the 8.1.7 database. 5. From 8.1.7 to 9.2.0 => Use the EXPORT 8.1.7 to export the data from the 8.1.7 database and IMPORT 9.2.0 to import the data into the 9.2.0 database. 6. From 9.0.1 to 9.2.0 => Use the EXPORT 9.0.1 to export the data from the 9.0.1 database and IMPORT 9.2.0 to import the data into the 9.2.0 database. 7. From 8.1.7 to 7.3.4 => Only if never run before, first run CATEXP7.SQL on the 8.1.7 database in order to create the Oracle7 data dictionary views; then use the EXPORT 7.3.4 to export the data from the 8.1.7 database and IMPORT 7.3.4 to import the data into the 7.3.4 database. 8. From 9.0.1 to 7.3.4 => Not supported. Possible error messages. ------------------------ EXP-24 : Export views not installed, please notify your DBA Cause : The necessary export views were not installed. Action : Ask the database administrator to install the required export views. IMP-23 : Import views not installed, please notify your DBA Cause : Import views not installed. Action : Notify DBA to install import views. EXP-37 : Export views not compatible with database version Cause : The EXPORT utility is at a higher version than the database version and is thereby incompatible. Action : Use the same version of EXPORT utility as the database. IMP-9 : Abnormal end of export file Cause : This is usually caused by an export file generated by an aborted export session. Action : Check if file was transferred in Binary-mode. If the export file was generated by an aborted export session, retry the export followed by the import, else report this as an Import bug. IMP-10 : Not a valid export file, header failed verification Cause : Either it is not a file generated by the Export utility or that the file is corrupted. Action : Check if file was transferred in Binary-mode. If the file was indeed generated by the Export utility, and no compatibility issue is related, report this as an Import bug. IMP-21 : operating system error - error code (dec %lu, hex 0x%X) Cause : Operating system error. Can occur together with IMP-10 or IMP-69. Action : Check the OS manual for the error code and take appropriate action. Check for compatibility issues when next errors are IMP-10 or IMP-69. IMP-69 : Could not convert to environment national character set's handle Cause : Internal error. Action : Contact Worldwide support. IMP-0 : Import terminated unsuccessfully Cause : Error encountered. Action : Check the preceding error message and take appropriate actions. Notes. ------ 1. To use EXPORT, you must have the CREATE SESSION privilege on an Oracle database. To export tables owned by another user, you must have the EXP_FULL_DATABASE role enabled. This role is granted to all DBAs. 2. To use an older EXPORT release on a newer database release, you have to use SQL*Net or Net8 to access this database: EXP <username>/<password>@<instance_alias> ... 3. When using an older EXPORT release on a newer database release, you have to use the default CONVENTIONAL path export (i.e.: do not specify DIRECT=YES in the export command statement). A conventional path export uses the SQL SELECT statement to extract data from tables. A direct path export reads the data directly, bypassing the SQL Command Processing layer (evaluating buffer). 4. In order to check the revision of the export and import views, you can query the table sys.props$ with the following statement: SQL> SELECT * FROM sys.props$ WHERE name LIKE 'EXPORT%'; NAME VALUE$ COMMENT$ ------------------------- ----------- ------------------------ EXPORT_VIEWS_VERSION 8 Export views revision # The value of the property EXPORT_VIEWS_VERSION has the following meaning: +-------------------------------+ | EXPORT_VIEWS_VERSION | +-------+-----------------------+ | Value | Introduced in Release | +-------+-----------------------+ | *)| 7.0.* | *) no compatibility - assume zero | 1 | 7.1.3 | | 2 | 7.2.1 | | 3 | 7.2.3 | | 4 | 8.0.1 | | 5 | 8.0.2 | | 6 | 8.0.3 | | 7 | 8.0.4 | | 8 | 8.1.6 | +-------+-----------------------+ RELATED DOCUMENTS ----------------- [NOTE:61949.1] Overview of Export and Import in Oracle7 [NOTE:76542.1] NT: Exporting from Oracle8, Importing Into Oracle7 [NOTE:1012189.6] Errors trying to Import Transferred Export File [NOTE:155477.1] Parameter DIRECT: Conventional Path Export Versus Direct Path A32541-01 "Oracle7 Server Utilities Release 7.3", Chapter 1 "Export" and Chapter 2 "Import". A58244-01 "Oracle8 Utilities Release 8.0", Chapter 1 "Export" and Chapter 2 "Import". A76955-01 "Oracle8i Utilities Release 2 (8.1.6)", Chapter 1 "Export" and Chapter 2 "Import". A90192-01 "Oracle9i Database Utilities Release 1 (9.0.1)", Chapter 1 "Export" and Chapter 2 "Import". A96652-01 "Oracle9i Database Utilities Release 2 (9.2)", Chapter 1 "Export" and Chapter 2 "Import". A86632-01 "Oracle8i Migration Release 3 (8.1.7)", Chapter 9 "Compatibility".
.
--------------------------------------------------------------------------------
Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
- Compartir respuesta
- Anónimo
ahora mismo