Your question is not simple. First of all SAN consists from a transport layer, storage controllers and disks. There are no difference from application point of view where storage controllers resides. Disk is disks - they have limited read and write throughoutput and latency. Of course storage controllers in SAN have internal caches but at end of data travel we see good old disks. Thats why carefully placement policy is important thing.
About tablespace/datafile problems - try to don't mix tables from one application with another in one tablespace.
Performance and backup strategy is arguments for
decision about number of tablespaces/datafile.
BTW this is a good paper about oracle and RAID:
http://www.fors.com/orasup
2schwertner: 64-bit oracle don't have 4GB limit in datafile size.
Main Topics
Browse All Topics





by: schwertnerPosted on 2003-05-10 at 06:06:31ID: 8499896
SUN is the name of computr, not SAN.
It is better when the index tablespaces resides on different drive from the table tablespace.
It is easier to manage (backup, recover, change increase parameters, etc') tablespaces that have a lower number of tables.
There is a boundary in Oracle systems, as I remember 4 GB. If you cross this boundary you will run in trouble - see the note bellow:
Does Oracle support files of this size?
Is this a problem with backups?
Search Words:
=============
2GB, 4GB, datafile, big, tablespace
Solution Description:
=====================
Can you create a 4 GB file if your Unix file size limit is 4 GB instead of 2 GB?
No, you must create smaller data file sizes.
Does Oracle support files of this size?
No, not for this version.
Is this a problem with backups?
No, with Oracle handling file sizes larger than 2 GB.
Solution Explantion:
====================
Oracle still uses data files no larger than 2 gigabytes in size. When allocating a large file use multiple equal size data files. You only need to create the first, then you can add others to meet your space requirements. In
a big tablespace (2GB) create 4 data files of 500 MB each.
Also consider this: Unix systems have trouble backing up data files that are larger than 1 gigabyte in size. So allocate a tablespace's physical data files in standard sizes. This will make swapping the data files an easy task when you begin the tuning cycle for I/O balancing.