How to structure instances/applications?

From: <jhostett_at_host1.redrose.net>
Date: 1996/01/30
Message-ID: <4elrbj$7dq_at_lily.redrose.net>#1/1

I have been in the DBA role for only a few months. We have a relatively small portion of our data in Oracle at the present time, but most of our applications will moving to Oracle. My question pertains to the organization of the instances,applications,data, etc. For example, when do I determine that I need a new instance? What schema does new data go into? My plan is as follows:

1. We have two instances, each on a separate host. I plan to divide the applications between the instances to distribute the work load. My understanding is that the more instances I create, the more overhead there is (i.e. I don't want an instance for each application).
2. Within each instance, I plan to set up a username for each application. Under this user, the data for that application will be stored. For example, our billing system data might reside under a user called BILLSYS. This username will not normally be used as a login account, it is just to organize the data.
3. I also plan to put each application into it's own tablespace(s), for ease of backup and recovery.
4. Each application will have its own set of roles. These roles will be granted to those users who need them. I will designate a user to be the administrator of these roles, granting them to other users who need them.

I am curious to know how others have organized their applications and data with Oracle. Am I on the right track? I would like to have a plan in place before all of our applications move to Oracle, rather than to look back and say "I should have done it this way..."

Thank you

---

Jay Hostetter
D&E Tel. & Tel. Co.
Ephrata, Pa. U.S.A
jhostett_at_host1.redrose.net

---

Received on Tue Jan 30 1996 - 00:00:00 CET