Space allocation when using SAN
We are moving from a dedicated application/database server environment to separate application and database environments. The new database server will use a SAN for storage.
Our current setup uses a 16K blocksize and an 8 block multyblock read count and provides good performance. We try use best practices of Oracle Flexible Architecture but this will not be possible as we have no way of knowing where the database data will actually wind up on the SAN.
So far my research says that we should have different "filesystems" for control files, redo logs, archived logs, undo and temporary tablespaces. The actual data should be in a different filesystem with segments grouped acording to volatillty (reference vs update), type (index vs table) and next extent size (small, medium, large, Xlarge). An Oracle instructor once told me during the tuning course what those sizes were but he also added that Oracle was in the business of selling disks so I didn't pay much attention.