Unless you’re in a cave asleep, you’ve seen the recent Oracle PSUs and patches that were released in January. This has many of my customers patching their agents, and a few have noticed a problem with some previously applied patches. Thanks to Brian for pointing this out!
Just a quick note here to say I’ve added a new blog post to the official Enterprise Manager blog site. You can find it here.
RMOUG Training Days – Feb 17-19 (Denver)
This is a great regional Oracle User’s Group conference with some of the best speakers you’ll find on multiple subjects! Something enticing about being in freezing cold temperatures during ski season I think? My colleague Kellyn Pot’vin-Gorman does a great job promoting it and making sure people get a great educational experience.
Oracle’s sample schemas are an extra download. For Oracle 12c, the sample schemas are in file 7 of 8 of the downloads. So if you want the sample schemas, you have to go to OTN or Metalink for the patchset version and download the file.
Someone also posted the sample schemas on GitHub here: https://github.com/oracle/
I was made aware of this today: Note 1951018.1 SQLT Utility and Partitioning Tables
The person who pointed this out was afraid that they would be violating licensing if they used SQLT, which would create partitioned tables. If you read the note carefully, SQLT will only create partitioned tables if you have Partitioning installed and enabled. If you aren’t licensed, why is this installed? Installing an unlicensed option is a very easy way to have someone accidentally use it and get yourself caught in an audit.
Every time a new plug-in, patch or PSU comes out for Enterprise Manager, I get a series of questions. I’m going to quickly address a few of the ones I’ve gotten this month with the release of the new plug-ins and the PSU patches to try and help you in updating your EM site. I wrote a detailed blog EM Patching 101 about the various patches, and that’s still relevant so read if you haven’t (or read it again)!
Oracle 12c deprecates the SEC_CASE_SENSITIVE_LOGON parameter. It is still there for backwards compatibility. But Oracle would like to see everyone use case sensitive logons in the future.
The one thing that did surprise me was when I recently upgraded a test db from 220.127.116.11 to 18.104.22.168 using the DBUA. At the end of the DBUA, I got this information in the Post Upgrade results: