Skip to main content

How to Patch Oracle RAC Clusterware 12c and Database Using opatch auto


<<Back to Oracle RAC Main Page

Step by Step Instruction to Patch Oracle RAC Cluster Version 12.1.0.2

Step0: download the PSU and read the readme.txt for the patch. The installation instruction and rollback instruction is provided in readme file.
Transfer the PSU on each node of the RAC cluster. 
Here is the extract and simplified version of Oracle  RAC patching procedure for release version 12.1.0.2 using opatchauto

Step1: Ensure the Latest OPatch utility is Available

Check Current OPatch Utility Version
Verify if the required  OPatch utility as mentioned in readme.txt is available.
$export ORACLE_HOME=/u01/product/12.1.0.2/dbhome1
$export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch
$opatch version
OPatch Version: 12.2.0.1.3
OPatch succeeded.

Upgrade OPatch Utility to The Latest Version
Download the latest OPatch utility version as mentioned in readme.txt. Ensure to upgrade the OPatch utility in all OH homes and GI home on all nodes. Latest OPatch utility for your version is available for Download from My Oracle Support patch 6880880.
To Upgrade the OPatch follow below steps for each OH and GI homes
  1. Download and transfer the OPatch utility file to all the server (I copied it in /u01/stage)
  2. $unzip /u01/stage/p28199085_12102190716_Linux-x86-64.zip
  3. #mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch_Backup
  4. # cp /u01/stage/OPatch $ORACLE_HOME/
  5. #chown -R oracle:dba $ORACLE_HOME/OPatch
  6. #chmod -R 755 $ORACLE_HOME/OPatch
  7. #opatch version
OPatch Version: 12.2.0.1.17
OPatch succeeded.


Step2: Perform Complete Cluster Stack Health Check: Strongly Recommended


Download latest ORACheck utility install it and run it to perform the cluster health check. You can find the instruction guide, download package etc at MOS Note 1268927.2
If you have latest version of TFA installed and configured ORACheck is part of TFA and already installed in your environment.You can run racheck directly from tfa CLI interface as below
$tfactl
tfactl> orachk
CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to /u01/grid/product/12.1.0.2/gi?[y/n][y]
Follow the screen instruction to and wait for completion of ORACheck execution.
Analyze the output file and fix any possible errors before proceeding to next step

Step3: Prepare the Node for Patching
NOTE: Since the patching is done in rolling mode to avoid any outage for application, ensure the database and services is always available from available node in the cluster

Verify the Database Services Running on Node1
$srvctl status service -d DB1
Service srv1 is running on instance(s) DB11,DB12
$srvctl status service -d DB2
Service srv2 is running on instance(s) DB21,DB22

Stop or relocate the services from the node1 to node2
NOTE: In production environment run this step at least few hours before starting the patching to ensure that all the sessions are properly gone from node1.  In my case, since the services are running on all the nodes I will simply stop them on node1 (the node which I am going to patch first)
$srvctl stop service -d DB1 -s srv1 -n node1
$srvctl stop service -d DB2 -s srv2 -n node1

Verify and Confirm that All the Services are now running on 2nd node and no service is running on node1
$srvctl status service -d DB1
Service srv1 is running on instance(s) DB21
$srvctl status service -d DB2
Service srv2 is running on instance(s) DB22

Verify and Ensure that there is no Active Session and Transactions Running on Node1
$ sqlplus "/as sysdba"
select SID,USERNAME,STATUS from v$session where username not in ('SYS','DBSNMP');
no rows selected

col machine for a30
col username for a30
col program for a30 trun
col sid for 99999
set lines 300select sid,USED_UBLK,username,program,machine,systimestamp
from v$transaction t, v$session s
where SES_ADDR = s.saddr order by 1;
no rows selected

select sid,USED_UBLK,username,program,machine,systimestamp
from gv$transaction t, gv$session s
where SES_ADDR = s.saddr order by 1;
no rows selected

NOTE: if you are using OPatch utility 12.2.0.1.5 or later you do not need OCM(Oracle Configuration Manager) response file any more

Step4: Validate Patch Inventory for all homes
$opatch lsinventory -detail -oh /u01/grid/product/12.1.0.2/gi > /u01/stage/GI_OH_INV
$opatch lsinventory -detail -oh /u01/product/12.1.0.2/dbhome1 > /u01/stage/DB_OH_INV

Step5: Verify and resolve the Patch Conflicts
as root user
# opatchauto apply /u01/stage/29698592 -analyze
to see the sample output of analyze command scroll down

Step6: Run opatch auto to patch node1

NOTE: The Patching Steps are only valid for systems where GI Home and the Database Homes are not shared and ACFS file system is not configured
As root user, execute the following command on node1

#export ORACLE_HOME=/u01/grid/product/12.1.0.2/gi
#export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin
#export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
#opatchauto apply /u01/stage/29698592


to see the sample out put of opatch apply command scroll down

Step7: Repeat step 3 to 6 for node2.

Step8: Verify the patch Installation


$opatch lsinventory -oh /u01/grid/product/12.1.0.2/gi |grep -e 'patch_id1' -e 'patch_id2' -e 'patch_id3'

SQL> set serverout on;
SQL>  exec dbms_qopatch.get_sqlpatch_status;

Patch Id : 25171037
        Action : APPLY
        Action Time : 13-MAR-2018 11:54:14
        Description : DATABASE PATCH SET UPDATE 12.1.0.2.170418
        Logfile :
/u01/cfgtoollogs/sqlpatch/25171037/21099266/25171037_apply_DBD_2018Mar13
_11_51_42.log
        Status : SUCCESS

Patch Id : 28259833
        Action : APPLY
        Action Time : 03-NOV-2018 17:14:39
        Description : DATABASE PATCH SET UPDATE 12.1.0.2.181016
        Logfile :
/u01/cfgtoollogs/sqlpatch/28259833/22488632/28259833_apply_DBD_2018Nov03
_17_13_55.log
        Status : SUCCESS
Patch Id : 29494060
        Action : APPLY
        Action Time : 19-SEP-2019 11:36:21
        Description : DATABASE PATCH SET UPDATE 12.1.0.2.190716
        Logfile :
/u01/cfgtoollogs/sqlpatch/29494060/22993235/29494060_apply_DBD_2019Sep19
_11_35_55.log
        Status : SUCCESS
PL/SQL procedure successfully completed.

OR

SQL> select xmltransform(dbms_qopatch.is_patch_installed('29494060'), dbms_qopatch.get_opatch_xslt) "Patch installed?" from dual;

Patch installed?
--------------------------------------------------------------------------------
Patch Information:
         29494060:   applied on 2019-09-19T11:00:56+02:00


NOTE: The step "Loading Modified SQL Files into the Database" has been automated with opatch auto starting from 12c. opatchauto automatically performs the load of the modified SQL files into the Database.



opatchauto apply <PatchID> -analyze Output
========================================================================================================================================
OPatchauto session is initiated at Tue Sep 17 17:05:18 2019
System initialization log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchautodb/systemconfig2019-09-17_05-05-20PM.log.
Session log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/opatchauto2019-09-17_05-06-52PM.log
The id for this session is 5CHZ
Executing OPatch prereq operations to verify patch applicability on home //u01/product/12.1.0.2/dbhome1
Executing OPatch prereq operations to verify patch applicability on home /u01/grid/product/12.1.0.2/gi
Executing OPatch prereq operations to verify patch applicability on home //u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home /u01/grid/product/12.1.0.2/gi
Patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome1

Verifying SQL patch applicability on home //u01/product/12.1.0.2/dbhome3
Verifying SQL patch applicability on home //u01/product/12.1.0.2/dbhome1
SQL patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome3
SQL patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome1
OPatchAuto successful.
--------------------------------Summary--------------------------------
Analysis for applying patches has completed successfully:
Host:node1
CRS Home:/u01/grid/product/12.1.0.2/gi
Version:12.1.0.2.0

==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is already been applied, so not going to apply again.

==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/stage/29698592/29423125
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Patch: /u01/stage/29698592/29494060
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log

Host:node1
RAC Home://u01/product/12.1.0.2/dbhome3
Version:12.1.0.2.0

==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"

==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/stage/29698592/29494060
Log: //u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Patch: /u01/stage/29698592/29509318
Log: //u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log

Host:node1
RAC Home://u01/product/12.1.0.2/dbhome1
Version:12.1.0.2.0

==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"

==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/stage/29698592/29494060
Log: //u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Patch: /u01/stage/29698592/29509318
Log: //u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log

Following homes are skipped during patching as patches are not applicable:
//u01/product/11.2.0.4/dbhome1

OPatchauto session completed at Tue Sep 17 17:13:17 2019
Time taken to complete the session 8 minutes, 0 second
You have new mail in /var/spool/mail/root
========================================================================================================================================

opatch auto apply <PATCH ID>  Output
========================================================================================================================================
OPatchauto session is initiated at Wed Sep 18 10:59:31 2019
System initialization log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchautodb/systemconfig2019-09-18_10-59-33AM.log.
Session log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/opatchauto2019-09-18_11-01-03AM.log
The id for this session is WD53
Executing OPatch prereq operations to verify patch applicability on home /u01/product/12.1.0.2/dbhome1
Executing OPatch prereq operations to verify patch applicability on home /u01/grid/product/12.1.0.2/gi
Executing OPatch prereq operations to verify patch applicability on home /u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home /u01/grid/product/12.1.0.2/gi
Patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome1

Verifying SQL patch applicability on home /u01/product/12.1.0.2/dbhome3
Verifying SQL patch applicability on home /u01/product/12.1.0.2/dbhome1
SQL patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome3
com.oracle.glcm.patch.auto.db.product.driver.crs.CrsProductDrivercom.oracle.glcm.patch.auto.db.product.driver.crs.CrsProductDrivercom.oracle.glcm.patch.auto.db.product.driver.crs.CrsProductDrivercom.oracle. glcm.patch.auto.db.product.driver.crs.CrsProductDriverSQL patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome1

Preparing to bring down database service on home /u01/product/12.1.0.2/dbhome1
Successfully prepared home /u01/product/12.1.0.2/dbhome1 to bring down database service

Preparing to bring down database service on home /u01/product/12.1.0.2/dbhome3
Successfully prepared home /u01/product/12.1.0.2/dbhome3 to bring down database service

Bringing down CRS service on home /u01/grid/product/12.1.0.2/gi
Prepatch operation log file location: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/crsconfig/crspatch_node1_2019-09-18_11-08-08AM.log
CRS service brought down successfully on home /u01/grid/product/12.1.0.2/gi

Performing prepatch operation on home /u01/product/12.1.0.2/dbhome1
Perpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome1

Performing prepatch operation on home /u01/product/12.1.0.2/dbhome3
Perpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome3

Start applying binary patch on home /u01/product/12.1.0.2/dbhome1
Binary patch applied successfully on home /u01/product/12.1.0.2/dbhome1

Start applying binary patch on home /u01/product/12.1.0.2/dbhome3
Binary patch applied successfully on home /u01/product/12.1.0.2/dbhome3

Performing postpatch operation on home /u01/product/12.1.0.2/dbhome1
Postpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome1

Performing postpatch operation on home /u01/product/12.1.0.2/dbhome3
Postpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome3

Start applying binary patch on home /u01/grid/product/12.1.0.2/gi
Binary patch applied successfully on home /u01/grid/product/12.1.0.2/gi

Starting CRS service on home /u01/grid/product/12.1.0.2/gi
Postpatch operation log file location: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/crsconfig/crspatch_node1_2019-09-18_11-20-52AM.log
CRS service started successfully on home /u01/grid/product/12.1.0.2/gi

Preparing home /u01/product/12.1.0.2/dbhome1 after database service restarted
No step execution required.........

Preparing home /u01/product/12.1.0.2/dbhome3 after database service restarted
No step execution required.........

Trying to apply SQL patch on home /u01/product/12.1.0.2/dbhome1
SQL patch applied successfully on home /u01/product/12.1.0.2/dbhome1

Trying to apply SQL patch on home /u01/product/12.1.0.2/dbhome3
SQL patch applied successfully on home /u01/product/12.1.0.2/dbhome3
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:node1
RAC Home:/u01/product/12.1.0.2/dbhome1
Version:12.1.0.2.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"

==Following patches were SUCCESSFULLY applied:
Patch: /u01/stage/29698592/29494060
Log: /u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-09-24AM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-09-24AM_1.log

Host:node1
RAC Home:/u01/product/12.1.0.2/dbhome3
Version:12.1.0.2.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"

==Following patches were SUCCESSFULLY applied:
Patch: /u01/stage/29698592/29494060
Log: /u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-12-08AM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-12-08AM_1.log

Host:node1
CRS Home:/u01/grid/product/12.1.0.2/gi
Version:12.1.0.2.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is already been applied, so not going to apply again.

==Following patches were SUCCESSFULLY applied:
Patch: /u01/stage/29698592/29423125
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Patch: /u01/stage/29698592/29494060
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log

Patching session reported following warning(s):
_________________________________________________
[WARNING] The database instance 'DCDB' from '/u01/product/12.1.0.2/dbhome1', in host'node1' is not running. SQL changes, if any,  will not be applied.
To apply. the SQL changes, bring up the database instance and run the command manually from any one node (run as oracle).
Refer to the readme to get the correct steps for applying the sql changes.

Following homes are skipped during patching as patches are not applicable:
/u01/product/11.2.0.4/dbhome1

OPatchauto session completed at Wed Sep 18 11:38:58 2019
Time taken to complete the session 39 minutes, 28 seconds
========================================================================================================================================

Comments

  1. Sumeet S. YogiJune 23, 2021 at 4:30 AM

    Well written article . Thank you for sharing this with all ..

    ReplyDelete

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