Skip to main content

How to Patch oracle 18c/19c Non RAC (Single Instance) database


<<Back to DB Administration Main Page

How to Patch oracle 18c/19c Non RAC (Single Instance) database

NOTE: Starting from 18c Oracle calls Patch Set Update (PSU), as Release Update (RU).
S
tep1> Download the Patch
Download the patch to be applied from oracle support

 Step2> Transfer the patch on the sever and unzip it using unzip utility
Note: I am using OCT2019 PSU(RU) together with OJVM patch
p30112122_180000_Linux-x86-64.zip  <= OCT DB PSU (DB RU)
p30133603_180000_Linux-x86-64.zip  <= OCT JAVA Patch

 $unzip p30112122_180000_Linux-x86-64.zip -d /OCT_2019_PSU/
$unzip p30133603_180000_Linux-x86-64.zip -d /OCT_2019_PSU/

 Step3> Verify Utility the Opatch version
OPatch Utility:
You must use the OPatch utility version as described in README file for the patch. Oracle recommends that you use the latest released OPatch version for 18c, which is available for download from My Oracle Support patch 6880880 by selecting the 18.0.0.0.0 release.
$export PATH=$PATH:$ORACLE_HOME/OPatch
$opatch version
OPatch Version: 12.2.0.1.17
OPatch succeeded.

Step4> Perform Patch Conflict Detection and Resolution
export ORACLE_HOME=/u01/app/product/18c/db_home
export PATH=$PATH:$ORACLE_HOME/OPatch
cd /OCT_2019_PSU/30112122/
opatch prereq CheckConflictAgainstOHWithDetail -ph ./

cd /OCT_2019_PSU/30133603/
opatch prereq CheckConflictAgainstOHWithDetail -ph ./

 Logs Provided Below "Conflict Resolution Run Log"

 Step5> Apply the patch
To apply the patch shut down all the database listener from the OH you are going to patch
Apply DB PSU
as oracle user
$cd /OCT_2019_PSU/30112122/$opatch apply

 Apply Java Patch

$cd /OCT_2019_PSU/30133603/
$opatch apply

logs for DB patch and JAVA patch provided below 
"DB Patch Run Log"
"JAVA Patch Run Log"

Step6> Start the oracle processes (DB + Listener)
sqlplus /nolog
SQL> Connect / as sysdba
SQL> startup
SQL> alter pluggable database all open;
SQL> quit
$lsnrctl start LISTENER01

 Step7> Load Modified SQL Files into the Database

cd $ORACLE_HOME/OPatch
./datapatch -verbose
Logs provided below "Datapatch Run Log"

 Step8> Run utlrp.slq to compile the invalid Objects
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

=========================================================
Conflict Resolution Run Log

 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 12.2.0.1.17
Copyright (c) 2019, Oracle Corporation.  All rights reserved.
PREREQ session
Oracle Home       : /u01/app/product/18c/db_home
Central Inventory : /u01/oraInventory
   from           : /u01/app/product/18c/db_home/oraInst.loc
OPatch version    : 12.2.0.1.17
OUI version       : 12.2.0.4.0
Log file location : /u01/app/product/18c/db_home/cfgtoollogs/opatch/opatch2019-10-25_09-21-50AM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.

=========================================================

=========================================================
DB Patch Run Log

export ORACLE_HOME=/u01/app/product/18c/db_home
export PATH=$PATH:$ORACLE_HOME/OPatch
cd /OCT_2019_PSU/30112122/
opatch apply
Oracle Interim Patch Installer version 12.2.0.1.17
Copyright (c) 2019, Oracle Corporation.  All rights reserved.
Oracle Home       : /u01/app/product/18c/db_home
Central Inventory : /home/oracle/oraInventory
   from           : /u01/app/product/18c/db_home/oraInst.loc
OPatch version    : 12.2.0.1.17
OUI version       : 12.2.0.4.0
Log file location : /u01/app/product/18c/db_home/cfgtoollogs/opatch/opatch2019-10-25_09-35-06AM_1.log
Verifying environment and performing prerequisite checks...
--------------------------------------------------------------------------------
Start OOP by Prereq process.
Launch OOP...
Oracle Interim Patch Installer version 12.2.0.1.17
Copyright (c) 2019, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/product/18c/db_home
Central Inventory : /home/oracle/oraInventory
   from           : /u01/app/product/18c/db_home/oraInst.loc
OPatch version    : 12.2.0.1.17
OUI version       : 12.2.0.4.0
Log file location : /u01/app/product/18c/db_home/cfgtoollogs/opatch/opatch2019-10-25_09-35-24AM_1.log
Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   30112122
Do you want to proceed? [y|n]
Y (auto-answered by -silent)
User Responded with: Y
All checks passed.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/product/18c/db_home')

Is the local system ready for patching? [y|n]
Y (auto-answered by -silent)
User Responded with: Y
Backing up files...
Applying interim patch '30112122' to OH '/u01/app/product/18c/db_home'
ApplySession: Optional component(s) [ oracle.assistants.server.oui, 18.0.0.0.0 ] , [ oracle.has.crs, 18.0.0.0.0 ] , [ oracle.network.gsm, 18.0.0.0.0 ] , [ oracle.rdbms.tg4db2, 18.0.0.0.0 ] , [ oracle.network.cman, 18.0.0.0.0 ] , [ oracle.crs, 18.0.0.0.0 ] , [ oracle.assistants.usm, 18.0.0.0.0 ] , [ oracle.tfa, 18.0.0.0.0 ] , [ oracle.rdbms.tg4tera, 18.0.0.0.0 ] , [ oracle.rdbms.tg4msql, 18.0.0.0.0 ] , [ oracle.rdbms.tg4ifmx, 18.0.0.0.0 ] , [ oracle.assistants.asm, 18.0.0.0.0 ] , [ oracle.rdbms.tg4sybs, 18.0.0.0.0 ] , [ oracle.ons.daemon, 18.0.0.0.0 ] , [ oracle.options.olap, 18.0.0.0.0 ] , [ oracle.net.cman, 18.0.0.0.0 ]  not present in the Oracle Home or a higher version is found.
Patching component oracle.rdbms.rsf, 18.0.0.0.0...
Patching component oracle.rdbms, 18.0.0.0.0...
Patching component oracle.assistants.acf, 18.0.0.0.0...
Patching component oracle.assistants.server, 18.0.0.0.0...
Patching component oracle.ctx, 18.0.0.0.0...
Patching component oracle.dbjava.ic, 18.0.0.0.0...
Patching component oracle.dbjava.jdbc, 18.0.0.0.0...
Patching component oracle.dbjava.ucp, 18.0.0.0.0...
Patching component oracle.javavm.client, 18.0.0.0.0...
Patching component oracle.ldap.owm, 18.0.0.0.0...
Patching component oracle.ldap.rsf, 18.0.0.0.0...
Patching component oracle.ldap.security.osdt, 18.0.0.0.0...
Patching component oracle.network.rsf, 18.0.0.0.0...
Patching component oracle.rdbms.dbscripts, 18.0.0.0.0...
Patching component oracle.rdbms.install.common, 18.0.0.0.0...
Patching component oracle.rdbms.install.plugins, 18.0.0.0.0...
Patching component oracle.rdbms.oci, 18.0.0.0.0...
Patching component oracle.sdo, 18.0.0.0.0...
Patching component oracle.sdo.locator.jrf, 18.0.0.0.0...
Patching component oracle.sqlplus, 18.0.0.0.0...
Patching component oracle.precomp.rsf, 18.0.0.0.0...
Patching component oracle.sqlplus.ic, 18.0.0.0.0...
Patching component oracle.xdk.rsf, 18.0.0.0.0...
Patching component oracle.rdbms.hsodbc, 18.0.0.0.0...
Patching component oracle.ons, 18.0.0.0.0...
Patching component oracle.rdbms.rman, 18.0.0.0.0...
Patching component oracle.oracore.rsf, 18.0.0.0.0...
Patching component oracle.rdbms.crs, 18.0.0.0.0...
Patching component oracle.ctx.rsf, 18.0.0.0.0...
Patching component oracle.network.client, 18.0.0.0.0...
Patching component oracle.server, 18.0.0.0.0...
Patching component oracle.oraolap.dbscripts, 18.0.0.0.0...
Patching component oracle.nlsrtl.rsf.core, 18.0.0.0.0...
Patching component oracle.rdbms.util, 18.0.0.0.0...
Patching component oracle.oraolap, 18.0.0.0.0...
Patching component oracle.odbc, 18.0.0.0.0...
Patching component oracle.sdo.locator, 18.0.0.0.0...
Patching component oracle.nlsrtl.rsf, 18.0.0.0.0...
Patching component oracle.ldap.rsf.ic, 18.0.0.0.0...
Patching component oracle.assistants.deconfig, 18.0.0.0.0...
Patching component oracle.xdk, 18.0.0.0.0...
Patching component oracle.install.deinstalltool, 18.0.0.0.0...
Patching component oracle.duma, 18.0.0.0.0...
Patching component oracle.ctx.atg, 18.0.0.0.0...
Patching component oracle.xdk.parser.java, 18.0.0.0.0...
Patching component oracle.rdbms.deconfig, 18.0.0.0.0...
Patching component oracle.network.listener, 18.0.0.0.0...
Patching component oracle.rdbms.rsf.ic, 18.0.0.0.0...
Patching component oracle.precomp.lang, 18.0.0.0.0...
Patching component oracle.precomp.common, 18.0.0.0.0...
Patch 30112122 successfully applied.
Sub-set patch [29757256] has become inactive due to the application of a super-set patch [30112122].
Please refer to Doc ID 2161861.1 for any possible further required actions.
Log file location: /u01/app/product/18c/db_home/cfgtoollogs/opatch/opatch2019-10-25_09-35-24AM_1.log
OPatch succeeded.
=========================================================

=========================================================

JAVA Patch Run Log

cd /OCT_2019_PSU/30133603/
opatch apply
Oracle Interim Patch Installer version 12.2.0.1.17
Copyright (c) 2019, Oracle Corporation.  All rights reserved.
Oracle Home       : /u01/app/product/18c/db_home
Central Inventory : /home/oracle/oraInventory
   from           : /u01/app/product/18c/db_home/oraInst.loc
OPatch version    : 12.2.0.1.17
OUI version       : 12.2.0.4.0
Log file location : /u01/app/product/18c/db_home/cfgtoollogs/opatch/opatch2019-10-25_09-40-40AM_1.log
Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   30133603
Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/product/18c/db_home')

Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying interim patch '30133603' to OH '/u01/app/product/18c/db_home'
Patching component oracle.javavm.server, 18.0.0.0.0...
Patching component oracle.javavm.server.core, 18.0.0.0.0...
Patching component oracle.rdbms.dbscripts, 18.0.0.0.0...
Patching component oracle.rdbms, 18.0.0.0.0...
Patching component oracle.javavm.client, 18.0.0.0.0...
Patch 30133603 successfully applied.
Sub-set patch [29774410] has become inactive due to the application of a super-set patch [30133603].
Please refer to Doc ID 2161861.1 for any possible further required actions.
Log file location: /u01/app/product/18c/db_home/cfgtoollogs/opatch/opatch2019-10-25_09-40-40AM_1.log
OPatch succeeded.
=========================================================
=========================================================
Datapatch Run Log
cd $ORACLE_HOME/OPatch
./datapatch -verbose
SQL Patching tool version 18.0.0.0.0 Production on Fri Oct 25 10:01:01 2019
Copyright (c) 2012, 2019, Oracle.  All rights reserved.
Log file for this invocation: /u01/cfgtoollogs/sqlpatch/sqlpatch_12096_2019_10_25_10_01_01/sqlpatch_invocation.log
Connecting to database...OK
Gathering database info...done
Note:  Datapatch will only apply or rollback SQL fixes for PDBs
       that are in an open state, no patches will be applied to closed PDBs.
       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
       (Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Determining current state...done
Current state of interim SQL patches:
Interim patch 27923415 (OJVM RELEASE UPDATE: 18.3.0.0.180717 (27923415)):
  Binary registry: Not installed
  PDB CDB$ROOT: Not installed
  PDB PDB$SEED: Not installed
Interim patch 29774410 (OJVM RELEASE UPDATE: 18.7.0.0.190716 (29774410)):
  Binary registry: Not installed
  PDB CDB$ROOT: Applied successfully on 18-OCT-19 01.07.10.275874 PM
  PDB PDB$SEED: Applied successfully on 18-OCT-19 01.07.12.312324 PM
Interim patch 30133603 (OJVM RELEASE UPDATE: 18.8.0.0.191015 (30133603)):
  Binary registry: Installed
  PDB CDB$ROOT: Not installed
  PDB PDB$SEED: Not installed
Current state of release update SQL patches:
  Binary registry:
    18.8.0.0.0 Release_Update 1909032123: Installed
  PDB CDB$ROOT:
    Applied 18.7.0.0.0 Release_Update 1906241920 successfully on 18-OCT-19 01.07.10.269630 PM
  PDB PDB$SEED:
    Applied 18.7.0.0.0 Release_Update 1906241920 successfully on 18-OCT-19 01.07.12.305647 PM
Adding patches to installation queue and performing prereq checks...done
Installation queue:
  For the following PDBs: CDB$ROOT PDB$SEED
    The following interim patches will be rolled back:
      29774410 (OJVM RELEASE UPDATE: 18.7.0.0.190716 (29774410))
    Patch 30112122 (Database Release Update : 18.8.0.0.191015 (30112122)):
      Apply from 18.7.0.0.0 Release_Update 1906241920 to 18.8.0.0.0 Release_Update 1909032123
    The following interim patches will be applied:
      30133603 (OJVM RELEASE UPDATE: 18.8.0.0.191015 (30133603))
Installing patches...
Patch installation complete.  Total patches installed: 6
Validating logfiles...done
Patch 29774410 rollback (pdb CDB$ROOT): SUCCESS
  logfile: /u01/cfgtoollogs/sqlpatch/29774410/22958594/29774410_rollback_CDBORCL_CDBROOT_2019Oct25_10_02_01.log (no errors)
Patch 30112122 apply (pdb CDB$ROOT): SUCCESS
  logfile: /u01/cfgtoollogs/sqlpatch/30112122/23124066/30112122_apply_CDBORCL_CDBROOT_2019Oct25_10_02_01.log (no errors)
Patch 30133603 apply (pdb CDB$ROOT): SUCCESS
  logfile: /u01/cfgtoollogs/sqlpatch/30133603/23088986/30133603_apply_CDBORCL_CDBROOT_2019Oct25_10_02_23.log (no errors)
Patch 29774410 rollback (pdb PDB$SEED): SUCCESS
  logfile: /u01/cfgtoollogs/sqlpatch/29774410/22958594/29774410_rollback_CDBORCL_PDBSEED_2019Oct25_10_02_27.log (no errors)
Patch 30112122 apply (pdb PDB$SEED): SUCCESS
  logfile: /u01/cfgtoollogs/sqlpatch/30112122/23124066/30112122_apply_CDBORCL_PDBSEED_2019Oct25_10_02_27.log (no errors)
Patch 30133603 apply (pdb PDB$SEED): SUCCESS
  logfile: /u01/cfgtoollogs/sqlpatch/30133603/23088986/30133603_apply_CDBORCL_PDBSEED_2019Oct25_10_02_39.log (no errors)
SQL Patching tool complete on Fri Oct 25 10:03:02 2019

=========================================================

Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more