Re: upgrade client on XP, how should the registry look?

From: shakespeare <whatsin_at_xs4all.nl>
Date: Tue, 5 Feb 2008 16:26:29 +0100
Message-ID: <47a88028$0$85783$e4fe514c@news.xs4all.nl>

"Ben" <benalvey_at_yahoo.com> schreef in bericht news:522c29a5-7498-4480-9f74-6c67022365de_at_d21g2000prf.googlegroups.com... On Feb 5, 9:23 am, "shakespeare" <what..._at_xs4all.nl> wrote:
> "Ben" <benal..._at_yahoo.com> schreef in
> berichtnews:7505c5e8-6f63-4989-a634-0682b0c034c8_at_f47g2000hsd.googlegroups.com...
>
> > We recently upgraded to 10.2.0.2 from 9.2.0.5 and with the client
> > upgrades we uninstalled 9.2 first and then installed & patched
> > 10.2.0.2.
> > We've had some random problems on an application server and with that
> > I decided to check the registry for oracle information. I found that
> > under local_machine->software->oracle the keys all have the old 9.2
> > information. There is then a sub folder local_machine->software-
> >>oracle->KEY_OraClient10g_1 with all the 10g information. All the
> > environment variables ORACLE_HOME, TNS_ADMIN, PATH have the 10g info.
>
> > Is it supposed to be required to manually remove all the 9i
> > information from the registry?
>
> Is this the client registry or the server registry?
>
> Shakespeare

client.

our database is on a unix server. most of our clients are windows XP machines.


I don't see what an oracle client has to do with application server. Where is it? Is it a seperate server? The only connection to the DB will be done by the application server, so your client config should not be the issue here.

But on the client, after de-installing the 9 version, all entries should have been removed from the registry, which obviously didn't happen... I don't think removing them would hurt. The 10g registry entries are in the right place, it's normal they are placed there. Actually, you can remove all entries at the higher level, EXCEPT the inst_loc entry, which points to your inventory (if it's there).

Shakespeare Received on Tue Feb 05 2008 - 09:26:29 CST

Original text of this message