![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 2292422.1 : Oracle Key Manager (OKM) - Any KMA Running 3.x Code Version Prior To 3.3 Will Get An Error On Future OKM Software Downloads After November 12 2017
In this Document
Applies to:Oracle Key Manager - Version 3.0 and laterInformation in this document applies to any platform. GoalOKM 3.3 Digital Signing Notes All OKM 3.x software upgrade releases are digitally signed. Due to a bug in the signature verification process, any 3.x code version prior to 3.3 will get an error on the download after November 12 2017. SolutionWhat this means is the following: 1) Any customer running below 3.3 will not be able to upgrade to the 3.3 version after November 12 2017 without assistance from Oracle Level 2 Support or a Field Engineer onsite to manually upgrade the code. 2) Any customer that is below version 3.3 and wants to stay on their current version can do so but with the knowledge that if they want to upgrade at a date after Nov 12 2017 manual intervention will be required by Oracle Level 2 support or a Field Engineer will need to be dispatched for this action. 3) Once an OKM is running on version 3.3 it can be upgraded to future versions without any further manual intervention. Standard upgrade procedures would apply. 4) Hard Disk Drive(HDD) FRUs - All HDD's are imaged with software that is below version 3.3 at this time. If a HDD fails, the code upgrade process varies depending on what version the customer was previously running on and what version they want to run on. X4170 M2 500GB Disk Drive 542-0371 with KMS 2.3.1 = FRU 542-0410 NS T4-1 OKM 3.0 Preloaded HDD = FRU 7087722 Sparc T7-1 OKM 3.1 Preloaded HDD = FRU 7331569 Reference KB 1492060.1 T7 T4 4170 x2100 and x2200 Attachments This solution has no attachment |
||||||||||||||
|