- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 68 Insurance
- 536.9K On-Premises Infrastructure
- 138.5K Analytics Software
- 38.6K Application Development Software
- 5.9K Cloud Platform
- 109.5K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
Using PDBs in Refresh Manner
Hello. Not new to Oracle or OTN, but fairly new to multi tenant architecture. I have done alot of reading of Oracle docs, MOS, blogs, etc., but have a few general questions OPERATIONALLY. Here's what I know and have done:
1.) We are using Oracle 12.1..0.2 (not 12.2) on a RAC configuration as well as ASM on all our HW.
2,) Put a non-CDB DB (named golddb) in READ only mode on Server 1 and created it's XML manifest.
3.) With the DB down, sftp-copied all of the data and temp files for glddb along with the manifest from Server 1 to Server 2. I will not need Server 1 any more at this point. All work will be Server 2-centric.
4.) Installed oracle 12.1.2. on Server 2 and with it came all of the prouct options (as I could not select or deselect any)
5.) Patched Server 2 with the same patches I had on Server 1.
6.) Created a CDB named cdb1 on Server 2 via dbca but created it w/o any PDBs.
7.) Created PDB named pdb1 inside cdb1 using the manifest from Server 1's non-PDB glddb (NOTE: not ALL products were installed in golddb like they were in cdb1)
Excluding PDB$SEED, we will only ever have two PDBs in cdb1. pdb1's contents will NEVER be touched/modified. My hope is that we can have a TEST environment on Server 2 where testers can change a second PDB named pdb2 (not yet created but 'copied' from pdb1 and also residing in cdb1) after which it (i. e., pdb2) can be unplugged and the datafiles removed. Then we could turn around and plug in pdb2 again using the XML manifest and the still-unchanged files in ASM from pdb1.
Here are my questions:
1.) MOST IMPORTANTLY, does this make approach sense and will it work operationally?**
2.) What would the HIGH LEVEL COMMAND(s) look like for:
a.) Copying pdb1 over to pdb2
b.) Unplugging pdb2 after TEST has modified it and then re-plugging it back in as pdb2 Again but with COPIES of pdb1's UNCHANGED data/temp files?
** I know there are many options with the CREATE PLUGGABLE DATABASE and ALTER PLUGGABLE DATABASE commands (e. g., SOURCE_FILE_NAME_CONVERT), just looking for agreement and some general syntax of a few commands if this scenario is feasible.