1 Server; Multiple Production DBs- Help...

From: David Wagoner <dwagoner_at_arsenaldigital.com>
Date: Wed, 16 Jul 2003 11:20:02 -0400
Message-Id: <25937.338059@fatcity.com>

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------_=_NextPart_001_01C34BAD.BA765B10
Content-Type: text/plain;

charset="iso-8859-1"

Here's my situation:

Management wants us to move 4 small production DBs to one server to save on licensing costs. Server is a Sun E4500, 4 CPUs, 8 GB RAM. There is a pair of internal disks that are mirrored with enough room for Solaris, swap, and 1 Oracle Home. There are 3 A1000 disk arrays (12 x 18 GB drives each), all set to RAID 1+0 using the S.A.M.E. approach.

Questions:

Should I use a separate Oracle Home for each DB?

Pros: --Allows upgrade/patching of 1 DB at a time without affecting others (some are home-grown, some are 3rd party).

	Cons:  --Takes up more space, but space is not a major concern. 
                       --I'll have to put some Oracle Homes on the A1000s
with the data files (i.e., concerns about disk contention).
                       --Requires applying multiple upgrades/patches

2. Should I put 1 DB per A1000? (Actually, 1 A1000 would hold 2 of the least active DBs.)

Pros: --Easier to determine performance problems b/c each DB is isolated on 1 A1000.

                      --If one controller dies, it only affects 1 DB.

	Cons:  --Only get 1 controller; could use 3 controllers if data

files spread across 3 A1000s.

Anyone with experience doing this, please share your tips, tricks, and gotchas!

Best regards,

David B. Wagoner
Database Administrator
Arsenal Digital Solutions

------_=_NextPart_001_01C34BAD.BA765B10
Content-Type: text/html;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>1 Server; Multiple Production DBs- Help...</TITLE>
</HEAD>
<BODY>

Here's my situation:


Management wants us to move 4 small =
production DBs to one server to save on licensing costs.  Server = is a Sun E4500, 4 CPUs, 8 GB RAM.  There is a pair of internal = disks that are mirrored with enough room for Solaris, swap, and 1 = Oracle Home.  There are 3 A1000 disk arrays (12 x 18 GB drives = each), all set to RAID 1+0 using the S.A.M.E. approach.

Questions:


1.  Should I use a separate =
Oracle Home for each DB?  


        Pros:   --Allows upgrade/patching of 1 DB at a = time without affecting others (some are home-grown, some are 3rd = party).

        Cons:  --Takes up more space, but space is not a = major concern. 
          &nb= sp;           &nb= sp; --I'll have to put some Oracle Homes on the A1000s with the data = files (i.e., concerns about disk contention).

         &nb= sp;           &nb= sp; --Requires applying multiple upgrades/patches

 

2.  Should I put 1 DB per A1000? =
(Actually, 1 A1000 would hold 2 of the least active DBs.)


        Pros:  --Easier to determine performance problems = b/c each DB is isolated on 1 A1000.
          &nb= sp;            = --If one controller dies, it only affects 1 DB.


        Cons:  --Only get 1 controller; could use 3 = controllers if data files spread across 3 A1000s. 

 

Anyone with experience doing this, =
please share your tips, tricks, and gotchas!

 

Best regards,


David B. Wagoner
 Database Administrator
 Arsenal Digital Solutions
Received on Wed Jul 16 2003 - 10:20:02 CDT