Glenn
Creating a new database definitely costs more in support. It needs a
backup plan, recovery testing, etc.
In the past I've examined issues like how much the new application is
like existing applications, whether it is likely to need the same upgrade
timing, backup schedule (before RMAN)
Another concern is user rights. When you copy a production database to test,
everything in that database is an exact copy of production. If you just import a
production schema into a test schema, your users and their roles are not updated.
You will have to discuss your concerns with the d
As you said, one advantage of a single instance is the memory and disk space
usage. Another disadvantage is when you need to upgrade the database for one
application, but not for another.
Keith
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Tuesd
Glenn:
You already know the questions and seem to be pointed to the answers. We
put multiple schemas in an instance when there is a similarity. If the
schemas belong to the same
business unit or department, and they are similar applications, like OLTP,
then we can put them in the same instance.
> Our DBA group has recently been getting numerous requests for
> new databases (training, inventory, customer contacts, etc..)
> from different departments within the company. Our normal
> procedure is to create a new instance for the database,
> create the schema, users, etc..., set up backups a
