Unexpected growth of ASM data file after modification of next attribute
I had an ASM tablespace run out of free space. I added a 250 MB datafile to the ASM disk group with no issue, except for the Next attribute being at 10 M, when I had meant to make it 100 M. I executed 'alter database datafile <fileid> autoextend on next 100M' and the file went from 250MB to 4GB in allocated space. I cannot figure out why this would happen. The disk group is in Normal redundancy. I had considered a template impacting the file size, but I didn't see any attributes that would set a minimum file size.
Does anyone know why this would happen?