Patching in Oracle Database in simple HIGH level steps from 11g to 12c

-
STEP BY STEP APPLYING PSU IN ORACLE:
====================================
1-> We have to check the version of the OS i.e 32 or 64 bit
2-> Next we have to check the version of the database , we can use Opacth lsinventory
3-> Now check the patch advisory document to check whether patch is released or not
4-> Now download the patch and unzip the patch and check the prerequisites of the patch
5-> If the mentions as we have to install the patch using new OPatch verson then we have to download latest Opatch version
6-> Now make sure you have taken the backup of you binaries and also take database backup
7-> Now count the number of invalid objects before applying the patch
8-> Make sure you down the listener if it is running from DB home and else not required
9-> Now Shutdown the databases and the apply  the patch using Opatch apply
10-> Now start the database and then run the catbundle.sql script
     Catbundle script contains list of applied patches on the database and it will the pick the patch information from catbundle_bundleseries.xml script
     which is updated by Opatch, So running this script will updates the database catalog as which patch have been applied.
11-> After this run the utlrp.sql which is a mandatory script to be run validate database objects.


STEP BY STEP PATCHING in ORACLE 12C:
===================================
High Level steps for applying the Patch

Check the OS version and database version and then look for the latest patch in the patch advisory tool
Check current version of Opatch Tool
Upgrade the Opatch utility
Take the backup of ORACLE_HOME
Shutdown the Database and Listener
Apply PSU patch on ORACLE_HOME
Execute Post installation Scripts (datapatch) // Here you just execute datapatch -verbose tool which is loated under Opatch utility
which gathers information like whther patch installation requirement is met or not unlike catbundle just updates the DBA registry
Startup the Database and Listener
Check the dba_registry_sqlpatch .

STEP BY STEP PATCHING on Dataguard:
==================================
1-> check the OS and DB version
2-> Upgrade the Opatch utlity
3-> take the backup of the oracle home
4-> Now stop the  shipping from primary to stand by using the command log_archive_dest_state_2 to "defer"
5-> Go to the stand by server and then stop the MRP (recover managed standby database cancel)
Note: PSU (Patch Set Update)/CPU (Critical Patch Update)/ Patch Set patches  always needs to be applied first on the standby database and then on the primary database.
6-> Now shutdow the standby server and then listener also
7-> Apply the patch using Opatch apply
8-> After this start the listener and then database
9-> Now go to the primary database and note the invalid objects  and then shutdown the database and listener
10-> Now apply the patch and then start the database and listener
11-> Now enable log shipping log_archive_dest_state_2=enable
12-> Now start the MRP at the stand by side
13-> Now on the primary run the catbundle.sql

STEP BY STEP PATCHING on GRID and ORACLE HOME :
==============================================
1-> check the OS and DB version
2-> Upgrade the Opatch utlity
3-> take the backup of the oracle home
4-> Apply the patch using Opatchauto
    Note: OPatchauto automatically patch the typical Grid Infrastructure (GI) and RAC home directories with minimal intervention.to apply a patch using opatchauto,we need to run as a root user.
    note: to apply a patch separately for both GRID and ORACLE_HOME in both nodes. /u01/app/12.1.0.2/grid/OPatch/opatchauto apply /u01/27468957 -oh /u01/app/12.1.0.2/grid
5-> Check the DBA_REGISTRY_SQLPATCH :-

select BUNDLE_SERIES,PATCH_UID,PATCH_ID,VERSION,ACTION,STATUS,ACTION_TIME ,DESCRIPTIONfrom dba_registry_sqlpatch;


Comments

Post a Comment

Popular posts from this blog

Understanding Terraform

-
 Terraform is a tool used  for building, changing, and versioning infrastructure safely and efficiently. A Terraform can manage multiple cloud services using a provider plugin  Terraform work flow? Terraform work flow will be comprised of validate -> plan -> apply and finally destroy. what is the important file of terraform which records the actions of Terraform apply? For every Terraform execution the action will be recorded in a file called Terraform state file .  The terraform init command is used to initialise a working directory containing Terraform configuration files. During init, the configuration is searched for module blocks, and the source code for referenced modules is retrieved from the locations given in  their source arguments. The terraform plan command is used to create an execution plan. It will not modify things in infrastructure. The terraform apply command is used to apply the changes required to reach the desired state of the configur...
Read more

How to make CRS and ASM not to restart after server reboot

-
I have noticed that server rebooting is taking lot of time on a VM machine for every reboot, so I have decided to auto start of the crs and ASM service During this phase I have noticed an attribute called auto_start when I try to execute the below command crsctl stat res -p This AUTO_START attribute is there for several resources like ora.ASM ,ora.crs,ora.DATA_DG it has got 2 options restore(0) , never(2) and always (1) always (1)  Causes the resource to restart when the node restarts regardless of the resource’s state when the node stopped -restore (0)  Does not start the resource at restart time if it was in an offline state, such as STATE=OFFLINE, TARGET=OFFLINE, when the node stopped. The resource is restored to its state when the node went down. The resource is started only if it was online before and not otherwise. -never (2)  Oracle Clusterware never restarts the resource regardless of the resource’s state when the node is stopped. So I have dec...
Read more

How to repair ASM disk header

-
Image
What is ASM disk header corruption? ASM disk header corruption is a loss or damage to the disk header which contains the metadata essential for the operation and availability of an ASM disk group in Oracle. Imagine that you have an ASM disk corruption in any of the ASM diskgroups that have critical business data and the diskgroup has been configured as "EXTERNAL" redundancy, meaning that if one disk is inaccessible the whole diskgroup will be unavailable. Now what? Is your only option to restore it from backup by recreating the diskgroup or are there any other faster ways to recover the data? Here you need to find out whether it’s a complete loss of data in the ASM disk or is it just a header corruption. Hopefully for you, this is just a header corruption. Because, yes, there is a way out!  Below find the steps to restore from the ASM header corruption. Most of the data in the ASM disk header is of interest to that disk only. However, some information in the ASM disk header ...
Read more