Articles
Improve Oracle's Automatic Storage Management (ASM) Feature Using Thin Provisioning
March 13, 2009
Click Here To Download:
Guest Column: Improve Oracle's Automatic Storage Management (ASM) Feature Using Thin Provisioning
Guest Column: Improve Oracle's Automatic Storage Management (ASM) Feature Using Thin Provisioning
Guest Column: Improve Oracle's Automatic Storage Management (ASM) Feature Using Thin Provisioning
By James F. Koopmann DCIG, LLC
The administration of storage for Oracle databases has come a long way and Oracle's Automatic Storage Management (ASM) feature has done a lot to eliminate the daily hassle of watching and provisioning storage. Gone are the days of when database administrators (DBAs) had to manage thousands of Oracle database files--watching block usage, extent allocations, file placement, file size, disk capacity, and performance hot spots. It's almost a crime when I think of the amount of time and effort it would take to maintain Oracle storage so space wasn't wasted and there was adequate performance.
As ASM is an Oracle Database 10g/11g feature, I'm sure many of us can still remember:
- Oracle and operating system limits on the number, size, and placement for data files
- Renaming and relocating data files to alleviate performance bottlenecks on disk
- Keeping specific object type (index, data) data files, as well as redo, control, and system files separate
- Resizing data file sizes, re-organizing objects, and recreating objects to condense or coalesce space
Guest Column: Improve Oracle's Automatic Storage Management (ASM) Feature Using Thin Provisioning




