Re:Yandex.Mail's successful migration from Oracle to Postgre...
by acdha on Tuesday September 13, 2016 @05:40PM
(#12492504)
What's Oracle's patch deployment strategy now? The last time I had to deal with it was around 2008, when a security update was a tarball with a README file telling you which files to copy where. I've heard it's improved considerably since then.
[ Parent
| on HN ]
Re:Yandex.Mail's successful migration from Oracle to Postgre...
by randomnerdiness on Tuesday September 13, 2016 @06:01PM
(#12492631)
Not a ton different, if you've used OPatch already. Basically it copies around files, runs a bunch of perl, runs a bunch of sql, and then you run the usual patch upgrade scripts at the end. The in-place patching is safer and smoother in 12c than it was in 11g, but the cumulative patching has really gotten out of hand.
For example - on a QA system we were running a couple of custom one-off patches delivered by Oracle Support. These blew up the entire patch process. I had to stop, back them out, re-patch, then re-apply the one-off patches.
Oh, and 12c is a seriously whiny bitch about XDB. Just for added fun.