Re: Curious question - naming CDBs and PDBs

Thanks Seth - initially we'll definitely have 1:1 CDB:PDB setup. Eventually we may license the multi-tenant option so I was just thinking through some of the "ins and outs" about future state what will make some logical sense when viewed at a high level.

Thank you for your input!

Chris

On Fri, Jul 15, 2016 at 2:55 PM, Seth Miller <sethmiller.sm_at_gmail.com> wrote:

> Chris,
>
> My customers that are migrating to 12c CDB but don't have the multitenant
> license have a one to one relationship between their CDB and PDB. They
> generally preserve the original database name for the PDB and add a C to
> the end of the database name. I would caution adding CDB to the end of the
> database name for the exact reason that Jay's example of using TVPRODCDB
> would not work. 12.1 still imposes an eight character limit on the database
> name.
>
>
> Seth Miller
>
> On Fri, Jul 15, 2016 at 1:55 PM, John Mchugh <john.mchugh_at_oracle.com>
> wrote:
>
>> If I may offer some guidance here based on Oracle internal experience and
>> customer deployment experiences....
>>
>> differentiate container from content. The container name CDB/SID, should
>> be an abstraction that should reflect ownership (ex. LOB), or geographic
>> location or version or some attribute specific to the container such as
>> service level, etc... The PDB name should reflect content and deployment
>> use (prod, test, dev, UAT...). The point here really is that you don’t want
>> to bind the PDB name to the hosting container as that could change.
>>
>> This is not hard and fast policies but intended as guidance. Keep it
>> simple and try to preserve these distinctions and where possible, global
>> uniqueness in naming conventions.
>>
>> hope this helps,
>> jpm
>>
>>
>>
>>
>>
>> I struggled with this as well. I was going to try something like
>> TVPRODCDB, but the pdbs may not relate as you stated. I ended up keeping
>> the pdb names the same as the database name from prior versions (e.g.
>> TVPROD), this way the applications could use the same tns entry. Of course
>> the tns entries can be called anything you like but I like for them to
>> match the container name for clarity sake. The cdb name I named similar to
>> the host server (e.g. PRODSERVDB01). Which of course is generic and
>> confusing but allows for the cdb name to be unrelated to its pdbs. I spent
>> way too much time thinking about this, but I like having consistent naming
>> conventions. I'm still not happy with the cdb name, but it was the best I
>> could come up with.
>>
>> Jay
>>
>> Sent from my iPhone
>>
>> On Jul 15, 2016, at 2:22 PM, Chris Taylor <
>> christopherdtaylor1994_at_gmail.com> wrote:
>>
>> Out of curiosity, how do you guys name your CDBs and PDBs in relation to
>> each other?
>>
>> For example, prior to 12c I might have TV Shows Databases called TVDEV,
>> TVTST, TVPROD.
>>
>> In the CDB/PDB world, I would assume I would name my PDBs TVDEV, TVTST,
>> TVPROD and I would NOT have them in the same container as they would exist
>> on dedicated dev, test, prod servers.
>>
>> So I'm what some of you guys are doing - I realize the CDB is the
>> instance name so for single PDB tenant databases, I would probably call
>> both the container and the PDB TVPROD (but I'm betting they have to be
>> different names?)
>>
>> In a world of disparate PDBs in one container, I might call my container
>> MISHMASH since the container may not really relate to the individual PDBs
>> it contains.
>>
>> Chris
>>
>>
>>
>>
>

--
http://www.freelists.org/webpage/oracle-l