This section describes bundle patches and explains differences between bundle patches, patch set exceptions (also known as one-offs), and patch sets.

• Bundle Patch

• Patch Set Exception

• Patch Set

A bundle patch is an official Oracle patch for an Oracle product. In a bundle patch release string, the fifth digit indicated the bundle patch number. Effective November 2015, the version numbering format has changed. The new format replaces the numeric fifth digit of the bundle version with a release date in the form "YYMMDD" where:

• YY is the last 2 digits of the year

• MM is the numeric month (2 digits)

• DD is the numeric day of the month (2 digits)

Each bundle patch includes the libraries and files that have been rebuilt to implement one or more fixes. All of the fixes in the bundle patch have been tested and are certified to work with one another. Regression testing has also been performed to ensure backward compatibility with all Oracle Mobile Security Suite components in the bundle patch.

In contrast to a bundle patch, a patch set exception addressed only one issue for a single component. Although each patch set exception was an official Oracle patch, it was not a complete product distribution and did not include packages for every component. A patch set exception included only the libraries and files that had been rebuilt to implement a specific fix for a specific component.

A patch set is a mechanism for delivering fully tested and integrated product fixes. A patch set can include new functionality. Each patch set includes the libraries and files that have been rebuilt to implement bug fixes (and new functions, if any). However, a patch set might not be a complete software distribution and might not include packages for every component on every platform. All of the fixes in a patch set are tested and certified to work with one another on the specified platforms.

You must satisfy the following requirements before applying this bundle patch:

• Confirm you are applying this bundle patch to an Oracle Identity Governance 12.2.1.3.0 installation.

  Note:

  When installing OPatch, you might find that interim or one off patches have already been installed.

• Download the latest version of OPatch. The OPatch version for this bundle patch is 12.2.1.3.0. However, Oracle recommends using the latest version of OPatch to all customers. To learn more about OPatch and how to download the latest version, refer to the following:

  You can access My Oracle Support at https://support.oracle.com.

• Verify the OUI Inventory. To apply patches, OPatch requires access to a valid OUI Inventory. To verify the OUI Inventory, ensure that ORACLE_HOME/OPatch appears in your PATH for example:

  export PATH=ORACLE_HOME/OPatch:$PATH 

  Then run the following command in OPatch inventory

  opatch lsinventory

  If the command returns an error or you cannot verify the OUI Inventory, contact Oracle Support. You must confirm the OUI Inventory is valid before applying this bundle patch.

• Confirm the opatch and unzip executables exist and appear in your system PATH, as both are needed to apply this bundle patch. Execute the following commands:

  which opatch
  which unzip

  Both executables must appear in the PATH before applying this bundle patch.

• Ensure that there are no pending JMS messages in Oracle Identity Governance server. You can monitor JMS messages with WebLogic console.

Applying Oracle Identity Governance Release 12.2.1.3.190624 patch is done in the following stages:

• Stage 1: Patching the Oracle Binaries (OPatch Stage)

• Stage 2: Filling in the patch_oim_wls.profile File

• Stage 3: Patching the Oracle Identity Governance Managed Servers (patch_oim_wls Stage)

• Understanding the Process Sequence With an Example

1. Stop the Admin Server, all Oracle Identity Governance managed servers, and all SOA managed servers.
2. Create a directory for storing the unzipped bundle patch. This document refers to this directory as PATCH_TOP.
3. Unzip the patch zip file in to the PATCH_TOP directory you created in step 2 by using the following command:

   unzip -d PATCH_TOP p29950141_122130_Generic.zip

   Note:

   On Windows, the unzip command has a limitation of 256 characters in the path name. If you encounter this issue, use an alternate ZIP utility, for example 7-Zip to unzip the zip file.

   Run the below command to unzip the file:

   "c:\Program Files\7-Zip\7z.exe" x p29950141_122130_Generic.zip
4. Move to the directory where the patch is located. For example:

   cd PATCH_TOP/29950141

5. Set the ORACLE_HOME directory in your system. For example:

   setenv ORACLE_HOME /u01/Oracle/Middleware

6. Apply the bundle patch to the ORACLE_HOME using the following command for Oracle Identity Governance:

   opatch apply

   Note:

   • Ensure the OPatch executables appear in your system PATH.

   • If OPatch fails with error code 104, cannot find a valid oraInst.loc file to locate Central Inventory, include the -invPtrLoc argument, as follows:

     opatch apply -invPtrLoc ORACLE_HOME/oraInst.loc

   When OPatch starts, it will validate the patch and ensure there are no conflicts with the software already installed in the ORACLE_HOME. OPatch categorizes two types of conflicts:

   • Conflicts with a patch already applied to the ORACLE_HOME. In this case, stop the patch installation and contact Oracle Support.

   • Conflicts with subset patch already applied to the ORACLE_HOME. In this case, continue the install, as the new patch contains all the fixes from the existing patch in the ORACLE_HOME. The subset patch will automatically be rolled back prior to the installation of the new patch.

     Note:

     For clustered and multi-node installation of Oracle Identity Governance, this step must be run on all the ORACLE_HOME directories on which Oracle Identity Governance is installed.

Using a text editor, edit the file patch_oim_wls.profile located in the directory ORACLE_HOME/server/bin/ directory and change the values in the file to match your environment. The patch_oim_wls.profile file contains sample values.

Table 1-1 lists the information to be entered for the patch_oim_wls.profile file. This file is used in next stage of the bundle patch process.

1. Make sure that the WebLogic Admin Server, SOA Managed Servers, and Oracle Identity Governance Managed Server are running.
2. Set the following environment variables:

   For LINUX or Solaris:

   setenv PATH $JAVA_HOME/bin:$PATH

   For Microsoft Windows:

   set JAVA_HOME=VALUE_OF_JAVA_HOME
   set ANT_HOME=\PATH_TO_ANT_DIRECTORY\ant
   set ORACLE_HOME=%MW_HOME%\idm

   Note:

   Make sure to set the reference to JDK binaries in your PATH before running the patch_oim_wls.sh (on UNIX) or patch_oim_wls.bat (on Microsoft Windows) script. This JAVA_HOME must be of the same version that is being used to run the WebLogic servers. The JAVA_HOME version from /usr/bin/ or the default is usually old and must be avoided. You can verify the version by running the following command:

   java -version

3. Execute patch_oim_wls.sh (on UNIX) or patch_oim_wls.bat (on Microsoft Windows) to apply the configuration changes to the Oracle Identity Governance server. On Linux systems, you must run the script in a shell environment using the following command:

   sh patch_oim_wls.sh

   Note:

   For EDG implementations, this script must be run against the mserver domain directory rather than the server domain directory.

4. Delete the following directory in domain home:

   IAMGovernanceDomain/servers/oim_server1/tmp/_WL_user/oracle.iam.console.identity.self-service.ear_V2.0

   Here, oim_server1 is the weblogic manged server used for OIG.

5. To verify that the patch_oim_wls script has completed successfully, check the ORACLE_HOME/idm/server/bin/patch_oim_wls.log log file.

   Note:

   • On running the patch_oim_wls script, the $DOMAIN_HOME/servers/MANAGED_SERVER/security/boot.properties file might be deleted. If you use a script to start the Managed Server and use the boot.properties file to eliminate the need of entering the password in the script, then create a new boot.properties file.

     In an EDG environment, the boot.properties file is in MSERVER_HOME/servers/MANAGED_SERVER/security.

   • Ignore the following exception traces in the patch_oim_wls.log file:

   [java] Aug 11, 2015 3:45:28 AM oracle.jdbc.driver.OracleDriver registerMBeans
        [java] WARNING: Error while registering Oracle JDBC Diagnosability MBean.
        [java] java.security.AccessControlException: access denied (javax.management.MBeanTrustPermission register)
        [java] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)

6. Stop and start WebLogic Admin Server, SOA Servers, and Oracle Identity Governance Servers.

   • Shutting down Oracle Identity Governance server might take a long time if it is done with force=false option. It is recommended that you force shutdown Oracle Identity Governance server.

   • The patch_oim_wls script is re-entrant and can be run again if a failure occurs.

1. Shutdown the Oracle Identity Governance, and ensure that the WebLogic Admin Server and SOA managed servers are running.
2. Run 'Opatch apply' on ORACLE_HOME_A. See Stage 1: Patching the Oracle Binaries (OPatch Stage) for more information.
3. Run 'Opatch apply' on ORACLE_HOME_B. See Stage 1: Patching the Oracle Binaries (OPatch Stage) for more information.
4. Fill-in the patch_oim_wls.profile file and run patch_oim_wls on ORACLE_HOME_A or ORACLE_HOME_B.

   See Stage 2: Filling in the patch_oim_wls.profile File for information on filling in the patch_oim_wls.profile.

   See Stage 3: Patching the Oracle Identity Governance Managed Servers (patch_oim_wls Stage) for information about running patch_oim_wls.

5. Restart the managed servers on all the nodes.

1. Perform the same verification steps and requirement checks that you made before applying the bundle patch. For example, backup the XML files and import them to a different location, verify the OUI Inventory and stop all services running from the ORACLE_HOME.
2. Move to the directory where the bundle patch was unzipped. For example:

   cd PATCH_TOP/29950141

3. Run OPatch as follows to remove the bundle patch:

   opatch rollback -id 29950141

4. Restore ORACLE_HOME, the WebLogic domain home from the backup created before applying the patch.
5. Restore the Oracle Identity Governance database using the backup you created in Step 1 of Applying the Bundle Patch to an Existing Instance.

Perform the following steps to apply the bundle patch to a new instance:

• Installing a New Oracle Identity Governance Instance with Bundle Patch 12.2.1.3.190624

• Postinstallation Configuration

• Updating Oracle Identity Governance Web Applications

1. Install Oracle WebLogic Server. See Installing and Configuring Oracle Identity and Access Management at the following URL:
   https://docs.oracle.com/en/middleware/idm/suite/12.2.1.3/inoam/index.html
2. Create the Oracle Identity Governance database schema. See Installing and Configuring Oracle Identity and Access Management.
3. Install SOA and Oracle Identity Governance. See Installing and Configuring Oracle Identity and Access Management.
4. Apply patch using Opatch, as described in Stage 1: Patching the Oracle Binaries (OPatch Stage).

   Note:

   If you are creating a new environment, then it is recommended that this step is performed before creating or extending the domain with Oracle Identity Governance.

5. Create domain by launching configuration wizard as specified in the Installing and Configuring Oracle Identity and Access Management.
6. Before starting the WebLogic Admin Server and SOA Server on Microsoft Windows, edit the startWeblogic.cmd file, and replace:

   call "%COMMON_ORACLE_HOME%\bin\wlst.cmd"           
   %COMMON_ORACLE_HOME%\tools\configureSecurityStore.py -d           
   %DOMAIN_HOME% -m validate

   With the following:

   call "FULL_PATH_TO_WLST_SCRIPT\wlst.cmd"
   %COMMON_ORACLE_HOME%\tools\configureSecurityStore.py -d
   %DOMAIN_HOME% -m validate

   Here, an example for FULL_PATH_TO_WLST_SCRIPT can be MW_HOME\oracle_common\common\bin\.

7. Start the WebLogic Admin Server and SOA Server.
8. Use Oracle Universal Installer to configure Oracle Identity Governance by running config.sh.
9. Stop and restart the WebLogic Admin Server and SOA Server.
10. Fill in the patch_oim_wls.profile file by referring to Stage 2: Filling in the patch_oim_wls.profile File.
11. Run patch_oim_wls.sh (on UNIX) and patch_oim_wls.bat (on Microsoft Windows) to complete patching the domain. This step must be run on the ORACLE_HOME directory of the Oracle Identity Governance Managed Server. For more information, see Stage 3: Patching the Oracle Identity Governance Managed Servers (patch_oim_wls Stage).

    Note:

    Before running the patch_oim_wls script, make sure that WebLogic Admin server and SOA servers are in running state.
12. Stop and restart the WebLogic Admin Server, SOA Server, and Oracle Identity Governance server.

After installing a new Oracle Identity Governance instance with Bundle Patch 12.2.1.3.190624, perform the following post installation configuration steps:

• Perform the following steps to seed the event handler for Application Onboarding:

  1. Go to, MW_HOME/idm/server/apps/oim.ear/APP-INF/lib/. 

  2. Locate BootStrapListener.jar. Copy the BootStrapListener.jar file to a temporary folder, for example temp_AoB. Extract the jar files and locate aob_adapters.xml file in the BootStrapListener.jar/scripts/ folder.

     Note:

     The jar file can be extracted using compression tool such as Zip,7–Zip or by using jar command jar -xvf .

  3. Copy the aob_adapters.xml file to a local folder.

  4. Using the Import option in Identity System Administration interface, import the aob_adapters.xml file into Oracle Identity Governance.

     For detailed steps for importing objects into Oracle Identity Governance, see Importing Deployments in Administering Oracle Identity Governance.

  5. Remove the temporary folder temp_AoB.

1. Stop Oracle Identity Governance Managed Server.
2. Login to WebLogic Administrative Console.
3. Click Lock & Edit.
4. Go to Deployments.
5. Select the oracle.iam.ui.view and oracle.iam.ui.model app, and click Update. Complete the steps of the wizard by clicking Next. Do not change anything.
6. Click Apply Changes.
7. Start Oracle Identity Governance Managed Server.

Before applying the bundle patch, perform the following prerequisites:

• This patch process makes changes to Oracle Identity Governance database schema (such as adding/modifying data), Oracle Identity Governance Meta Data Store (MDS) database schema (such as adding/modifying data), domain configuration changes, and other binary changes in the file system under ORACLE_HOME on which Oracle Identity Governance is installed. It is mandatory to create a backup of the following:

  • Oracle Identity Governance, MDS, and Service-Oriented Architecture (SOA) database schemas. For example, the database schema can be DEV_OIM, DEV_MDS schemas used by Oracle Identity Governance. Simple export of the schemas is sufficient.

  • The ORACLE_HOME directory on which Oracle Identity Governance is installed, for example, /u01/Oracle/Middleware.

  • Oracle Identity Governance WebLogic Domain location, for example, /u01/Oracle/Middleware/user_projects/domains/IAMGovernanceDomain/.

  • The UNIX user applying opatch must have read, write, and execute permissions on both ORACLE_HOME as well as WEBLOGIC_DOMAIN_HOME. You can verify this manually in the file system for DOMAIN_HOME and ORACLE_HOME.

• If you have customized the event handler file metadata/iam-features-configservice/event-definition/EventHandlers.xml in your setup, then perform the following steps to ensure that the upgrade does not override any customization done to this file:

  1. Export the metadata/iam-features-configservice/event-definition/EventHandlers.xml file from MDS, and create a backup of this file.

  2. After upgrading and running all the post install steps, export the new metadata/iam-features-configservice/event-definition/EventHandlers.xml file, merge your customization to this new file, and import it back to MDS.

  Note:

  For more information on MDS Utilities, see MDS Utilities and User Modifiable Metadata Files.

This bundle patch release supports integration of Oracle Identity Governance (OIG) and Oracle Access Manager (OAM) using Connectors. For more information see, Integrating Oracle Identity Governance and Oracle Access Manager Using LDAP Connectors in Integration Guide for Oracle Identity Management Suite.

Track Request functionality will change after this Bundle Patch is applied.

When a user performs a search in Self Service tab, Track Requests page, and in the search result table, applies Show list option as For Reportees, all the requests raised by or for the logged in user and user's direct and indirect reportee are displayed.

In the search result table, user has to select a Show list option and click Search. Oracle Identity Governance will not trigger a search action until user clicks on Search.

IP Filter (IPF) related updates are not part of the Oracle Identity Governance bundle patch release. For instructions on how to download and applying the IPF one-off bundle patch, see My Oracle Support document ID 2383246.1.

1. Manually copy the contents of $PATCH_DIRECTORY/files/oracle.oim.server/12.2.1.3.0/oracle.oim.symbol/server/reports/oim_product_BIPReports_12c.zip/* directory to the $BI_DOMAIN_HOME/bidata/components/bipublisher/repository/Reports/ directory.
2. Restart the BI server.

Oracle Identity Governance 12c (12.2.1.3.190624) is certified with Microsoft Internet Explorer 11. To use Oracle Identity Governance with Internet Explorer 11, download and apply ADF patch 29620828 from My Oracle Support web site at:

https://support.oracle.com

For information about this patch, see Tech Note OIG 12c certification with IE11 browser (Doc ID 2556385.1) at My Oracle Support web site at:

https://support.oracle.com

The following are the major enhancements up to Release 12.2.1.3.190109:

• Major Enhancements in Release 12.2.1.3.190109

• Major Enhancements in Release 12.2.1.3.180713

A new parameter, opss_customizations_present is introduced which controls the seeding of data from jazn-data.xml to OPSS database through post patch automation script. The default value of this parameter is false. If this parameter is set to false, then data from jazn-data.xml in the Bundle Patch is seeded to the OPSS database through post patch automation script.

If the environment contains customizations to workflows or custom task flows, then set the value of opss_customizations_present to true and then, manually seed the data from jazn-data.xml into OPSS database . For instructions see, My Oracle Support document ID 2472116.1.

In the Self Service Roles page, when you create a UDF to add a Checkbox type attribute in the Catalog Attributes tab, the Apply button is enabled when navigating between the attributes tab of the role. To overcome this issue, a new change listener catReqBean.checkBoxChangeListener is introduced in this bundle patch release.

The following section lists the issues resolved in Release 12.2.1.3.190624:

• Resolved Issues in Release 12.2.1.3.190624

• Resolved Issues in Release 12.2.1.3.190109

• Resolved Issues in Release 12.2.1.3.180920

• Resolved Issues in Release 12.2.1.3.180713

• Resolved Issues in Release 12.2.1.3.180413

• Resolved Issues in Release 12.2.1.3.180109

Applying this bundle patch resolves the issues listed in Table 1-3:

Applying this bundle patch resolves the issues listed in Table 1-4:

Applying this bundle patch resolves the issues listed in Table 1-5:

Applying this bundle patch resolves the issues listed in Table 1-6:

Applying this bundle patch resolves the issues listed in Table 1-7.

Known issues and their workarounds in Oracle Identity Governance Release 12.2.1.3 are described in the Oracle Identity Governance chapter of the Release Notes for Oracle Identity Management document. You can access the Release Notes document in the Oracle Identity Management Documentation library at the following URL:

https://docs.oracle.com/middleware/12213/idmsuite/IDMRN/toc.htm

This section describes the issues and workarounds in this BP release of Oracle Identity Governance:

• LDAP User Create and Update Reconciliation Job Fails in Integrated and Upgraded Environment

• IT Resource Password is Updated as Null

• Recommendations for Upgrade

• Oracle Identity Governance Server URL is Inaccessible After Rollback

• Role Hierarchy Tab Shows Only 301 Roles

• Customizing the Fetch Size in Add Members Tab of Roles Page Results in Search Issue

• Manual Update of Refreshing Materialized View Fails

• Identity Self Service and Identity System Administration are Inaccessible After Upgrading OPatch Version

Few upgrade bugs are resolved in this bundle patch release, 27113693, 27119830, 27145500, and 27168000. See Resolved Issues in Release 12.2.1.3.180413.

Pre-upgrade report will be generated if any of the issue stated in above bugs exists in a Oracle Identity Manager 11gR2PS3 setup prior to upgrading it to Oracle Identity Governance 12.2.1.3.0 version. For automated fix of these upgrade bugs, please apply the Bundle Patch Release 12.2.1.3.180413 binaries on top of Oracle Identity Governance 12.2.1.3.0 binaries and then proceed with Oracle Identity Governance 12.2.1.3.0 upgrade process. Steps for manual fix are present in pre-upgrade reports.

After upgrading the OPatch version from 13.9.2.0.0 to 13.9.4.0.0, Identity Self Service and Identity System Administration cannot be accessed because of a mismatch in the versions of the com.oracle.cie.com*.jar file.

For more information about this issue and a workaround, see Tech Note OIM 12c: OIM Consoles Do Not Come Up After Upgrading OPatch Version From 13.9.2.0.0 to 13.9.4.0.0 Due to com.oracle.cie.com*.jar (Doc ID 2535244.1) at the My Oracle Support web site at:

https://support.oracle.com

For more information, see the following resources:

• Oracle Fusion Middleware Documentation

  This contains documentation for all Oracle Fusion Middleware 12c products.

• Oracle Technology Network

  This site contains additional documentation that is not included as part of the documentation libraries.

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.