Re: DB12c in Production?

  • From: John McHugh <john.mchugh@xxxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Mon, 19 May 2014 21:14:42 -0700

12c: USE_SID_AS_SERVICE_listener_name <>


To enable the system identifier (SID) in the connect descriptor to be interpreted as a service name when a user attempts a database connection. Database clients with earlier releases of Oracle Database that have hard-coded connect descriptors can use this parameter to connect to a container or pluggable database.

When the database is an Oracle Database 12c container database, the client must specify a service name in order to connect to it. Setting this parameter to on instructs the listener to use the SID in the connect descriptor as a service name and connect the client to the specified database.





addresses the SID/SERVICE connect descriptor for Multitenant.


On 5/19/2014 3:17 PM, Jeff Smith wrote:
Then there are the myriad of folk who connect using @{SID} instead of @{Service}
Yup, I'm already seeing this a lot. It's the first thing I ask a user to check 
when they have a login issue with 12c.

-----Original Message-----
From: Hans Forbrich [mailto:fuzzy.graybeard@xxxxxxxxx]
Sent: Monday, May 19, 2014 5:22 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: DB12c in Production?

On 19/05/2014 12:14 PM, Seth Miller wrote:
Those of us that don't have the luxury of connecting with "/" or "as
sysdba" will find it easier to adjust.
To a certain extent.

Then there are the myriad of folk who connect using @{SID} instead of @{Service}

... remembering that each database has a unique service within the container, 
and TNSNAMES.ora is not necessarily updated, and oratab can no longer be 
twisted to help a lot.



Other related posts: