Fragmentation Help

| Fragmentation Help |
--- | --- | ---
Fragmentation occurs at the table (heap) or index (b-tree) level. Essentially when you create objects in a tablespace, if you set them all with different storage parameters, or a pctincrease which is non-zero you'll likely cause tablespace fragmentation of the objects contained therein. Fragmentation can be resolved by rearranging objects in other tablespaces, rebuilding with different storage parameters, or export/import. Ideally though, it would be best to avoid fragmentation altogether. How can we accomplish this? Oracle recommends in their latest whitepaper on the subject "How To Stop Defragmenting and Start Living" to avoid fragmentation altogether by creating tablespaces with with uniform extent sizes, and leaving objects to assume the default storage params when they're created. For more information, check: How To Stop Defragmentating and Start Living. At any rate, karma can be setup to be strict or not so strict. Configure karma for fragmentation monitoring as follows: fragmentation:X:Y:Z Where X, as usual is frequency in minutes at which to check for fragmentation. Y is the WARNING value, and Z is the ALERT value.