My Oracle Support Banner

ORA-28374: Typed Master Key Not Found In Wallet During ASM Migration with RMAN (Doc ID 1934374.1)

Last updated on APRIL 09, 2018

Applies to:

Advanced Networking Option - Version 11.1.0.7 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.0.7 version, Transparent Data Encryption

When attempting to Migrated datafiles to ASM storage on the same server.
the following error occurs.

ERROR
-----------------------
ORA-28374: typed master key not found in wallet


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Full backup

rman target /

RUN
{
 ALLOCATE CHANNEL dev1 DEVICE TYPE DISK;
 ALLOCATE CHANNEL dev2 DEVICE TYPE DISK;
 BACKUP AS COPY
  INCREMENTAL LEVEL 0
  DATABASE
  FORMAT '+DATA'
  TAG 'ORA_ASM_MIGRATION';
}

(2) Incremental Applied backup

rman target /

RUN
{
 BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'ORA_ASM_MIGRATION' DATABASE;
 RECOVER COPY OF DATABASE WITH TAG 'ORA_ASM_MIGRATION';
}

(3) Update database parameters and shutdown

ALTER SYSTEM SET DB_CREATE_FILE_DEST='+DATA' SCOPE=SPFILE SID='*';
ALTER SYSTEM SET DB_CREATE_ONLINE_LOG_DEST_1='+REDO_01' SCOPE=SPFILE SID='*';
ALTER SYSTEM SET DB_CREATE_ONLINE_LOG_DEST_2='+REDO_02' SCOPE=SPFILE SID='*';
ALTER SYSTEM SET CONTROL_FILES='+DATA','+DATA' SCOPE=SPFILE SID='*';

ALTER SYSTEM ARCHIVE LOG CURRENT;
ALTER DATABASE DISABLE BLOCK CHANGE TRACKING;
SHUTDOWN IMMEDIATE;

(4) Switch control file to ASM

RMAN> STARTUP FORCE NOMOUNT;

Oracle instance started

Total System Global Area 2087780352 bytes

Fixed Size 2161272 bytes
Variable Size 1157629320 bytes
Database Buffers 922746880 bytes
Redo Buffers 5242880 bytes

RMAN> RESTORE CONTROLFILE FROM '/export/data/DBATEST1/control01.ctl';

Starting restore at 29-SEP-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=261 device type=DISK

channel ORA_DISK_1: copied control file copy
output file name=+DATA/dbatest1/controlfile/current.311.859583685
output file name=+DATA/dbatest1/controlfile/current.312.859583685
Finished restore at 29-SEP-14

RMAN> ALTER DATABASE MOUNT;

database mounted
released channel: ORA_DISK_1

(5) Switch datafiles to ASM

RMAN> SWITCH DATABASE TO COPY;

datafile 1 switched to datafile copy "+DATA/dbatest1/datafile/system.299.859568545"
datafile 2 switched to datafile copy "+DATA/dbatest1/datafile/sysaux.300.859568571"
datafile 3 switched to datafile copy "+DATA/dbatest1/datafile/undotbs.301.859568595"
datafile 4 switched to datafile copy "+DATA/dbatest1/datafile/xdb.303.859568611"
datafile 5 switched to datafile copy "+DATA/dbatest1/datafile/ipulsar.304.859568613"
datafile 6 switched to datafile copy "+DATA/dbatest1/datafile/quartz.305.859568615"
datafile 7 switched to datafile copy "+DATA/dbatest1/datafile/users.306.859568615"
datafile 8 switched to datafile copy "+DATA/dbatest1/datafile/pulsar.302.859568595"
datafile 9 switched to datafile copy "+DATA/dbatest1/datafile/icosmos.296.859568453"
datafile 10 switched to datafile copy "+DATA/dbatest1/datafile/lobsegments.298.859568545"
datafile 11 switched to datafile copy "+DATA/dbatest1/datafile/cosmos.297.859568453"
datafile 12 switched to datafile copy "+DATA/dbatest1/datafile/cdc_sfs_indx.307.859568617"
datafile 13 switched to datafile copy "+DATA/dbatest1/datafile/cdc_sfs_data.308.859568619"

(6) recover database

RMAN> RECOVER DATABASE;

Starting recover at 30-SEP-14
using channel ORA_DISK_1

starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/30/2014 14:09:44
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed start
ORA-00283: recovery session canceled due to errors
ORA-28374: typed master key not found in wallet

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.