How To
Summary
When a customer performs an upgrade from 8.5.x to 8.6 AND they decide to re-encrypt the DB at the same time i.e. in parallel, an error is thrown on the Maxinst pod when validating the crypto keys. The java stack trace is pasted in the "Additional Information" section. The reason for this error is the new Crypto Keys provided by the customer are not copied to the maximo.properties file. Therefore, when Manage tries to re-encrypt again with the old keys the crypto logic throws the error.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite-\u003EMAS Applications-\u003EManage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.0;8.6.0"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
28 March 2023
UID
ibm16965770