topic Re: Oracle in Operating System - HP-UX

Oracle

Vogra — Mon, 09 Jul 2001 20:00:13 GMT

Hi All!
I need to create a copy of my production database, but the name of the copy database cannot be different. It's possible to run two instances with same name on diferent servers on the same network?
Thanx.

Re: Oracle

A. Clay Stephenson — Mon, 09 Jul 2001 20:19:10 GMT

Yes, no problem at all.

Clay

Re: Oracle

James A. Donovan — Mon, 09 Jul 2001 20:56:02 GMT

As long as you're careful about any automatic jobs (select * from dba_jobs) and database link definitions I see no problem with this.

Also, be sure that whatever tnsnames.ora files you may use have seperate aliases for each copy.

Re: Oracle

Thierry Poels_1 — Tue, 10 Jul 2001 05:28:09 GMT

Hi,
as already mentioned : no problem.
I tend to use different passwords for production, development and test environment as an extra check to avoid having anybody working on the wrong environment.
regards,
Thierry.

Re: Oracle

federico_3 — Tue, 10 Jul 2001 05:42:08 GMT

No problerm , but if i were in your shoes i'd use different password for the two instances

Re: Oracle

Volker Borowski — Tue, 10 Jul 2001 05:55:49 GMT

Hi,

indeed this is not a problem.
But I would not like to have it this way.
Is there a reason why you do not want to have
diffrent names ?

Volker

Re: Oracle

Joseph C. Denman — Tue, 10 Jul 2001 11:40:01 GMT

Above are some really good suggestions. Why not Create a new instance with a different and import the data?

...jcd...

Re: Oracle

Vogra — Tue, 10 Jul 2001 11:43:04 GMT

Hi! All.

I have to migrate from Oracle 8.0.5 to 8.1.6(8i). I have to migrate server and ERP too. Some applications, developed a long time, don't work with synonyms and, if I change the name of database, they won't work well.
due to various causes (im my production system), during certain time, both of the database have to exist...
Thanx,

Re: Oracle

Bill Thorsteinson — Wed, 11 Jul 2001 03:30:05 GMT

Yes, it is possible to have two datatabase with the same
name on different servers on the network. However, if
you are connecting with network protocols you may
run into problems. Also if you allow any broadcast
based discovery of the database you can't count on
finding the desired database.

I had to assist reconstructing data from two servers
when an open firewall allowed some users to connect
to a test database while other connected to the
production data. Until we found out about the the
firewall it was confusing to get different results from
two computers side by side connected to the "same"
database running the same query.

If you have network connections for your applications.
how will you direct the user to the right database?
TNS will send them only one of the databases.

Your 8.0.5 applications should be happy connecting to
the 8.1.6 database. You can deffer the upgrade of
the internal structure and just change the software.
Leave the compatibility at 8.0.5 until you are ready
to upgrade. This will allow you to back down to
8.0.5 if necessary.

Test your upgrade in a sub-net disconnected from
the production network if possible.

I would upgrade as follows if possible:
- install 8.1.6 software
- shutdown database and start under 8.1.6
- upgrade applications
- upgrade server software to HP-UX 11 if desired.