ORA-7445 [__longjmp()+78] and ORA-600 [kztsmdml:key Hash Too Long], [52372] When Setting the TDE Encryption Key (Doc ID 2064341.1)

Last updated on NOVEMBER 03, 2015

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Advanced Networking Option - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

ORA-7445 encountered when setting the TDE encryption key

Issue:
-- create master key
administer key management create encryption key using tag 'DBORA5T_MASTER_KEY' identified by "******" with backup using 'Create-MK-DBORA5T';
-- get the key_id
select key_id from v$encryption_keys;
-- activate key
administer key management use encryption key 'AS1W8wbIz0/Vv+2JzYiFxOoAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' using tag 'DBORA5T_MASTER_KEY' identified by "******" with backup using 'Active-MK-DBORA5T';

Activating the key fails with:
ORA-07445: exception encountered: core dump [__longjmp()+78] [SIGSEGV] [ADDR:0x0] [PC:0x7F886D8E674E] [SI_KERNEL(general_protection)] []
ORA-00600: internal error code, arguments: [kztsmdml:key hash too long], [52372], [], [], [], [], [], [], [], [], [], []

Incident trace file displays:

[TOC00000]
Jump to table of contents
Dump continued from file: /ade/b/2284577791/oracle/log/diag/rdbms/x0/x0/trace/x0_ora_21316.trc
[TOC00001]
ORA-07445: exception encountered: core dump [__longjmp()+66] [SIGSEGV] [ADDR:0x0] [PC:0x3F4B830122] [SI_KERNEL(general_protection)] []
ORA-00600: internal error code, arguments: [kztsmdml:key hash too long], [52372], [], [], [], [], [], [], [], [], [], []

[TOC00001-END]
[TOC00002]
========= Dump for incident 2706 (ORA 7445 [__longjmp]) ========
[TOC00003]
----- Beginning of Customized Incident Dump(s) -----
Dumping swap information
Memory (Avail / Total) = 15.00M / 7800.00M
Swap (Avail / Total) = 5401.35M /  10047.30M
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x3F4B830122, __longjmp()+66] [flags: 0x0, count: 1]
Registers:
%rax: 0x0000000000000258 %rbx: 0x0000000000000000 %rcx: 0x0000000000000000
%rdx: 0xad8b5f850e5d1b3d %rdi: 0x00007fff94a909d0 %rsi: 0x0000000000000258
%rsp: 0xad8b5f850e5d1b3d %rbp: 0xad8b5f850e5d1b3d  %r8: 0xad8b5f850e5d1b3d
 %r9: 0xad8b5f850e5d1b3d %r10: 0x0000000000000001 %r11: 0x0000003f4c40d330
%r12: 0x0000000000000000 %r13: 0x0000000000000000 %r14: 0x0000000000000000
%r15: 0x0000000000000000 %rip: 0x0000003f4b830122 %efl: 0x0000000000010282
  __longjmp()+54 (0x3f4b830116) mov 0x28(%rdi),%r15
  __longjmp()+58 (0x3f4b83011a) mov %esi,%eax
  __longjmp()+60 (0x3f4b83011c) mov %r8,%rsp
  __longjmp()+63 (0x3f4b83011f) mov %r9,%rbp
> __longjmp()+66 (0x3f4b830122) jmp *%edx
  __longjmp()+68 (0x3f4b830124) nop
  __longjmp()+69 (0x3f4b830125) nop
  __longjmp()+70 (0x3f4b830126) nop
  __longjmp()+71 (0x3f4b830127) nop

*** 2015-10-07 05:44:08.374
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
[TOC00004]
----- Current SQL Statement for this session (sql_id=2jgx34jwgw0kh) -----
administer key management use encryption key
'AXeSBjDcgE8Av8P3og6AdvsAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
using tag 'DBORA5T_MASTER_KEY' identified by *with backup using 'Active-MK-DBORA5T'
[TOC00004-END]

In the call stack trace section the following may be seen:

__longjmp()+66       signal   __sighandler()       7FFF94A909D0 000000258
                                                   AD8B5F850E5D1B3D 000000000 ?
                                                   AD8B5F850E5D1B3D ?
                                                   AD8B5F850E5D1B3D ?
*************v
Unable to complete stack trace past the above frame.  The follwoing frames
are the result of searching for a call chain and are not certain.
*************^

.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms