Re: Q: Setting up multiple databases - same name

Daniel's reply is a perfectly reaonable approach - and one we used on a project we're just finishing. Just to spell it out:

Just to cover all options, you _can_ do it through multiple schemas if the development is all client-based. In this approach, each instance has a _different_ name but, when you set up the TNSNAMES on the clients, give the THS Alias the same name on each client machine.

Having said that, I prefer Daniel's approach: less resource intensive and easier to manage.

However, you still have to plan it. In particular, you also have to ask:

how are we going to manage system test, large volume test, pre-production test etc;

how are we configuring the final production database and does that have any implication for the test environment?

Len

>I am just starting out in the Oracle scene. I have been asked to setup
>a test environment for our developers on a local machine. These
>developers will be independantly using a database to test some
>programs.
>Here are the funtional requirements:
>
>1. All the developers will be testing their programs using the same
>DATABASE name.
>
>2. The developers need to have their own set of tables that will be
>common across the databases.
>
>How can this be best implemented:
>
>So far I have used dbassist to create a shell script and changed the
>locations of the tables and the SID names. When I start the first
>instance it runs fine but when I start the 2nd instance with a
>different parameter file name it complains that oracle is already
>running and to shut it down before trying to start the 2nd instance.
>I am testing this under Linux but this has to run under Win2K.
  Received on Sat Jun 09 2001 - 09:57:00 CDT