Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 866
  • Last Modified:

Initial_Extent & Next_Extent in USER_TABLES.

Hi!

I got three pairs of info about Initial and Next, and all of them are different:
(1). Initial_Extent/Next_Extent in USER_TABLES
(2). Initial/Next  in the .dmp file, compress=n
(3). Initial/Next in the .dmp file, compress=y

I thought that (1) and (2) should be the same and both represent the most update setting of the tablespace. However, in some of my tables, the NEXT_EXTENT in (1) and the NEXT in (2) are different. Why?

In some of my tables, The NEXT in (2) and (3) are also different. Why? Because PCTINCREASE is NOT equal to 0?

Thanks a lot!!


0
mingichu
Asked:
mingichu
  • 2
1 Solution
 
nevalCommented:

If pct increase is not 0 that means you are intented to increase the next extent by =nextextent+(nextextent*pct increase) But this is not why these two comparisions have different results.


Regardless of the compress yes/no keeps the existsing structure of the tables but reestablish the structure and organize the blocks and each block will be fully optimally used, the raw migrations and raw chanins will be eliminated.

If you say compress=y then structure will be rebuild but if you say no the existing structure will be saved.

Regards.
Neval
0
 
mingichuAuthor Commented:
So, does it mean: INITIAL or NEXT shouldn't have any difference no matter compress = y or n?
Thanks again!
0
 
mingichuAuthor Commented:
So, does it mean: INITIAL or NEXT shouldn't have any difference no matter compress = y or n?
Thanks again!
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now