Re: Oracle8i - Node name and ghost imaging!

If I understand your position correctly, I rather suspect that you will be better off writing an unattended installation script and installing oracle from that each time. This route would obviously take longer though.

Alternatively what is wrong with locating the databases centrally?

--
Niall Litchfield
Oracle DBA
Audit Commission UK
"Trevor Bell" <trevor.bell_at_powertec.co.uk> wrote in message
news:992259546.448405_at_dionysos...


> Paul,

>  we have approx 15 workstations we want to set up with Oracle8i and 4

> databases

>  and would like configs to be identical, hence use of imaging. This would

> allow any user to

>  use any workstation (with their own profile) and access any of the 4

 local


> databases.

>  Databases would be db-1, db-2 etc where each user would import whatever

> data

>  they like into any of the 4 databases on their workstation.

>  The imaging is to guarantee each machine has same configuration, and if 1

> machine loses a disk, then the

>  image can be loaded onto a new disk without too much fuss. Also any new

> machine can be setup immediately

>  without the hassle of trying to install all software required.

>  We already know if on machine A, we change host of db_1 in tnsnames to

> point to machine B, then

>  stop service for db_1 on machine A, when we restart db_1 service on

 machine


> A we can access db_1

>  on machine B from machine A.

> The problem is, when installing Oracle it takes the machine name as the

 node


> name

> and propogates it throughout the Registry and the services, therefore

> cutting the image

> will take the node name of that machine and spread it across the other

> machines.

> We cannot use the same node name/machine name for each machine as this

 would


> cause confusion

> within the NT network. (we also have Oracle8i databases installed on NT

> servers within the network which need to

> be accessed from each workstation)

> What we want is to be able to create an image, then when copied to another

> machine,with different machine name,

> change the node name within Oracle for that machine, which will also

 change


> all the Oracle services.

>

> Thanks

>

> Trevor

>

> Paul Drake <paled_at_home.com> wrote in message

> news:3B23BA4C.3F692DFB_at_home.com...

> > Trevor Bell wrote:

> > >

> > > I am trying to install Oracle 8i onto a workstation.  This computer is

 to be


> > > used for taking an image for putting on all the computers in the

 office.


> > > The problem that I have is that Oracle8i automatically takes the

 computer


> > > name as the node name.  Once this has happened I can find no way of

 changing


> > > the node name.  I am also unable to change the computer name because

 if
 I do


> > > I can't start the Oracle services because of the name conflicts.  Does

> > > anyone know how to change either the default of computer name being

 taken,


> > > or how to change the computer name after the install or the node after

> > > install so that imaging software an be used.  Otherwise all the

 computers


> > > will have the same name and the same node and hence their host will be

 the


> > > same making it impossible to change the tnsnames file to log onto

 another


> > > computers database.

> > >

> > > --

> > >

> > > Trevor

> > > POWERtec Systems and Consultancy Ltd

> > > Tel: 0118 935 0009     Fax: 0118 935 0001

> > > www.powertec.co.uk

> >

> > Do you mean that you are installing Oracle 8i Server on each

> > workstation?

> > If you are installing the Oracle 8i Client, the same tnsnames.ora file

> > can be used, as the workstations will be connecting to the same

> > server(s) - not the local host.

> > Also - if you are installing clients - there are no services to be

> > created.

> >

> > If you are cloning Oracle Servers, you could run post-cloning scripts to

> > rename the local database(s).

> > Basically, you create a backup controlfile to trace, edit the file to

> > rename the database and execute it (nomount) to create a new

> > controlfile.

> > You can have the same ORACLE_SID on different servers in the same

> > domain, but the global database name (service_name) should be unique.

> > As the same OracleService%ORACLE_SID% can be used on each workstation -

> > I don't see the problem here.

> > This just means that the ORACLE_SID != v$database.name.

> > I believe that if you use a service name of

> > <v$database.name>.<hostname>.<domain_name>

> > e.g. dev.quaddamage.mydomain.com that you could still have the same

> > db_name on each host.

> >

> > hth,

> >

> > Paul

>

>