Last night the PSUs and BPs for January 2016 have been made available for download on support.oracle.com.
Oracle Critical Patch Update Advisory – January 2016
It contains 248 security fixes across all products and platforms. And of course important non-security fixes – and that’s why we recommend to apply the PSUs (or the BPs in case you are on Exadata or an Oracle In-Memory user) as soon as possible.
Change in Patch Numbering
Please be aware that as of November 2015 there’s been a change in patch numbering introduced which most of you may not be aware of. A database PSU was named 184.108.40.206.5 before (or I used to call it 220.127.116.11.PSU5 before to make clear that a PSU and not a BP has been applied). But the new notation will change the 5th digit to a 6-digit-number to include the date. See MOS Note:2061926.1 for details.
- Before: Oracle Database 12c PSU October 2015 … 18.104.22.168.5
- Now: Oracle Database 12c PSU January 2016 … 22.214.171.124.160119
- MOS Note:2074802.1
Patch Set Update and Critical Patch Update January 2016 Availability Document
- MOS Note:2076309.1
Critical Patch Update January 2016 Database Known Issues
- MOS Note:1924126.1
126.96.36.199 Patch Set Updates – List of Fixes in each PSU
- MOS Note:21948354.8
Bug 21948354 – 188.8.131.52.160119 (Jan 2016) Database Patch Set Update (DB PSU)
- MOS Note:2061926.1
Oracle Database, Enterprise Manager and Middleware – Change to Patch Numbering from Nov 2015 onwards
- MOS Note:756671.1
Oracle Recommended Patches — Oracle Database
- MOS Note:1683799.1
184.108.40.206 Patch Set – Availability and Known Issues
- MOS Note:1562139.1
220.127.116.11 Patch Set – Availability and Known Issues
- Oracle Security Blog