|
|
|
|
| Re: Difference between SORT_MULTIBLOCK_READ_COUNT and DB_MULTIBLOCK_READ_COUNT [message #202834 is a reply to message #202821] |
Mon, 13 November 2006 00:30   |
reena_ch30
Messages: 100
Registered: December 2005
|
Senior Member |
|
|
It says "If the information needing to be sorted does not fit into the memory allocated to SORT_AREA_SIZE, sections of data are written to temporary
segments in the form of sorted runs. Once all the data has been partially sorted to these runs, the runs are merged by reading pieces of them (i.e. based on sort_multiblock_read_count) from the temporary segment into memory to produce the final sorted output. If SORT_AREA_SIZE is not large enough to merge all the runs at once (which is likely to be the case as it was not large enough to perform the entire sort in memory to begin with), subsets of the runs are merged in a number of merge passes."
My question is , if sort_area_size cannot merge all the runs at once, how would it do in no. of merge passes? Is the sort_area_retained_size used then?
Thanks
Reena
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
