Patching Template - Exadata Platinum Patching
Platinum patching:
Exadata Bundle patching:
Once we schedule a exadata bundle patching with oracle we need to upload this patching template 4 to 5 weeks in advance to the SR#.
1) Schedule a patching through Platinum Scheduling Tool which will generate the Patching SR# automatically.
Please refer the Platinum Scheduling Tool document
2) Run and upload the Exachk report to Oracle SR# 4 to 5 weeks in advance
Please refer How to run exachk Report document
3) Fill the Patching_Template upload to Oracle SR# 4 to 5 weeks in advance
Additionally, we require the following information to kick off the patching process (all mandatory, please confirm / correct / fill in, where necessary):
==========================================================================================================================================================================================
System Function: (Prod/Dev/Test/QA/DR/UAT): PROD
Gateway: ct-gateway-01
CSI #: 12121212
Rack Serial Number: AK12341234
System Name: RAC1
Virtualized Exadata – OVM – (Y/N): N
If OVM is present - we will patch up to 4 Virtual RAC clusters per rack and up to 2 database homes per RAC cluster.
Solaris compute node servers (Y/N): N
If Linux - target OEL version: 6.9
Rack Size: (1/8-1/4-1/2-Full): 1/4 + Elastic
Patch method Rolling/Non-Rolling/Hybrid: Non-Rolling
==========================================================================================================================================================================================
When Choosing the QFSDP Patch level, I suggest to go N-1. If you need the latest release, at the minimum, you will need to choose a date 1 full month AFTER the month the QFSDP was release.
When scheduling please consider:
Jan QFSDP release, first date would be March 1st of that year.
April QFSDP release, first date would be June 1st of that year.
July QFSDP release, first date would be September 1st of that year.
Oct QFSDP release, first date would be December 1st of that year.
1. Desired Patch (Jan/April/Jul/Oct): <By default we take the last available bundle patch (Please check Doc ID 888828.1 for further information on patch version)>: April 2019
2. Components to be patched:
- GI upgrade to 12c required (Y/N): <Platinum will upgrade only one GI per physical Rack> : N/A
- GI BP (Y/N): Y
- DB BP (Y/N): Y
- YUM (Y/N): Y
- CELLS (Y/N): Y
- IB (Y/N): Y
- Catbundles/Datapatch (Y/N): Y
- OJVM option - Your option: (select one from below options and write it on this line)
Option 1: Apply OJVM patch - ~ one hour downtime - RECOMMENDED
Option 2: Apply Mitigation patch - can interfere with other Java applications - RECOMMENDED FOR SHORT TERM ONLY IF OJVM DOWNTIME IS NOT POSSIBLE
Option 3: Apply none - NOT RECOMMENDED.
- please review note 1929745.1 and select one of the above options (applying the OJVM requires ~ 1 hour of downtime per RAC for both primary and stand-by environments)
NOTE: Mitigation and OJVM patches can coexist. The mitigation patch can be turned on and off, at will.
Your option: Option 1
3. Platinum does not cover database upgrades.
4. Other patching requirements (if any): N/A
==========================================================================================================================================================================================
Name and number of DB's to be patched (please specify for each one of them if RAC or NON-RAC):
3 Node RAC DB - DB1:/u01/app/oracle/product/11.2.0.4/DB1:N (OBIEE-11.1.1.9.5)
3 Node RAC DB - DB2:/u01/app/oracle/product/11.2.0.4/DB2:N (EBS R12.1.3)
3 Node RAC DB - STDBY:/u01/app/oracle/product/11.2.0.4/STDBY:N (Standby DB for DB1)
Single instance databases – if present - (please specify for each one of them if RAC or NON-RAC): N/A
Multi-tenant architecture databases to be patched (optional feature on 12C version only, if you are running 11G please leave blank): N/A
==========================================================================================================================================================================================
Oracle Homes to be patched (Platinum will patch Max 2 DB Homes per Rack/OVM): (3 OH - We have exceptinal aproval to patch 3 OH)
DB1:/u01/app/oracle/product/11.2.0.4/DB1:N (OBIEE-11.1.1.9.5)
DB2:/u01/app/oracle/product/11.2.0.4/DB2:N (EBS R12.1.3)
STDBY:/u01/app/oracle/product/11.2.0.4/STDBY:N (Standby DB for DB1)
==========================================================================================================================================================================================
EBS database/grid/home present in the environment (Y/N): Y
If Y, please provide details (for more information about the special instructions that need to be taken in consideration for EBS patching, please review MOS DOC ID 1392527.1 ): EBS R12.1.3
==========================================================================================================================================================================================
SAP GRID / HOME / DB (Y/N): N/A
If Y, please provide details: N/A
==========================================================================================================================================================================================
Data guard (Y/N): YES
If Y: Yes
- Please confirm if primary or stand-by: Primary and Standby are on same RACK
- Please confirm the OEL version for the interconnected machine (OEL 5.10/OEL 6.6): OEL 6.9
- Any hardware/software differences between primary and stand-by (Y/N) – if Y, please detail the differences: N/A
==========================================================================================================================================================================================
Normal/High Redundancy (for ROLLING events, HIGH REDUNDANCY is recommended): Normal
Requested Patch Date – please provide us with a tentative patch date: N/A
Requested Patch Start Time (please also add your time zone): 11-Aug-2019 4:30 AM ET
If the requested patch date is in weekend and cannot be accommodated, please share the most comfortable weekday (Monday-Thursday) when you would patch (please share the start time also): N/A
Customer available maintenance (TOTAL) window - <in hours>: 10 hours
Customer available outage (DOWNTIME ONLY) window - <in hours>: 10 hours
==========================================================================================================================================================================================
Exalogic attached (Y/N) <if Yes, please confirm which patch version it is patched to>: N/A
ZFS Storage Appliance attached (Y/N): N/A
Patching “Special Instructions” for Oracle to take in consideration: We have EBS database (EBS R12.1.3) and OBI database (OBIEE-11.1.1.9.5)
Any other system (logical or physical) setups/specifics/installed software, that Oracle should be aware of:
==========================================================================================================================================================================================
Primary Patching Contact (Full Name / email / phone): Mallikarjun Ramadurg / mallikarjun.ramadurg@aaaaa.com
Secondary Patching Contact(Full Name / email / phone):
We also recommend you to check:
Oracle Platinum Services - Recommended Best Practices for Patch Events ( Doc ID 2147697.1 )
Exadata Patching Overview and Patch Testing Guidelines ( Doc ID 1262380.1 )
==========================================================================================================================================================================================
***IMPORTANT***: Please make sure that the relevant system passwords are up to date on the OASG Portal; for more details:
please consult “Platinum Service Delivery - Credential Management in gateway release 9.X ( Doc ID 2285834.1 ).
==========================================================================================================================================================================================
=====================================================================================================================================================================
Exachk:
The version of exachk is updated periodically, so please make sure to download the latest version, run it and upload the .zip file to the Patching SR.
1. Login as root user, make a clean directory and load Exachk latest version (Oracle Exadata Database Machine exachk or HealthCheck Doc ID 1070954.1
2. cd to the directory created
export RAT_IBSWITCH_USER=root
export RAT_NOCLEAN_DIR=1
export RAT_ROOT_TIMEOUT=900
export RAT_PASSWORDCHECK_TIMEOUT=100
export RAT_TIMEOUT=240
3. Run exachk
./exachk -a
answer the prompt to set crs home as "Y".
select all databases
answer the prompts for the root password on the storage servers
answer the prompts for the root userid password on the database servers
answer the prompts for the nm2user(root) password on the IB switches
Upload the complete exachk report (exachk_<date,time>.zip file).
For EXadata with VM's use the below as guidance if needed: N/A
From one management domain (dom0)
From one user domain (domU) in each RAC VM cluster
Each Compute node is the DOM0 and it has the same ip as physical compute node .
The following procedure describes how to show running domains: N/A
Connect to the management domain (domain zero, or dom0) (Physical compute node).
Run the xm list command. The following is an example of the output: N/A
Example
# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 ***** **** ***** ******
=====================================================================================================================================================================
Please run the below commands and post the results into the SR:
**Owner, Group details of Grid & Oracle homes to be patched <Execute below command as root or sudo user in 1st DB node of cluster>:
egrep -v "^#|^$|agent" /etc/oratab | cut -d ":" -f2 | sort | uniq | while read home;do echo -n "$home==>"; stat -c %U:%G $home/inventory; done
[root@dbnode01 ~]# egrep -v "^#|^$|agent" /etc/oratab | cut -d ":" -f2 | sort | uniq | while read home;do echo -n "$home==>"; stat -c %U:%G $home/inventory; done
/u01/app/12.2.0.1/grid==>grid:oinstall
/u01/app/oracle/product/11.2.0.4/dbhome_1==>oracle:oinstall
/u01/app/oracle/product/11.2.0.4/DB2==>oraxprod:oinstall
/u01/app/oracle/product/11.2.0.4/STDBY==>obisprod:oinstall
/u01/app/oracle/product/11.2.0.4/DB1==>DB1:oinstall
[root@dbnode01 ~]#
**Agent Details : <Execute below command as root or sudo user in 1st DB node of cluster>
ps -ef | grep agent | grep java | sed 's/\s\+/ /g' | cut -d " " -f 1,8 | sed 's/\/jdk.*//'
[root@dbnode01 ~]# ps -ef | grep agent | grep java | sed 's/\s\+/ /g' | cut -d " " -f 1,8 | sed 's/\/jdk.*//'
omauser /u01/app/oracle/product/agent13c/agent_13.2.0.0.0/oracle_common
grid /u01/app/12.2.0.1/grid
orarom /opt/OracleHomes/agent_home/agent_13.2.0.0.0/oracle_common
[root@dbnode01 ~]#
=====================================================================================================================================================================
Platinum patching:
Exadata Bundle patching:
Once we schedule a exadata bundle patching with oracle we need to upload this patching template 4 to 5 weeks in advance to the SR#.
1) Schedule a patching through Platinum Scheduling Tool which will generate the Patching SR# automatically.
Please refer the Platinum Scheduling Tool document
2) Run and upload the Exachk report to Oracle SR# 4 to 5 weeks in advance
Please refer How to run exachk Report document
3) Fill the Patching_Template upload to Oracle SR# 4 to 5 weeks in advance
Patching_Template
==========================================================================================================================================================================================Additionally, we require the following information to kick off the patching process (all mandatory, please confirm / correct / fill in, where necessary):
==========================================================================================================================================================================================
System Function: (Prod/Dev/Test/QA/DR/UAT): PROD
Gateway: ct-gateway-01
CSI #: 12121212
Rack Serial Number: AK12341234
System Name: RAC1
Virtualized Exadata – OVM – (Y/N): N
If OVM is present - we will patch up to 4 Virtual RAC clusters per rack and up to 2 database homes per RAC cluster.
Solaris compute node servers (Y/N): N
If Linux - target OEL version: 6.9
Rack Size: (1/8-1/4-1/2-Full): 1/4 + Elastic
Patch method Rolling/Non-Rolling/Hybrid: Non-Rolling
==========================================================================================================================================================================================
When Choosing the QFSDP Patch level, I suggest to go N-1. If you need the latest release, at the minimum, you will need to choose a date 1 full month AFTER the month the QFSDP was release.
When scheduling please consider:
Jan QFSDP release, first date would be March 1st of that year.
April QFSDP release, first date would be June 1st of that year.
July QFSDP release, first date would be September 1st of that year.
Oct QFSDP release, first date would be December 1st of that year.
1. Desired Patch (Jan/April/Jul/Oct): <By default we take the last available bundle patch (Please check Doc ID 888828.1 for further information on patch version)>: April 2019
2. Components to be patched:
- GI upgrade to 12c required (Y/N): <Platinum will upgrade only one GI per physical Rack> : N/A
- GI BP (Y/N): Y
- DB BP (Y/N): Y
- YUM (Y/N): Y
- CELLS (Y/N): Y
- IB (Y/N): Y
- Catbundles/Datapatch (Y/N): Y
- OJVM option - Your option: (select one from below options and write it on this line)
Option 1: Apply OJVM patch - ~ one hour downtime - RECOMMENDED
Option 2: Apply Mitigation patch - can interfere with other Java applications - RECOMMENDED FOR SHORT TERM ONLY IF OJVM DOWNTIME IS NOT POSSIBLE
Option 3: Apply none - NOT RECOMMENDED.
- please review note 1929745.1 and select one of the above options (applying the OJVM requires ~ 1 hour of downtime per RAC for both primary and stand-by environments)
NOTE: Mitigation and OJVM patches can coexist. The mitigation patch can be turned on and off, at will.
Your option: Option 1
3. Platinum does not cover database upgrades.
4. Other patching requirements (if any): N/A
==========================================================================================================================================================================================
Name and number of DB's to be patched (please specify for each one of them if RAC or NON-RAC):
3 Node RAC DB - DB1:/u01/app/oracle/product/11.2.0.4/DB1:N (OBIEE-11.1.1.9.5)
3 Node RAC DB - DB2:/u01/app/oracle/product/11.2.0.4/DB2:N (EBS R12.1.3)
3 Node RAC DB - STDBY:/u01/app/oracle/product/11.2.0.4/STDBY:N (Standby DB for DB1)
Single instance databases – if present - (please specify for each one of them if RAC or NON-RAC): N/A
Multi-tenant architecture databases to be patched (optional feature on 12C version only, if you are running 11G please leave blank): N/A
==========================================================================================================================================================================================
Oracle Homes to be patched (Platinum will patch Max 2 DB Homes per Rack/OVM): (3 OH - We have exceptinal aproval to patch 3 OH)
DB1:/u01/app/oracle/product/11.2.0.4/DB1:N (OBIEE-11.1.1.9.5)
DB2:/u01/app/oracle/product/11.2.0.4/DB2:N (EBS R12.1.3)
STDBY:/u01/app/oracle/product/11.2.0.4/STDBY:N (Standby DB for DB1)
==========================================================================================================================================================================================
EBS database/grid/home present in the environment (Y/N): Y
If Y, please provide details (for more information about the special instructions that need to be taken in consideration for EBS patching, please review MOS DOC ID 1392527.1 ): EBS R12.1.3
==========================================================================================================================================================================================
SAP GRID / HOME / DB (Y/N): N/A
If Y, please provide details: N/A
==========================================================================================================================================================================================
Data guard (Y/N): YES
If Y: Yes
- Please confirm if primary or stand-by: Primary and Standby are on same RACK
- Please confirm the OEL version for the interconnected machine (OEL 5.10/OEL 6.6): OEL 6.9
- Any hardware/software differences between primary and stand-by (Y/N) – if Y, please detail the differences: N/A
==========================================================================================================================================================================================
Normal/High Redundancy (for ROLLING events, HIGH REDUNDANCY is recommended): Normal
Requested Patch Date – please provide us with a tentative patch date: N/A
Requested Patch Start Time (please also add your time zone): 11-Aug-2019 4:30 AM ET
If the requested patch date is in weekend and cannot be accommodated, please share the most comfortable weekday (Monday-Thursday) when you would patch (please share the start time also): N/A
Customer available maintenance (TOTAL) window - <in hours>: 10 hours
Customer available outage (DOWNTIME ONLY) window - <in hours>: 10 hours
==========================================================================================================================================================================================
Exalogic attached (Y/N) <if Yes, please confirm which patch version it is patched to>: N/A
ZFS Storage Appliance attached (Y/N): N/A
Patching “Special Instructions” for Oracle to take in consideration: We have EBS database (EBS R12.1.3) and OBI database (OBIEE-11.1.1.9.5)
Any other system (logical or physical) setups/specifics/installed software, that Oracle should be aware of:
==========================================================================================================================================================================================
Primary Patching Contact (Full Name / email / phone): Mallikarjun Ramadurg / mallikarjun.ramadurg@aaaaa.com
Secondary Patching Contact(Full Name / email / phone):
We also recommend you to check:
Oracle Platinum Services - Recommended Best Practices for Patch Events ( Doc ID 2147697.1 )
Exadata Patching Overview and Patch Testing Guidelines ( Doc ID 1262380.1 )
==========================================================================================================================================================================================
***IMPORTANT***: Please make sure that the relevant system passwords are up to date on the OASG Portal; for more details:
please consult “Platinum Service Delivery - Credential Management in gateway release 9.X ( Doc ID 2285834.1 ).
==========================================================================================================================================================================================
=====================================================================================================================================================================
Exachk:
The version of exachk is updated periodically, so please make sure to download the latest version, run it and upload the .zip file to the Patching SR.
1. Login as root user, make a clean directory and load Exachk latest version (Oracle Exadata Database Machine exachk or HealthCheck Doc ID 1070954.1
2. cd to the directory created
export RAT_IBSWITCH_USER=root
export RAT_NOCLEAN_DIR=1
export RAT_ROOT_TIMEOUT=900
export RAT_PASSWORDCHECK_TIMEOUT=100
export RAT_TIMEOUT=240
3. Run exachk
./exachk -a
answer the prompt to set crs home as "Y".
select all databases
answer the prompts for the root password on the storage servers
answer the prompts for the root userid password on the database servers
answer the prompts for the nm2user(root) password on the IB switches
Upload the complete exachk report (exachk_<date,time>.zip file).
For EXadata with VM's use the below as guidance if needed: N/A
From one management domain (dom0)
From one user domain (domU) in each RAC VM cluster
Each Compute node is the DOM0 and it has the same ip as physical compute node .
The following procedure describes how to show running domains: N/A
Connect to the management domain (domain zero, or dom0) (Physical compute node).
Run the xm list command. The following is an example of the output: N/A
Example
# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 ***** **** ***** ******
=====================================================================================================================================================================
Please run the below commands and post the results into the SR:
**Owner, Group details of Grid & Oracle homes to be patched <Execute below command as root or sudo user in 1st DB node of cluster>:
egrep -v "^#|^$|agent" /etc/oratab | cut -d ":" -f2 | sort | uniq | while read home;do echo -n "$home==>"; stat -c %U:%G $home/inventory; done
[root@dbnode01 ~]# egrep -v "^#|^$|agent" /etc/oratab | cut -d ":" -f2 | sort | uniq | while read home;do echo -n "$home==>"; stat -c %U:%G $home/inventory; done
/u01/app/12.2.0.1/grid==>grid:oinstall
/u01/app/oracle/product/11.2.0.4/dbhome_1==>oracle:oinstall
/u01/app/oracle/product/11.2.0.4/DB2==>oraxprod:oinstall
/u01/app/oracle/product/11.2.0.4/STDBY==>obisprod:oinstall
/u01/app/oracle/product/11.2.0.4/DB1==>DB1:oinstall
[root@dbnode01 ~]#
**Agent Details : <Execute below command as root or sudo user in 1st DB node of cluster>
ps -ef | grep agent | grep java | sed 's/\s\+/ /g' | cut -d " " -f 1,8 | sed 's/\/jdk.*//'
[root@dbnode01 ~]# ps -ef | grep agent | grep java | sed 's/\s\+/ /g' | cut -d " " -f 1,8 | sed 's/\/jdk.*//'
omauser /u01/app/oracle/product/agent13c/agent_13.2.0.0.0/oracle_common
grid /u01/app/12.2.0.1/grid
orarom /opt/OracleHomes/agent_home/agent_13.2.0.0.0/oracle_common
[root@dbnode01 ~]#
=====================================================================================================================================================================
Regards,
Mallik
No comments:
Post a Comment