Very High Next_extent After Transportable Tablespace Exercise
(Doc ID 1362579.1)
Last updated on MARCH 10, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 to 22.214.171.124 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This issue occurs if source database is 10g and destination database is 126.96.36.199 But this issue is fixed in 188.8.131.52 database version if both databases( Source and target are 184.108.40.206)
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
A transportable tablespace exercise where 6 tablespaces were transported into a new database. After completion, all segments in those tablespaces had NEXT_EXTENT set to 17,592,186,036,224 (= 16 TB less 8192 bytes). Is this large NEXT_EXTENT setting expected behaviour after such an exercise?
As you can see the next extent has been set extremely high.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document