Re: EZCONNECT problem with Oracle11 (solved)
From: Mladen Gogala <mgogala_at_yahoo.com>
Date: 25 Mar 2008 13:25:43 GMT
Message-ID: <47e8fd57$0$1342$834e42db@reader.greatnowhere.com>
>> This is solved. As it turns out, it isn't a bug but a feature. On
>> Oracle10g and previous releases, the client was specifying the service
>> name. On oracle11 and later, one should specify default service for the
>> listener by using DEFAULT_SERVICE_<listener_name> directive in the
>> listener.ora. That means that the default service can now be configured
>> and that, if the target database is 11g or later, one doesn't need to
>> modify the service_names parameter to make certain database the default
>> one.
>>
>> --
>> Mladen Gogalahttp://mgogala.freehostia.com
Date: 25 Mar 2008 13:25:43 GMT
Message-ID: <47e8fd57$0$1342$834e42db@reader.greatnowhere.com>
On Tue, 25 Mar 2008 06:13:57 -0700, hpuxrac wrote:
> On Mar 25, 5:40 am, Mladen Gogala <mgog..._at_yahoo.com> wrote:
>> This is solved. As it turns out, it isn't a bug but a feature. On
>> Oracle10g and previous releases, the client was specifying the service
>> name. On oracle11 and later, one should specify default service for the
>> listener by using DEFAULT_SERVICE_<listener_name> directive in the
>> listener.ora. That means that the default service can now be configured
>> and that, if the target database is 11g or later, one doesn't need to
>> modify the service_names parameter to make certain database the default
>> one.
>>
>> --
>> Mladen Gogalahttp://mgogala.freehostia.com
> > Is this in reference to something else that you posted? > > If so it doesn't look like your message is connected to an earlier > thread.
It is connected to the thread named:
"Oracle11 bug: EZCONNECT adapter doesn't populate service name".
This is about oracle11 client and name resolution.
-- Mladen Gogala http://mgogala.freehostia.comReceived on Tue Mar 25 2008 - 08:25:43 CDT