Podobne
- Strona startowa
- Kres Feliks W Polnocna Granica scr
- securing redhat
- Alistair Maclean Lalka Na Lancuchu 2 (2)
- Tolkien J R R Wladca Pierscieni T 3 Powrot Krola
- Szczypiorski Andzej Poczatek
- John Fowles Mag
- Feist Raymond E Adept magii (SCAN dal 734)
- NamiętnoÂść po zmierzchu
- Tony.Buzan. .Pamięć.na.zawołanie
- Rok1794 t. 3 Reymont
- zanotowane.pl
- doc.pisz.pl
- pdf.pisz.pl
- radius.htw.pl
Cytat
Do celu tam się wysiada. Lec Stanisław Jerzy (pierw. de Tusch-Letz, 1909-1966)
A bogowie grają w kości i nie pytają wcale czy chcesz przyłączyć się do gry (. . . ) Bogowie kpią sobie z twojego poukładanego życia (. . . ) nie przejmują się zbytnio ani naszymi planami na przyszłość ani oczekiwaniami. Gdzieś we wszechświecie rzucają kości i przypadkiem wypada twoja kolej. I odtąd zwyciężyć lub przegrać - to tylko kwestia szczęścia. Borys Pasternak
Idąc po kurzych jajach nie podskakuj. Przysłowie szkockie
I Herkules nie poradzi przeciwko wielu.
Dialog półinteligentów równa się monologowi ćwierćinteligenta. Stanisław Jerzy Lec (pierw. de Tusch - Letz, 1909-1966)
[ Pobierz całość w formacie PDF ]
.For object types, if IGNORE=N and the object type already exists, an error isreported.If the object identifiers do not match, any tables using the objecttype are not imported.For object tables, if IGNORE=Y and the table already exists and the objectidentifiers match, no error is reported.Rows are imported into the objecttable.If the object identifiers do not match, an error is reported and the tableis not imported.For object tables, if IGNORE = N and the table already exists, an error isreported and the table is not imported.For object tables, if IGNORE=Y and if the table already exists and the table sobject identifiers match, import of rows may fail if rows with the same objectidentifier already exist in the object table.Because Import preserves object identifiers of object types and object tables,note the following considerations when importing objects from one schemainto another schema, using the FROMUSER and TOUSER parameters:" If the FROMUSER s object types and object tables already exist on thetarget system, errors occur because the object identifiers of theTOUSER s object types and object tables are already in use.TheFROMUSER s object types and object tables must be dropped from thesystem before the import is started." If an object table was created using the OID AS option to assign it thesame object identifier as another table, both tables cannot be imported.One may be imported, but the second receives an error because theobject identifier is already in use.2-56 Oracle8 Server Utilities Importing Existing Object Tables and Tables That Contain Object TypesUsers frequently pre-create tables before import to reorganize tablespaceusage or change a table's storage parameters.The tables must be created withthe same definitions as were previously used or a compatible format (exceptfor storage parameters).For object tables and tables that contain columns ofobject types, format compatibilities are more restrictive.For object tables, the same object type must be specified and that object typemust have the same object identifier as the original.The object table's objecttype and identifier must be the same as the original object table's object type.For tables containing columns of object types, the same object type must bespecified and that type must have the same object identifier as the original.Export writes information about object types used by a table in the Export file,including object types from different schemas.Object types from differentschemas used as top level columns are verified for matching name and objectidentifier at import time.Object types from different schemas that are nestedwithin other object types are not verified.If the object type already exists, itsobject identifier is verified.Import retains information about what objecttypes it has created, so that if an object type is used by multiple tables, it iscreated only once.In all cases, the object type must be compatible in terms of the internal formatused for storage.Import does not verify that the internal format of a type iscompatible.If the exported data is not compatible, the results areunpredictable.Importing Nested TablesFor nested tables, the storage information for the inner tables is exported witha DDL statement separate from the creation of the outer table.Import handlesthe multiple statements as one atomic operation.If the creation of the outertable fails, the inner table storage information is not executed.If the creationof the outer table succeeds, but the storage creation for any inner nested tablefails, the entire table is dropped and table data is not imported.If the outertable already exists and IGNORE=Y, the inner table storage is not created.Because inner nested tables are imported separately from the outer table,attempts to access data from them while importing may produce unexpectedresults.For example, if an outer row is accessed before its inner rows areimported, Import returns an incomplete row to the user.Import 2-57 Inner nested tables are exported separately from the outer table.Therefore,situations may arise where data in an inner nested table might not beproperly imported:" Suppose a table with an inner nested table is exported and thenimported without dropping the table or removing rows from the table.If the IGNORE=Y parameter is used, there will be a constraint violationwhen inserting each row in the outer table.However, data in the innernested table may be successfully imported, resulting in duplicate rowsin the inner table." If fatal errors occur inserting data in outer tables, the rest of the data inthe outer table is skipped, but the corresponding inner table rows are notskipped.This may result in inner table rows not being referenced by anyrow in the outer table." If an insert to an inner table fails after a non-fatal error, its outer tablerow will already have been inserted in the outer table and data willcontinue to be inserted in it and any other inner tables of the containingtable.This circumstance results in a partial logical row." If fatal errors occur inserting data into an inner table, the import skipsthe rest of that inner table s data but does not skip the outer table orother nested tables." You should always carefully examine the logfile for errors in outertables and inner tables.To be consistent, table data may need to bemodified or deleted.Importing REF DataREF columns and attributes may contain a hidden ROWID that points to thereferenced type instance.Import does not automatically recompute theseROWIDs for the target database.You should execute the following commandto reset the ROWIDs to their proper values:ANALYZE TABLE [schema.]table VALIDATE REF UPDATESee the Oracle8 Server SQL Reference manual for more information about theANALYZE TABLE command
[ Pobierz całość w formacie PDF ]