Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify how to identify oracle patches or bundle patches (SBP) in SAP system.

Overview

On this session you will refer to methods on how to identify the list of Oracle patches (SBP, DBBP) or Bundle patches that are installed from R3 level and OS level.

Methods from OS level

1.  As of Oracle 9i:

Execute the following command under ora<sid> \ <sid>adm \ oracle user:

$ORACLE_HOME/OPatch/opatch lsinventory (UNIX)

$ORACLE_HOME\OPatch\opatch lsinventory (Windows) 

2.  As of BRCONNECT 7.00 patch level 20:

brconnect -F lsinv 

3.  As of Oracle Release 10g and up to 12c generally:

You can use DBA_REGISTRY_HISTORY to display information about upgrades, downgrades, and critical patch updates that have been performed on the database.

Example:

- select action, namespace, version, id, comments from dba_registry_history where version = '<version>' order by action_time desc;

- select action_time, version, comments from dba_registry_history order by action_time desc;  

4.  As of Oracle 12c:

Here we have to differentiate between Windows and Unix/Linux system.


Windows:

You can use dba_registry_sqlpatch only.

Example:

- select patch_id,action,status,action_time,description,bundle_series,bundle_id from dba_registry_sqlpatch;


UNIX/Linux:

You can use dba_registry_history and dba_registry_sqlpatch at the same time.

Example:

- select patch_id,action,status,action_time,description,bundle_series,bundle_id from dba_registry_sqlpatch;

- select action_time, version, comments from dba_registry_history order by action_time desc;

Please note:

  • Refer SAP Note 1899453 dba_registry_history does not record SBP installed for more information.
  • The SAP Bundle Patches are installed correctly ONLY if “opatch lsinventory” and the latest entry of DBA_REGISTRY_HISTORY show the same bundle series SBP
  • The dba_registry_history will not show the most recent row associated with bundle series SBP although the “opatch lsinventory” shows the patches have been installed if the post installation script is NOT executed.  Hence, please make sure that the  post-installation steps are implemented as per the README guide.

On Windows:
The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series.

On UNIX:
After you have successfully run catsbp.sql, you can also find the SBP version in the database in view dba_registry_history in the most recent row associated with bundle series SBP.  

Methods from R/3 level

1.  As of Basis Release 7.10 and Release 7.00 Support Package 11, Release 6.40 Support Package 20 and Release 6.20 Support Package 62:

SE38 -> Report RSORAPATCHINFO

 Please note: 

  •  Known bugs: SAP Note 1381337 Report RSORAPATCHINFO fails during BRCONNECT or OPatch call
  •  User <sid>adm must have read and write files permission under the ‘$ORACLE_HOME/cfgtoollogs/opatch/’ sub-folder, example: opatch_history.txt.
  •  A log file will be generated under '$ORACLE_HOME/cfgtoollogs/opatch/', example:  lsinventory2012-02-16_16-48-55PM.txt 

 2.  As of Oracle 10g:

AL11 -> DIR_ORAHOME -> cfgtoollogs -> opatch -> lsinv (Sort the files by the latest date and timestamp, example: lsinventory2012-02-16_16-48-55PM.txt)

 3.  As of Oracle 10.2.0.4 and as of the patch day (May 10th, 2010), SAP Bundle Patches is provided for UNIX platform:

AL11 -> DIR_ORAHOME -> sapbundle -> version.txt

 Please note:

  • The version.txt can be edited manually.
  • It is advisable to verify the current SBP patch level by using the dba_registry_history.

Current version of this documentation is available in SAP KBA number 1696147.

Related Content

Related SAP Notes/KBAs

SAP Note 1381337: Report RSORAPATCHINFO fails during BRCONNECT or OPatch call

SAP Note 1899453: dba_registry_history does not record SBP installed

 

  • No labels