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 126.96.36.199.5 before (or I used to call it 188.8.131.52.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 … 184.108.40.206.5
- Now: Oracle Database 12c PSU January 2016 … 220.127.116.11.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
18.104.22.168 Patch Set Updates – List of Fixes in each PSU
- MOS Note:21948354.8
Bug 21948354 – 22.214.171.124.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
126.96.36.199 Patch Set – Availability and Known Issues
- MOS Note:1562139.1
188.8.131.52 Patch Set – Availability and Known Issues
- Oracle Security Blog
184.108.40.206.160119 160119 is an international dat format not us.
YYMMDD (or YYYYMMDD) is international.
MMDDYY (or MMDDYYYY) are us.
thanks – my fault 🙂
Hi Mike ,
Our 12c production environment has 2 databases prod1 and prod2(same Oracle Home).
PSU 5 was applied but only prod1 was datapatched.
What about prod2 , is it in hybrid situation ?
Is it normal to patch only kernel and not instance (datapatch) ?
please see here:
It should be very straight forward:
run datapatch -verbose afterwards.
The January 2016 BP is not available as QFSDP for Exadata as yet. Do you happen to know if there is always a delay in QFSDP availability? I am looking at MOS Doc ID 888828.1 and there is no mention of Jan 2016 QFSDP.
Comming soon – please be patient 😉
Hi Mike ,
Do you recommend specific action after installing a PSU , like gathering system or dictionary statistics …?
nothing is necessary as the PSU does not change configuration or behavior.
This patch p22310559_121020_WINNT is not applicable for Oracle SE2 220.127.116.11.0.
I still could not see any latest windows patch for Oracle SE2 18.104.22.168.0.
Please let me know if there are any latest patch.
The only that I have apply is the full version of patch set p21419221_121020_MSWIN-x86-64.
Tried to apply the Oracle Database 12c PSU January 2016 … 22.214.171.124.160119 into our Oracle SE2.
Verifying environment and performing prerequisite checks…
Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
The details are:
Patch ( 22310559 ) is not applicable on current platform.
Platform ID needed is : 233
Platform IDs supported by patch are: 215 207 912 100
Why the reason this patch for p22310559_121020_WINNT.zip is not for Oracle SE2?
I feel very sorry when reading about your approach. Please log an SR immediately as this IS SUPPOSED TO WORK. I can only guess that it is a problem in the patches metadata.
As far as my understanding goes that PSU must be applicable on SE2 as well as there are no specific patch set updates built for SE2.
Sorry for all the inconvenience – that is not funny …
Please confirm me , this patch is applicable to 126.96.36.199.0 GRID infrastructure 2 Node RAC database .
for the correct BP for your GI version.