1. Use the Oracle Export / Import tool for Export / Import to deliver data between the database. EXPORT exports data from the database to the DUMP file in the Dump file In the DUMP file, the following is the usual use of their situation (1), the two databases transmit data the same version of the Oracle Server between the same version. Different versions. Between the other OS between Oracle Server (2), used for backup and recovery of the database (3), transfer from one schema to another, transfer from a TableSpace to another TABLESPACE 2 , DUMP files Export arrives at the binary format file, which is not manually edited, otherwise the data will be damaged. This file is the same format on any platform supported by Oracle, which can be universal on each platform. The DUMP file uses an upwardly compatible mode when IMPORT is that Oralce7's DUMP file can be imported into Oracle8, but there may be problems between versions of the version. 3, the DUMP file exported by the Export / Import process export contains two basic types of 氖 ? NBSP; - DDL - Data DUMP file contains all DDL statements that recreate Data Dictionary, basically readable format. But it should be noted that don't use the text editor to edit it, Oracle does not support this.
The Oracle objects included in the dump file are divided into Table / User / Full, and some objects are just in the full mode (such as public synonyms, users, rolls, rollback segm ents, etc.) Table Mode User Mode Full Database Mode ---------------------------------------------- ------------------- Table Definitions Table Definitions Table Definitions Table Data Table Data Table Data Owner's Table Grants Owner's GRANTS GRANTS OWNER's Table Indexes Owner '
s indexes Indexes Table constraints Table constraints Table constraints Table triggers Table triggers All triggers Clusters Clusters Database links Database links Job queues Job queues Refresh groups Refresh groups Sequences Sequences Snapshots Snapshots Snapshot logs Snapshot logs Stored procedures Stored procedures Private synonyms All synonyms Views Views Profiles Replication catalog Resource Cost ROLES ROLLBACK SEGMENTS System Audit Options System Privileges TableSpace Definitions 4 of.
1. Tablespaces 14. Snapshot Logs 2. Profiles 15. Job Queues 3. Users 16. Refresh Groups 4. Roles 17. Cluster Definitions 5. System Privilege Grants 18. Tables (also grants, commen ts, 6. Role Grants indexes, constraints , audi ting) 7. Default Roles 19. Referential Integrity 8. Tablespace Quotas 20. POSTTABLES actions 9. Resource Costs 21. Synonyms 10. Rollback Segments 22. Views 11. Database Links 23. Stored Procedures 12. Sequences 24. Triggers, Defaults And AUD ITING 13. Snapshots According to this order, it is mainly to solve the problem that may generate dependencies between objects. Trigger finally imports, not exciting Trigger when INSERT data to the database. There may be some states after importing, which is the Proc Edure of Invalid, which is mainly imported, which affects some database objects, and IMPORT does not recompile procedure, resulting in this, can be recompiled, can solve this problem. 5. Compatibility The IMPORT tool can handle the DUMP file exported after the version of Export 5.1.22, so you use Oracl E7's Import to handle Oracle6's dump file, push it according to the class, but oracle is much better if the version varies. The specific problem can refer to the corresponding document, such as the parameter setting, etc. (Compatible parameters) 6, the View Export required for Export is created by catexp.sql, which is used for the data format in the Export organization DUMP file. Most View is used to collect create DDL statements, others are mainly used by Oracle developers. These Views may differ between different Oracle versions, each version may have new features.
So in the new version, the old DUMP file will have an error. You can execute catexp.sql to solve these problems, and solve the general steps of backward compatibility issues are as follows: Exporting the database is older than the target database: - Import Old catexp.sql in the target database - Export Dump files with old exports - Import the old IMPORT to the database - perform new catexp.sql in the database to recover the version of the version of the export view exported database ratio New Situation: - Perform new catexp.sql in the target database that needs to be imported - Export Dump files with new export - Import the new import into the database - perform old catexp.sql in the database to recover This version of Export View 7, fragmentation of Export / Import is a very important application to finish the debris. Because if IMPPORT is time IMPPORT, you will re-import data, so the entire sheet is continuously stored. In addition, it is default Exports to generate DUMP files "Compress" table, but this compression is misconced in many cases. In fact, Compress is the value of changing the Storage Parameters Initial. For example: Create Table .... Storage (Initial 10k next 10k ..) Nowadays have been extended to 100 extent, if compress = y is used to export data, the Storage (Initial 1000K Next 10K) We can see The NEXT value did not change, and initial is the sum of all Extent. So the following cases, Table A has 4 100M Extent, execute the delete from A, then use compress = y to export data, the resulting CREATE TABLE statement will have 400m Initial Extent. Even this is there is no data in Table! ! This is the DUMP file even if it is small, but it will generate a huge Table when IMPORT. In addition, it may exceed the size of the DataFile. For example, there are 4 50m data files, where Table A has 15 10M Extent, and if you use compress = y, you will have initial = 150m, then you cannot allocate a 150M extent, Because a single extent cannot span multiple files. 8. Transferring data between user and tablespace usually export's data to be restored to it. If the Scott user's table is used in Table or User mode, when the Scott user does not exist, it will be an error! The data exported in the full mode with the crete user information, so you will create the user yourself to store data. Of course, you can use fromuser and Touser parameters when IMPORT can determine the User to import, but to ensure that Touser must already exist. 9. EXPORT / IMPORT's impact on Sques In both cases, Export / Import will have Sequence. (1) If in Export, the user is taking the value of the Sequence, which may cause the disqualification of Sequence.
