We have two X4 and two X5 ODAs currently, all with 11gR2 DBs. We'll soon
receive two X8s, sadly with only the minimum storage - 6.4 duplexed storage.
Our major vendor-supplied apps, like Student Information System, are OK with
19c (12cR2), so we just need a migration plan.
So far our plan is to pre-create the 19c DBs on the new X8s and get all the
pieces - tablespaces, user accounts, etc. - in place before a final downtime to
export all data from old DB and import into new DB. That shouldn't take
terribly long, as we export to a Flash SAN and the X8s are SSD storage.
Since we can now have up to 3 PDBs in one CDB without extra licensing, we're
thinking of going that route, as three of our DBs are intertwined via DB links
and we constantly see that as the main wait event in them. Is this a good idea
or should we have 3 CDBs each with a single PDB? We have zero experience with
the whole CDB/PDB architecture, so only know what we've read.
We'll have to migrate the X5 DBs (all Prod) to the X8s, then reimage the X5s to
19c, then migrate the X4 DBs (all Dev and Test) to the X5s. Then we'll
re-purpose or retire the X4s, as our support has ended for them.
Any recommendations, guidance, or warnings anyone can share would be greatly
appreciated.
TIA
--
Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)
I cannot help but notice that there is no problem between us that cannot be
solved by your departure. -- Mark Twain
Confidentiality Notice: This email message, including all attachments, is for
the sole use of the intended recipient(s) and may contain confidential student
and/or employee information. Unauthorized use of disclosure is prohibited under
the federal Family Educational Rights & Privacy Act (20 U.S.C. §1232g, 34 CFR
Part 99, 19 TAC 247.2, Gov't Code 552.023, Educ. Code 21.355, 29 CFR
1630.14(b)(c)). If you are not the intended recipient, you may not use,
disclose, copy or disseminate this information. Please call the sender
immediately or reply by email and destroy all copies of the original message,
including attachments.