I basically do that. I have 5 databases on a single server and it works
great for me except I have a separate mount for Tempfiles and Control files
as our storage vendor - NetApp has that has best practice because of the
way they do Snapshot backups. I didn't use tue u01 naming convention
though. Everything is its own mount point. If I had more databases this
might be too much but it works well. Oh and I am not running ASM, NetApp
suggested not too many years ago when we put our data on there.
/mnt/oralcehome
/mnt/FRA/fast_recovery_area/<DB_NAME>
/mnt/<DB_NAME>/archive01
/mnt/ <DB_NAME> /control01
/mnt/ <DB_NAME> /control02
/mnt/ <DB_NAME> /data01
/mnt/ <DB_NAME> /redo01
/mnt/ <DB_NAME> /redo02
/mnt/ <DB_NAME> /temp01
On Sun, Feb 28, 2021 at 3:19 PM Arian Stijf <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
Hi,
we use a similar setup too. Een though /u01/app/oracle is quite small and
only used for dba scripts.
With multiple database you create more mountpoints. We sepearate
redo/oradata/fra in separate mountpoints too. It allows us to assign
different i/o profiles to different mountpoints. OEM-agent, backup and DB
tree are located on HHD storage. The others are mixed SSD/HHD storage with
Tier 1 (highest performance for redo filesystem).
Do you have any reason to think this is a bad layout?
Regards,
Arian
On 2021-02-28 23:48, Michael Kline wrote:
Database setup
First time I’ve seen this layout?
Anyone else using it?
Each is a whole file system. Not sure what they do if you are running 5-8
databases on a server.
/u01/app/oracle
/u01/app/oracle/agent
/u01/app/oracle/backup/<DB_NAME>
/u01/app/oracle/<DB_NAME>/oradata ß All data here I guess.
/u01/app/oracle/<DB_NAME>/redo_01
/u01/app/oracle/<DB_NAME>/redo_02
/u01/app/oracle/<DB_NAME>/fra
*Michael Kline*
13308 Thornridge Ct
Midlothian, VA 23112
Cell: 804.314.6262
