Oracle - Applying PSU/CPU on Grid Home

-


This process was tested and documented on test server which is running a test database on +ASM version 12.1.0.2 and
I was applying PSU 181016 (October 2018)

Check the Status of the Databases and Listener(s)


Check the status of the Cluster Ready Services - using the crstat.py (V12 compatible)

Or you can use the crsctl stat res -t - which is the Oracle standard command


Download the appropriate patch for the Grid Infrastucture and place them in the /home/oracle/installers directory.

Unzip the GI patch and then check you have the correct version of Opatch to perform the installation.

Use the opatch analyze command as user root to check if the patch can be applied

[root@cdcol7test OPatch]# opatchauto apply /home/oracle/installers/PSU/28349311 -analyze

OPatchauto session is initiated at Thu Oct 18 10:00:08 2018

System initialization log file is /app/oracle/product/12.1.0/grid/cfgtoollogs/opatchautodb/systemconfig2018-10-18_10-00-14AM.log.

Session log file is /app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/opatchauto2018-10-18_10-00-25AM.log
The id for this session is BCRM

Executing OPatch prereq operations to verify patch applicability on home /app/oracle/product/12.1.0/dbhome_1
Patch applicability verified successfully on home /app/oracle/product/12.1.0/dbhome_1


Verifying SQL patch applicability on home /app/oracle/product/12.1.0/dbhome_1
SQL patch applicability verified successfully on home /app/oracle/product/12.1.0/dbhome_1


Executing OPatch prereq operations to verify patch applicability on home /app/oracle/product/12.1.0/grid
Patch applicability verified successfully on home /app/oracle/product/12.1.0/grid

OPatchAuto successful.

--------------------------------Summary--------------------------------

Analysis for applying patches has completed successfully:

Host:cdcol7test
SIDB Home:/app/oracle/product/12.1.0/dbhome_1
Version:12.1.0.2.0


==Following patches were SKIPPED:

Patch: /home/oracle/installers/PSU/28349311/26983807
Reason: This patch is not applicable to this specified target type - "oracle_database"

Patch: /home/oracle/installers/PSU/28349311/28259950
Reason: This patch is not applicable to this specified target type - "oracle_database"


==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /home/oracle/installers/PSU/28349311/28259833
Log: /app/oracle/product/12.1.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2018-10-18_10-00-57AM_1.log

Patch: /home/oracle/installers/PSU/28349311/28259914
Log: /app/oracle/product/12.1.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2018-10-18_10-00-57AM_1.log


Host:cdcol7test
SIHA Home:/app/oracle/product/12.1.0/grid
Version:12.1.0.2.0


==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /home/oracle/installers/PSU/28349311/26983807
Log: /app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2018-10-18_10-03-29AM_1.log

Patch: /home/oracle/installers/PSU/28349311/28259833
Log: /app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2018-10-18_10-03-29AM_1.log

Patch: /home/oracle/installers/PSU/28349311/28259914
Log: /app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2018-10-18_10-03-29AM_1.log

Patch: /home/oracle/installers/PSU/28349311/28259950
Log: /app/oracle/product/12.1.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2018-10-18_10-03-29AM_1.log



OPatchauto session completed at Thu Oct 18 10:04:00 2018
Time taken to complete the session 3 minutes, 52 seconds

If the Patch analyze was successful then apply the patch using autopatch apply

The Cluster Ready Services and the Database will be automatically shutdown and patched and re-started during this process


Check the Patch has been applied at the database level - using @version

And use opatch lsinventory to check all the patches have been applied

Finally check that all the CRS Resources are back online, as per the original check.


























Comments

Post a Comment

Popular posts from this blog

SQL SERVER – Event ID 107- Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

-
SQL SERVER – Event ID 107- Report Server Windows Service cannot connect to the report server database. Error with Report Server One of my clients reported an error which is the subject of the blog. In the event viewer they were seeing below error:     Event Type: Error Event Source: Report Server Windows Service (MSSQLSERVER) Event Category: Management Event ID: 107 Computer: SQLSERVER Description: Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database The error is generic because it doesn’t tell the exact error which is causing a connectivity error. My immediate question was that, are there any more errors? So, I asked them to look at Reporting Service Log file. Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. The application domain WindowsService_17 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report se
Read more

SQL Server Builds Information

-
Image
Very Useful information about SQL Server Builds .  It is nicely presented in the blog . Please see  below for our reference . Microsoft SQL Server Version List What version of SQL Server do I have? This unofficial build chart lists all of the known Service Packs ( SP ), Cumulative Updates ( CU ), patches, hotfixes and other builds of MS SQL Server 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released. Useful articles: How to identify your SQL Server version and edition SQL Server Internal Database Versions Microsoft SQL Server Support Lifecycle Microsoft SQL Server Home Microsoft SQL Server Developer Center Microsoft TechNet: Microsoft SQL Server Microsoft Knowledge Base Sqlservr.exe versions   Quick summary:   RTM (no SP ) SP1 SP2 SP3 SP4   SQL Server 2017      codename vNext 14.0.1000.169 *new           SQL Server 2016 13.0.1601.5 13.0.4001.0 or 13.1.4001.0 13.0.5026.0 or 13.2.5026.0   S
Read more

Using DBCA silent install and disabling automatic memory management

-
Image
Avoid issue [DBT-11211] /app/oracle/product/12.2.0/dbhome_1/bin=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -memoryPercentage 20 -emConfiguration NONE [FATAL] [DBT-11211] The Automatic Memory Management option is not allowed when the total physical memory is greater than 4GB.    CAUSE: The current total physical memory is 11GB. Solution : disable automatic memory management with in the response file and you will be fine :) .  /app/oracle/product/12.2.0/dbhome_1/assistants/dbca/templates=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -automaticMemoryManagement FALSE -memoryPercentage 20 -emConfiguration NONE Enter SYS user password: Enter SYSTEM user password: [WARNING] [DBT-06208] The 'SYS' password entered does not conform to the Oracle recommended standards.    CAUS
Read more