Transporting tablespaces with XMLTypes limitations - Oracle Tablespaces

Q.  What are the additional limitations for Transporting tablespaces with XMLTypes?
- Published on 12 Aug 15

a. Advanced Queues
b. SYSTEM Tablespace Objects
c. Opaque Types
d. Floating-Point Numbers
e. All mentioned above

ANSWER: All mentioned above

Related Content

 

    Discussion

  • Nirja Shah   -Posted on 31 Aug 15
    - Additional limitations include the following:

    - SYSTEM - Tablespace Objects you cannot transport the SYSTEM tablespace or objects owned by the user SYS.
    - Some examples of such objects are PL/SQL, Java classes, callouts, views, synonyms, users, privileges, dimensions, directories, and sequences.

    - Opaque Types - Types whose interpretation is application-specific and opaque to the database (such as RAW, BFILE, and the AnyTypes) can be transported, but they are not converted as part of the cross-platform transport operation.
    - Their actual structure is known only to the application, so the application must address any endianness issues after these types are moved to the new platform.
    - Types and objects that use these opaque types, either directly or indirectly, are also subject to this limitation.

    - Floating-Point Numbers - BINARY_FLOAT and BINARY_DOUBLE types are transportable using Data Pump.

    - Advanced Queues - Transportable tablespaces do not support 8.0-compatible advanced queues with multiple recipients.

➨ Post your comment / Share knowledge


Enter the code shown above:
 
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)
▲