oracle ASM详细资料.ppt

Objectives Understand how Oracle database files are stored in ASM Calculate how long ASM rebalance operations will take Agenda ASM Instances ASM Disk Groups Metadata Extent Distribution Rebalancing Redundancy ASM Single Instance Architecture ASM Single Instance Background Processes ASM RAC Architecture ASM RAC Architecture ASM RAC Instance Background Processes ASM Disk Groups and Disks ASM Disk Groups and Disks ASM Disk Groups, Disks and Database Files File Extents versus Allocation Units File Extent Logical unit of ASM file Map to allocation units One to many mapping Allocation Unit Physical unit of ASM disk Oracle 10.2 and below Always 1MB Can be increased using _asm_ausize Oracle 11.1 and above Variable size 1MB, 2MB ,4MB, 8MB, 16MB, 32MB, 64MB X$KFFXP Maps file extents to allocation units Only populated in ASM instance Columns include ASM Metadata Metadata is stored in first 256 files in ASM disk group Space is initially allocated when disk group is created Can be subsequently extended Metadata allocation units are divided into blocks Each block is 4096 bytes Block size specifed using _asm_blksize Metadata files include ASM Metadata ASM Metadata Initial Allocation (Single Instance) ASM Metadata Block Types KFED Utility In Oracle 10.2 and above the kfed utility can be used to inspect and edit the contents of ASM blocks KFED Utility For example to dump blocks in aliases directory in DISKGROUP1 Find group number KFED Utility Example (continued) Allocation unit is 1MB Block size is 4096 Therefore there are 256 blocks per allocation unit Starting block offset = 256 * 49 = 12544 Extent Distribution Creating a disk group: Extent Distribution1 disk Extent Distribution2 disks Extent Distribution4 disks Extent Distribution1 large disk - 1 small disk Extent Distribution1 large disk - 3 small disks Extent Distribution2 large disks - 2 small disks Extent Distribution Adding a disk: RebalancingAdding disks - 1 disks to 2 disks RebalancingAdding disks - 1 disks