This content has been marked as final. Show 4 replies
To change default striping you need :
1. to use ALTER DISKGROUP with ADD TEMPLATE or ALTER TEMPLATE clause: http://docs.oracle.com/cd/B19306_01/server.102/b14231/storeman.htm#i1019485.
2. to create the database file with the right template: http://docs.oracle.com/cd/B19306_01/server.102/b14231/storeman.htm#i1010348.
Thank you so much
I've defined template and added new diskgroup (with number 5)
When I query v$asm_template I see new lines were added with group_number 5 where it uses different striping for onlinelogs, controlfiles, datafiles and etc.
I will use this dskgroup for online redo log files, so how asm defines that the files are online log files and uses correct striping?
Striping is enforced by ASM at the file level not diskgroup.
Redundancy is enforced at diskgroup level.
ASM knows which file is what by it's header when it gets created and will apply the stripping accordingly, as set on the template.
But we can also specify protection level while creating the template. For example let's say we have a diskgroup +DATA with normal redudancy and I created a template for DATA diskgroup with protection level UNPROTECTED, in that case whatever files will be created with this template will not mirror the data although diskgroup redudancy level is Normal.