Thanks for the question, Nell.
Asked: June 21, 2016 - 3:14 am UTC
Answered by: Connor McDonald - Last updated: June 23, 2016 - 2:21 am UTC
Category: Database - Version: Oracle 12c
Viewed 1000+ times
I have an Oracle 12c running on AWS on CentOS Linux rel 7.1. The database has been installed as a standalone non-CDB database. This DEV database is used for development. I have to install a second environment, for QA, on the same server. This time I want to use Container DB/Pluggable DB feature of 12c.
I think here is what my plan should be:
- Install a separate Container database
- Create the QA database as a first PDB
- Convert the standalone DEV database to become a second PDB
- To create this Container/Pluggable databases, do I have to run a separate Oracle installation? Can I create it as another database within the existing Oracle Home?
- Can Container/Pluggable databases installation be placed in the same Oracle Home as the standalone DEV, or a separate Home needs to be created?
- The DEV was installed using "oracle" account. There is a .bash_profile defining the instance for the "oracle" user. Do I have to create another user, say "oracle_qa", and use it for the second installation? Would oracle install run if I use non-"oracle" user? Or I have to run the second installation as "oracle", but somehow switch between the instances before I start the install process? would both installations, DEV and QA, run under "oracle" user if i use it for both installs?
The install runs using a response file, db_install.rsp, there is no graphics.
Your suggestions are appreciated!
and we said...
You do not need another software installation. For example, on my laptop here I have one installation of 12c software, and have
Is this answer out of date? If it is, please let us know via a Review
- one non-pluggable database
- one container with 2 pluggables within it
so I can test things in both scenarios.
Similarly, this can all be done under a common user account (eg oracle) if you choose. Simply settings the ORACLE_SID environment variable (and running oraenv/coraenv) determines which of the databases you wish to talk to.
(In the pluggable circumstance, you'd be using a service name as well, ie connect myuser/mypass@pluggable_service_name)
Hope this helps.