File system size and performance

[support_5]

Hi guys,

I'm creating a ServiceGuard package for a large Oracle database. The current database is on a 500GB file system.

Are there any advantages in splitting the large file system to 2x 250GB file systems? If so, how can I quantify it? I am using Secure Path Active-Passive on EVA5000, maybe create 2x 250GB LUNs, each to a separate controller? But with the new EVA5000 firmware due out soon that supports Active-Active, is it worth the trouble?

Background:
HP-UX 11i v2
Oracle 9.2.0.4 (soon to be 10g)
EVA5000 within one disk group, dual 2GB fibre SAN connected, Secure Path 3.0F Active-Passive
Database used for scanning/retrieving documents, online transaction type processing

Thanks in advance, guys.

Tung

[RAC_1 · Accepted solution]

If I look at what I usually follow, I do not want to have files systems greater than 250GB max. The problem is manageability. I also feel that there is slight overhead with performance. vg activation takes a little longer.

And in case of Oracle, the better thing to do is seperate redo logs, archive logs database files and binaries. ORACLE advises SAME, (strip all mirror everything.) So instead of going for one 500GB FS, whay not split it??

200GB*3 or 150*xx looks fine to me. This firther depends upon is oracle operation write intensive or read itensive??

[Arunvijai_4]

Have a look at these thread,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=183536
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=145144

-Arun

[support_5]

Thanks for your quick responses.

As silly as it may sound, the holdback of splitting the FS is the naming convention, ha! To answer your question, RAC, we split archive logs and oradata files. The database is used for our correspondence management, I'll say read/write are equal.

Seems worthwhile to split the FS, now to convince the DBAs.

[Sยภเl Kย๓คг]

Hi,
If you are using oracle with RAW colume for tablespace, u can utilize only a mximum of 32Gb size in of one filesystem. After that you need to create another LV and extend tablespace in to teh new LVs. We have online databases which is more than 2TB in size with XP12000. To improve the performance you need to plan a lot

1. No of stripes of the LV, if no of stripes increases the performance boosts up
2. At Storage side, how the port load balancing is done.
3. You need to have Secure path with load balancing at server side.

For the Database we use 8 No of stripes and for archive log we use 4 no of stripes

regards,
Sunil