[DERBY-5976] Document the new SQLWarning raised when trying to change the encryption state of an already booted database.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.1.1
• Component/s: Documentation
• Urgency: Normal
• Assignee: Camilla Haase
• Reporter: Richard N. Hillegas
• Created: 01/Nov/12 14:40
• Updated: 24/Jan/13 16:22
• Resolved: 06/Nov/12 17:51

Description

After committing derby-5969-01-aa-warnEncryptionOnBootedDB.diff, we will want to adjust the user guides to clarify the following point:

o If you are changing the encryption state of the database, be sure to check for SQLWarnings after the change. The change succeeded only if there were no SQLWarnings or SQLExceptions.

I think that the following sections need to be touched up:

Developer's Guide:

o "Encrypting an existing unencrypted database"

o "Encrypting databases with a new boot password"

o "Encrypting databases with a new external encryption key"

o "Decrypting an encrypted database"

Reference Manual:

o "dataEncryption=true attribute"

o "newBootPassword=newPassword attribute"

o "newEncryptionKey=key attribute"

o "decryptDatabase=true attribute"

Issue Links

• relates to: DERBY-5969 Encryption, re-encryption, and un-encryption silently fail if the database is already booted.