About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Technical Blog Post
Abstract
SQL1782N on Create Database with encrypt option if Master Node is down
Body
When we have Database Encryption is setup with Master-Clone node in KeySecure.
If Master Node is down,we may get error while Creating database.
When MASTER Node is down in Kesecure:
db2 create db test encrypt
SQL1782N The command or operation failed because an error was encountered
accessing the centralized key manager. Reason code "5:111".
A new master key is automatically added when you create an encrypted database without
specifying the MASTER KEY LABEL option on the CREATE DATABASE command.
Clone servers are considered read only and are only used for retrieving
existing master keys from the centralized keystore. Clone servers are not used when
inserting a new key.
Workaround:
a) Set your master server to your clone IP.
b) Create the master key on KeySecure ahead of time when Master is available before using create db.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
UID
ibm13286155