Database

Get Involved. Join the Conversation.

Topic

    Robin Chatterjee
    Non CDB/PDB databases for Exadata Cloud at CustomerAnswered
    Topic posted August 16, 2018 by Robin ChatterjeeBlack Diamond: 60,000+ Points, last edited November 13, 2018 by Arijit ChakrabortyBronze Trophy: 5,000+ Points, tagged Exadata 
    298 Views, 2 Comments
    Title:
    Non CDB/PDB databases for Exadata Cloud at Customer
    Summary:
    Can we have 12C Non CDB databases hosted on An Exadata Cloud Machine
    Content:

    We have 12c Databases which are non CDB on Premise supporting various applications. We are now thinking of Migrating them to Exadat Cloud Machine. Previously it was Discussed on these forums that In Oracle Cloud we cannot have non PDB/CDB databases for 12.1 or 12.2

    I would like to understand if this restriction is there for Exadata cloud@customer also or we are able to create non PDB 12c databases. It looks like the front end forces input of CDB and PDB name during DB creation.

     

    Best Comment

    Kasey Parker

    Hi Robin - 

    The cloud tooling for Exadata cloud@customer, just like Exadata Cloud Service or any other Oracle DBaaS offerings only supports a CDB architecture for 12c+ databases. Making a 12c+ database instance non-CDB on any of these environments removes all cloud tooling capabilities and is strongly advised against.  

    Comment

     

    • Kasey Parker

      Hi Robin - 

      The cloud tooling for Exadata cloud@customer, just like Exadata Cloud Service or any other Oracle DBaaS offerings only supports a CDB architecture for 12c+ databases. Making a 12c+ database instance non-CDB on any of these environments removes all cloud tooling capabilities and is strongly advised against.  

    • Robin Chatterjee

      Though it may be strongly advised against is it forbidden ? if we create the dataabse from the console then drop them from the backend and create new non pdb databases with the same names would oracle support this ? the reason is many databases have not been tested withPDB and third party vendors often have not done the requisite testing and certifiation...

      So we would like to migrate like for like ...