AliD wrote:May make sense, means you are not sure? If sure, then any example or any doc link which supports your saying. I just want to see in docs that mention the uses of MSSM in compare to ASSM please.
In a data warehouse using MSSM may make sense. There's minimum update in DW and locking is not an issue.
Why oracle is not brining back MSSM in its new versions, if ASSM has been proved the best.I am not sure I am getting where you are coming from. MSSM was never ruled out. Its usage was not suggested by Oracle with the introduction of ASSM which is obvious because ASSM is a better option than MSSM.
May make sense, means you are not sure?May means you have to try it in your own environment as there is no "rule of thumb" that applies every where.
Its usage was not suggested by OracleYes, and this makes me in a fix; that if it is not recommended by oracle, experts; then why it is still there? Can i say it as an "Not suggested but existing feature", something like "no use"?
there are couple of issues you may run into when you use ASSMI shall be thankful to you, if you please mention more those issues like you mentioned with issue of large blocksize.
Yes, and this makes me in a fix; that if it is not recommended by oracle, experts; then why it is still there? CI am not sure that why you are struck on this that its there? Its a feature, its usage is based on your choice. It was the default way to manage the segments till 10g if I remember correctly even when the ASSM was around since 9i. Only in 11g(if I am correctly recalling) , the management behavior now is using ASSM by default.
Can i say it as an "Not suggested but existing feature", something like "no use"?Yes, that's what I tried to explain with the above example of DMT and Latches.
Probably, i am missing some really good advantages over ASSM; otherwise oracle could have withdrawal this feature.I suggest not to bother that when it would be withdrawn. Just remember that its better to use ASSM and this is the default too if you won't play with the tablespace level attributes and let them be default.
user12050217 wrote:And they probably will at some point in the future. Most software vendors take several major releases to phase out old features in favor of new, and during the transition, both are documented and supported. This allows customers an easier upgrade path. Can you imagine what it would be like to upgrade from 9 to 10 if every "replaced" feature were totally eliminated at once? You're spinning your wheels looking for some deep technical justification when the real answer is probably far simpler and more mundane.
Probably, i am missing some really good advantages over ASSM; otherwise oracle could have withdrawal this feature.
Thanks and Regards,
With ASSM, the extent size starts small (64KB) and grows to 1MB, 8MB, etc. as additional extents are added to segmentsWrong. Extent Sizes are defined by the Allocation Policy which you would specify with EXTENT MANAGEMENT LOCAL AUTOALLOCATE.