[ Pobierz całość w formacie PDF ]
.Each table is associated with otherobjects, such as the data, indexes, grants, audits, triggers, and comments.The entire grant structure for tables or views is exported with the underlyingbase tables.Indexes are exported with their base table, regardless of whocreated the index.If the base view is included, instead of triggers on viewsare included.Any modification (UPDATE, INSERT, or DELETE) on a table automaticallyqualifies that table for incremental Export.When a table is exported, all of itsinner nested tables and LOB columns are exported also.Modifying an innernested table column causes the outer table to be exported.Modifying a LOBcolumn causes the entire table containing the LOB data to be exported.Also, the underlying base tables and data are exported if database structureshave changed in the following ways:" a table is created" a table definition is changed by an ALTER TABLE statement" comments are added or edited" auditing options are updated" grants (of any level) are altered1-40 Oracle8 Server Utilities " indexes are added or dropped" index storage parameters are changed by an ALTER INDEX statementIn addition to the base tables and data, the following data is exported:" all system objects (including tablespace definitions, rollback segmentdefinitions, and user privileges, but not including temporary segments)" information about dropped objects" clusters, tables, views, procedures, functions, and synonyms createdsince the last export" all type definitionsExample Incremental Export SessionThe following example shows an incremental Export session after the tablesSCOTT.EMP and SCOTT.DEPT are modified:> exp system/manager full=y inctype=incrementalExport: Release 8.3.0 - Production on Tue May 20 7:57:47 1997(c) Copyright 1997 Oracle Corporation.All rights reserved.Connected to: Oracle8 Server Release 8.3.0 - ProductionPL/SQL Release 8.3.0 - ProductionExport done in US7ASCII character set and WE8DEC NCHAR character setAbout to export the entire database.exporting tablespace definitions.exporting profiles.exporting user definitions.exporting roles.exporting resource costs.exporting rollback segment definitions.exporting database links.exporting sequence numbers.exporting directory aliases.exporting foreign function library names.exporting object type definitions.exporting cluster definitions.about to export SYSTEM's tables via Conventional Path.about to export SCOTT's tables via Conventional Path.exporting table DEPT 8 rows exported.exporting table EMP 23 rows exported.about to export ADAMS's tables via Conventional Path.about to export JONES's tables via Conventional Path.about to export CLARK's tables via Conventional Path.Export 1-41 .about to export BLAKE's tables via Conventional Path.exporting referential integrity constraints.exporting posttables actions.exporting synonyms.exporting views.exporting stored procedures.exporting triggers.exporting snapshots.exporting snapshot logs.exporting job queues.exporting refresh groups and children.exporting default and system auditing options.exporting information about dropped objectsExport terminated successfully without warnings.System TablesThe user SYS owns three tables (INCEXP, INCFIL, and INCVID) that aremaintained by Export.These tables are updated when you specifyRECORD=Y (the default).You should not alter these tables in any way.SYS.INCEXPThe table SYS.INCEXP tracks which objects were exported in specific exports.It contains the following columns:OWNER# The username of the schema containing the table.NAME The object name.With OWNER#.The primary keyconsists of OWNER#, NAME and TYPE#.TYPE# The type of the object (a code standing for TABLE,CLUSTER, VIEW, SYNONYM, SEQUENCE,PROCEDURE, FUNCTION, PACKAGE, TRIGGER,SNAPSHOT, SNAPSHOT LOG, or PACKAGE BODY).CTIME The date and time of the last cumulative export thatincluded this object.ITIME The date and time of the last incremental export thatincluded this object.EXPID The ID of the incremental or cumulative export, alsofound in table SYS.INCFIL.You can use this information in several ways.For example, you couldgenerate a report from SYS.INCEXP after each export to document the export1-42 Oracle8 Server Utilities file.You can use the views DBA_EXP_OBJECTS, DBA_EXP_VERSION, andDBA_EXP_FILES to display information about incremental exports.SYS.INCFILThe table SYS.INCFIL tracks the incremental and cumulative exports andassigns a unique identifier to each.This table contains the following columns:EXPID The ID of the incremental or cumulative export, alsofound in table SYS.INCEXP.EXPTYPE The type of export (incremental or cumulative).EXPFILE The name of the export file.EXPDATE The date of the export.EXPUSER The username of the user doing the export.When you export with the parameter INCTYPE = COMPLETE, all theprevious entries are removed from SYS.INCFIL and a new row is addedspecifying an x in the column EXPTYPE.SYS.INCVIDThe table SYS.INCVID contains one column for the EXPID of the last validexport.This information determines the EXPID of the next export.Export 1-43 Network ConsiderationsThis section describes factors to take into account when you use Export andImport across a network.Transporting Export Files Across a NetworkBecause the export file is in binary format, use a protocol that supports binarytransfers to prevent corruption of the file when you transfer it across anetwork.For example, use FTP or a similar file transfer protocol to transmitthe file in binary mode.Transmitting export files in character mode causeserrors when the file is imported.Exporting and Importing with Net8By overcoming the boundaries between different machines and operatingsystems on a network, Net8 (previous versions are called SQL*Net) providesa distributed processing environment for Oracle8 Server products.With Net8(and SQL*Net V2), you can perform exports and imports over a network.Forexample, if you run Export locally, you can write data from a remote Oracledatabase into a local export file
[ Pobierz całość w formacie PDF ]