Re: multi oracle instances in one machine

On Mon, 28 Dec 1998 19:21:47 +0800, bjin <jinbo_at_hpsgns1.sgp.hp.com> wrote:

>Hi,
>
>Kindly give me some guidelines on this.
>
>Within our product framework, there are 3 sub-applications which use
>Oracle database to store data. Each of them owns a set of tables
>respectively. These 3 applications run on a single machine.
>
>When implementing system, we have two choices.
>1. Create only 1 Oracle database and create tables of 3 applications in
>3 different user's schema.
>2. Create 3 Oracle databases in 1 machine and create tables in 3
>different databases.
>
>Which way is better? What should we consider when choosing from the 2
>methods?
>
>The platform is hp9000, hpux 10.x and Oracle 7.3.4. It has 1G memory and
>4 cpus.
>
>Thanks
>
>bjin

You'll get lots of responses here following along with Oracle's mentality of "put them all in one instance". Some things to note (and pointing towards separate instances) are:

1. Different apps. OLTP, DSS and DW style apps all have different DB tuning requirements. If the apps are different types, definately something worth considering
2. Restore problems. It usually takes one experience of this to realise that backups are easy in one instance, but restores can be a nightmare. Depending on the reason for a restore, each of the different apps may need full, partial, or point-in-time restores. The point being, they may possibly require DIFFERENT levels/types of restores (believe me, some apps can be really screwy like this - especially if ref integrity and transactions aren't used as they should be). While this isn't a glitch with the way Oracle works - you'd think all apps would handle being restored to the maximum extent possible - it's worth checking out the applications themselves to see if they have any limitation in this regard.

Ciao
Fuzzy
:-) Received on Mon Jan 04 1999 - 17:17:04 CST