Re: Renamed db refuses SQL*Net connection

andrew.nelson_at_astramerck.com wrote:
>
> In article <337FA343.323A_at_comsense.com>,
> leng_at_comsense.com wrote:
> >
> > Hello all,
> >
> > Env: OSF 3.2, RDBMS 7.3.2.1, SQL*Net 2.3.2.1
> >
> > My database has just been renamed by recreating the controlfile.
> > Now I've found that not only is the global_name not
> > reflecting the new database name, now I can't connect to it via
> > sql*net. I can connect to new database using a direct connection
> > "sqlplus /" and when querying v$database I can see the new database
> > name. But when I do "sqlplus /@new" it fails with ORA-00472: PMON
> > process terminated with error. This error also occurs on any client
> > that wishes to connect to the new db view sql*net. No, we're not
> > using Oracle Names, just plain old sql*net.
> >
> > Doing a "ps-fe | grep pmon" shows that pmon is certainly alive. And
> > there are no trace files generated, or any entries in the alert.log.
> >
> > I've restarted the listener (with the new name) and bounced the
> > database a couple of times already. TNSNAMES.ORA has also been
> > changed. So the question for you guys out there is: after renaming a
> > database, did you have problems connecting via sql*net?
> >
> > Thanks.
> > Leng.
> > -------
> > Leng Kaing - leng_at_comsense.com
> > Common Sense Consulting
> > Tel: +61-3-9885-5829 Fax: +61-3-9885-0116
> > VOUG: http://dingo.vut.edu.au/voug
>
> Did you remember to change LISTENER.ORA on the server where the
> database resides? If not, change it and either start/stop sqlnet
> or reload sqlnet on that server.

also did you issue an alter database rename global_name to <NEWDB.SERVER>.

Dick Allie - dallie_at_ionet.net

>
> -------------------==== Posted via Deja News ====-----------------------
> http://www.dejanews.com/ Search, Read, Post to Usenet
Received on Wed May 21 1997 - 00:00:00 CDT