Hi Largou,
I apologize for the most complete, yet simple answer: It depends! (In reference to Bernie Schiefer!)
Now, back to a different answer. Well, there are a lot of things to consider splitting up the database into filesystems, LUNs etc.
You might want to use as much spindles in parallel as possible. Split data tablespaces and index tablespaces. Make sure, your large data (BLOB, CLOB, LONG) is in a separate tablespace. Define multiple bufferpools. Have lots of memory. And for BLU have lots of cores. It aint cheap.
Partitioning is a good thing, if you have understood what to partition on and depending on your queries. So does the layout depend on your data and what is stored in your databases. If not partitioning, put your larges data in a separate tablespace. Not to forget fact tables, which are in referential integrity with it.
A 17TB SAP system would require a different layout than a dump from some physics experiment.
Don't disregard the old docs. Look for the "best practices" series within Db2 Community. If you don't find it yourself, I can lookup pointers for you.
If you need more help, just give us some more details, about your environment.
Cheers
------------------------------
Roland Schock
Distinguished Engineer
ARS Computer und Consulting GmbH
Muenchen
------------------------------
Original Message:
Sent: Tue March 08, 2022 10:05 AM
From: Largou walid
Subject: DB2 Storage layout for large databases
Hi Everyone,
Have been looking for some documentation on sizing recommendations and best practices for setting up the storage (LUNs size and number, filesystems layout …) but only found old documentation.
We have three databases with 17T in total, can you suggest a rule of thumbs for DB211.5with BLU on AIX ?
Thank you
------------------------------
Largou walid
------------------------------
#Db2