Oracle Fusion Middleware Oracle Identity Governance Bundle Patch Readme, OIM Bundle Patch 12.2.1.3.220115

This document is intended for users of OIM Bundle Patch 12.2.1.3.220115. It contains the following sections:

Note:

For issues documented after the release of this OIM BUNDLE PATCH 12.2.1.3.220115, see My Oracle Support Document 2568304.1, Oracle Fusion Middleware 12.2.1.3.0 Known Issues (Doc ID 2568304.1) at the following URL:

https://support.oracle.com

Understanding Bundle Patches
Recommendations
Bundle Patch Requirements
Prerequisites of Applying the Bundle Patch
Applying the Bundle Patch to an Existing Instance
Removing the Bundle Patch
Applying the Bundle Patch to a New Instance
Configuring Oracle Identity Governance-Oracle Access Manager Integration (Optional)
Changes in Track Request Functionality
IP Filter Related Updates
Copying the Oracle Identity Governance Reports ZIP Directory
Internet Explorer 11 Certification
Bulk Load Utility for Loading Accounts
Steps to Map the Role and employeeType Attributes
Access Policy Harvesting for Direct Provisioned and Request Created Accounts
Access Policy Harvesting to Enable Account Data Update
Major Enhancements
Resolved Issues
Known Issues and Workarounds
Related Documents
Documentation Accessibility

1.1 Understanding Bundle Patches

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

1.1.1 Bundle Patch

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.

1.1.2 Patch Set Exception

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.

1.1.3 Patch Set

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.

1.2 Recommendations

Oracle has certified the dependent Middleware component patches for Identity Management products and recommends that you apply these certified patches. For more information about these patches, see Certification of Underlying or Shared Component Patches for Identity Management Products (Doc ID 2627261.1) at https://support.oracle.com.

1.3 Bundle Patch Requirements

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

Verify that 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 13.9.4.2.7. 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.

1.4 Applying the Bundle Patch to an Existing Instance

Applying OIM Bundle Patch 12.2.1.3.220115 patch is done in the following stages:

Note:

Before performing the steps to apply the bundle patch, create a backup of the database, as stated in Prerequisites of Applying the Bundle Patch which will help you rollback to the previous release.

Understanding the Process Sequence With an Example
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)

1.4.1 Understanding the Process Sequence With an Example

If you have ORACLE_HOME_A and ORACLE_HOME_B, and ORACLE_HOME_A is running WebLogic Admin Server, oim_server1, and soa_server1, and ORACLE_HOME_B is running oim_server2 and soa_server2, then the following is the process sequence to apply the bundle patch to the Oracle Identity Governance instance:

Shutdown Oracle Identity Governance server, WebLogic Admin Server, and SOAMmanaged Server.
Run 'Opatch apply' on ORACLE_HOME_A. See Stage 1: Patching the Oracle Binaries (OPatch Stage) for more information.
Run 'Opatch apply' on ORACLE_HOME_B. See Stage 1: Patching the Oracle Binaries (OPatch Stage) for more information.
Fill-in the patch_oim_wls.profile file and run patch_oim_wls on ORACLE_HOME_A with WebLogic Admin Server, oim_server1, and soa_server1 running. The rest of the servers on other nodes can be down.

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.
Restart the managed servers on all the nodes.

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

This section describes the process of applying the binary changes by copying files to the ORACLE_HOME directory, on which Oracle Identity Governance is installed. This step must be executed for each ORACLE_HOME in the installation topology nodes irrespective of whether Oracle Identity Governance server is being run in the node or not.

Perform the following steps to apply the bundle patch to an existing Oracle Identity Governance instance:

Stop the Admin Server, all Oracle Identity Governance managed servers, and all SOA managed servers.
Create a directory for storing the unzipped bundle patch. This document refers to this directory as PATCH_TOP.
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 p33757401_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 p33757401_122130_Generic.zip
Move to the directory where the patch is located. For example:
```
cd PATCH_TOP/33757401
```
Set the ORACLE_HOME directory in your system. For example:
```
setenv ORACLE_HOME /u01/Oracle/Middleware
```
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.

1.4.3 Stage 2: Filling in the patch_oim_wls.profile File

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.

Note:

For clustered and multinode installation of Oracle Identity Governance, perform the step described in this topic on the ORACLE_HOME_A directory on which Oracle Identity Governance is installed. This is because you need to run the patch_oim_wls script from the node with WebLogic Admin Server, oim_server1, and soa_server1 installed. In the patch_wls_oim.profile file, mention the host and port of the Oracle Identity Governance server and SOA server running on the first node. When you run the script, only WebLogic Admin Server, oim_server1, and soa_server1 should be running, and the rest of the servers can be down.

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.

Table 1-1 Parameters of the patch_oim_wls.profile File

Parameter	Description	Sample Value
ant_home	Location of the ANT installation. It is usually under MW_HOME.	For Linux: $MW_HOME/oracle_common/modules/thirdparty/org.apache.ant/1.9.8.0.0/apache-ant-1.9.8/ For Windows: %MW_HOME%\oracle_common\modules\thirdparty\org.apache.ant\1.9.8.0.0\apache-ant-1.9.8\
java_home	Location of the JDK/JRE installation that is being used to run the Oracle Identity Governance domain.	For Linux: $MW_HOME/oracle_common/jdk/ For Windows: %MW_HOME%\oracle_common\jdk\
mw_home	Location of the middleware home location on which Oracle Identity Governance is installed.	For Linux: /u01/Oracle/Middleware For Windows: C:\Oracle\MW_HOME\
oim_oracle_home	Location of the Oracle Identity Governance installation.	For Linux: $MW_HOME/idm For Windows: %MW_HOME%\idm
oim_username	Oracle Identity Governance username.	System administrator username
oim_password	Oracle Identity Governance password. This is optional. If this is commented out, then you will be prompted for the password when the script is executed.	N/A
oim_serverurl	URL to navigate to Oracle Identity Governance.	t3://oimhost.example.com:14000
soa_home	Location of the SOA installation.	For Linux: $MW_HOME/soa For Windows: %MW_HOME%\soa
weblogic.server.dir	Directory on which WebLogic server is installed.	For Linux: $MW_HOME/wlserver For Windows: %MW_HOME%\wlserver
weblogic_user	Domain administrator user name. Normally it is weblogic, but could be different as well.	weblogic
weblogic_password	Domain admin user's password. If this line is commented out, then password will be prompted.	N/A
soa_host	Listen address of the SOA Managed Server, or the hostname on which the SOA Managed Server is listening. Note: If the SOA Managed Server is configured to use a virtual IP address, then the virtual host name must be supplied.	oimhost.example.com
soa_port	Listen port of the SOA Managed Server, or SOA Managed Server port number.	8001 Only Non-SSL Listen port must be provided.
operationsDB.user	Oracle Identity Governance database schema user.	DEV_OIM
OIM.DBPassword	Oracle Identity Governance database schema password. If this line is commented out, then the password will be prompted when the script is executed.	N/A
operationsDB.host	Host name of the Oracle Identity Governance database.	oimdbhost.example.com
operationsDB.serviceName	Database service name of the Oracle Identity Governance schema/database. This is not the hostname and it can be a different value as well.	oimdb.example.com
operationsDB.port	Database listener port number for the Oracle Identity Governance database.	1521
opss_customizations_present	Enables customizations related to authorization or custom task flow. Set this value to true to enable customization.	true
mdsDB.user	MDS schema user	DEV_MDS
mdsDB.password	MDS schema password. If this line is commented out, then password will be prompted.	N/A
mdsDB.host	MDS database host name	oimdbhost.example.com
mdsDB.port	MDS database/Listen port	1521
mdsDB.serviceName	MDS database service name	oimdb.example.com
wls_serverurl	URL to navigate to WLS Console	t3://wlshost.example.com:7001

Note:

Updated the parameter value as per the setup used and then execute the patch_oim_wls.sh file.

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

Patching the Oracle Identity Governance managed servers is the process of copying the staged files in the previous steps (stage 1) to the correct locations, and running SQL scripts and importing event handlers and deploying SOA composite. For making MBean calls, the script automatically starts the Oracle Identity Governance Managed Server and SOA Managed Server specified in the patch_oim_wls.profile file.

This step is performed by running patch_oim_wls.sh (on UNIX) and patch_oim_wls.bat (on Microsoft Windows) script by using the inputs provided in the patch_oim_wls.profile file. As prerequisites, the WebLogic Admin Server, SOA Managed Server, and Oracle Identity Governance Managed Server must be running.

Note:

For clustered and multinode installation of Oracle Identity Governance, perform the steps described in this topic on the ORACLE_HOME_A directory on which Oracle Identity Governance is installed. In other words, run the patch_oim_wls script from the node with WebLogic Admin Server, oim_server1, and soa_server1 installed. When you run the script, only WebLogic Admin Server, oim_server1, and soa_server1 should be running, and the rest of the servers can be down.

To patch Oracle Identity Governance Managed Server on WebLogic:

Make sure that the WebLogic Admin Server, SOA Managed Server, and Oracle Identity Governance Managed Server are running.
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
```
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.
Delete the following two directories from the domain home:
- IAMGovernanceDomain/servers/oim_server1/tmp
- IAMGovernanceDomain/servers/AdminServer/tmp
Here, oim_server1 is the weblogic managed server used for OIG.
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)
```
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.5 Removing the Bundle Patch

If you must remove the bundle patch after it is applied, then perform the following steps:

Note:

For clustered installations, perform steps 1 through 3 on all nodes in the cluster.

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.
Move to the directory where the bundle patch was unzipped. For example:
```
cd PATCH_TOP/33757401 
```
Run OPatch as follows to remove the bundle patch:
```
opatch rollback -id  33757401 
```
Restore ORACLE_HOME, the WebLogic domain home from the backup created before applying the patch.
Restore the Oracle Identity Governance database using the backup you created in Step 1 of Applying the Bundle Patch to an Existing Instance.

1.6 Applying the Bundle Patch to a New Instance

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

Installing a New Oracle Identity Governance Instance with OIM Bundle Patch 12.2.1.3.220115
Postinstallation Configuration
Updating Oracle Identity Governance Web Applications

1.6.1 Installing a New Oracle Identity Governance Instance with OIM Bundle Patch 12.2.1.3.220115

Perform the following steps to apply the bundle patch to a new Oracle Identity Governance instance. You can perform the same steps for clustered deployments.

Note:

For clustered deployments, perform the steps provided in this section on each node in the cluster.

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
Create the Oracle Identity Governance database schema. See Installing and Configuring Oracle Identity and Access Management.
Install SOA and Oracle Identity Governance. See Installing and Configuring Oracle Identity and Access Management.
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.
Create domain by launching configuration wizard as specified in the Installing and Configuring Oracle Identity and Access Management.

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\.

Start the WebLogic Admin Server and SOA Server.
Use Oracle Universal Installer to configure Oracle Identity Governance by running config.sh.
Stop and restart the WebLogic Admin Server and SOA Server.
Fill in the patch_oim_wls.profile file by referring to Stage 2: Filling in the patch_oim_wls.profile File.
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.
Stop and restart the WebLogic Admin Server, SOA Server, and Oracle Identity Governance server.

1.6.2 Postinstallation Configuration

After installing a new Oracle Identity Governance instance with OIM Bundle Patch 12.2.1.3.220115, 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.6.3 Updating Oracle Identity Governance Web Applications

The procedure described in this section is applicable only when installing bundle patches for Oracle Identity Governance and not for installing patch set updates.

For updating your web applications on Oracle WebLogic Server:

Stop Oracle Identity Governance Managed Server.
Login to WebLogic Administrative Console.
Click Lock & Edit.
Go to Deployments.
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.
Click Apply Changes.
Start Oracle Identity Governance Managed Server.

1.6.4 Prerequisites of Applying the Bundle Patch

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.

1.7 Configuring Oracle Identity Governance-Oracle Access Manager Integration (Optional)

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.

1.8 Changes in Track Request Functionality

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.

Note:

The Organization Name field works only with the For Reportees feature.
While using the Organization Name search criteria, at least one direct reportee should be associated with the organization. See Errors Related to the For Reportees Feature for the error message that is displayed when an organization name outside the reportee's organization is entered.
Only two levels of reportees are considered, direct reportees and their immediate reportees
The total number of direct reportees and indirect reportees must not exceed 1000. See Errors Related to the For Reportees Feature for the error message that is displayed if the number of direct reportees and indirect reportees are more than 1000.

1.9 IP Filter Related Updates

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.10 Copying the Oracle Identity Governance Reports ZIP Directory

Under the Request Summary page of BIP reports URL, when the Request Type is Revoke Entitlement with request start date and request end date, the Request Details column shows the entitlement number instead of the entitlement name. This issue has been fixed (bug 25695572) in this bundle patch. For the bug fix 25695572 to work:

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.
Restart the BI server.

1.11 Internet Explorer 11 Certification

This bundle patch 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

1.12 Bulk Load Utility for Loading Accounts

With the fix for bug# 30145982 in the bundle patch, the Bulk Load Utility for loading account data asks for the following input:

Note:

The requirement to run the Bulk Load Utility for account data has the following requirements:

Oracle Identity Governance server is running.
The MW_HOME and OIM_ORACLE_HOME paths must be accessible although they are running on different hosts.

Before running the utility, perform the following steps
1. Edit the oim_blkld_accounts.sh script, and add the following lines, and save the script.
```
$MW_HOME/wlserver/server/lib/wlfullclient.jar
$MW_HOME/oracle_common/modules/javax.management.j2ee.jar
```
2. Generate wlfullclient.jar if it is not available in the MW_HOME/server/lib/ directory, and grant execute (755) permisssions to the file.
Enter the MW_HOME directory or Press [Enter] to accept the default.
Enter the OIM_ORACLE_HOME directory or Press [Enter] to accept the default.
Enter the hostname on which OIG is running :

It is mandatory that OIG is running on the same host.
Enter the port where OIG server is running :

The default port is 14000.
Enter the path of OIM_HOME.
Enter the OIG system administrator user name.
Enter the OIG system administrator password.

1.13 Steps to Map the Role and employeeType Attributes

If the bundle patch is applied after the OAM-OIG integration, then for the bug fix 31162758 to work, perform the following steps to map the Role attribute to the employeeType attribute:

Login to Oracle Identity Self Service.
Click the Manage tab, and then click the Applications box to open the Applications page.
Search for SSOTrusted-for-SSOTargetApp and open it.
Click the Schema tab.
Map Role to employeeType.
Save the changes.

If the bundle patch is applied to OIG before the integration with OAM, then the manual mapping of the attributes are not required.

1.14 Access Policy Harvesting to Enable Account Data Update

As a fix for bug# 30978612 in the bundle patch, the new XL.APHarvesting.AllowAccountDataUpdate system property is available to update the account data with the policy defaults for the accounts linked to the access policies. This system property has the following details:

Name: XL.APHarvesting.AllowAccountDataUpdate

Keyword: XL.APHarvesting.AllowAccountDataUpdate

Default value: FALSE

When this system property is set to TRUE, the account data is updated with the policy defaults for the accounts linked to access policy. If set to FALSE or if the system property does not exist, the account data is not updated.

To enable updating the account data with the policy defaults for the accounts linked to the access policies, set the values of the XL.APHarvesting.AllowAccountDataUpdate, XL.AllowAPHarvesting, XL.APHarvestRequestAccount, XL.APHarvestDirectProvisionAccount, and XL.AllowAPBasedMultipleAccountProvisioning system properties to TRUE.

1.15 Access Policy Harvesting for Direct Provisioned and Request Created Accounts

As a fix for bug# 27599841, you can link access policies to accounts created by request and to accounts that are provisioned directly.

To enable linking access policies to accounts created by request, set the values of XL.APHarvestRequestAccount, XL.AllowAPHarvesting, and XL.AllowAPBasedMultipleAccountProvisioning system properties to TRUE.

To enable linking access policies to accounts that are provisioned directly, set the values of XL.APHarvestDirectProvisionAccount, XL.AllowAPHarvesting, andXL.AllowAPBasedMultipleAccountProvisioning system properties to TRUE.

1.16 Major Enhancements

The following are the major enhancements up to Release 12.2.1.3.2201XX:

Major Enhancements in Release 12.2.1.3.210329
Major Enhancements in Release 12.2.1.3.190109
Major Enhancements in Release 12.2.1.3.180713

1.16.1 Major Enhancements in Release 12.2.1.3.210329

When users are disabled, Oracle Identity Governance handles tasks without losing the assignments although the target assignee of the task being initiated is already disabled, or the current assignee of the pending tasks is being disabled. The type of tasks can be one of request/approval task, identity audit (IDA) scan violation, or certification. See Use Cases for Disabled or Deleted Proxy Users in Administering Oracle Identity Governance for more information.

1.16.2 Major Enhancements in Release 12.2.1.3.190109

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.

1.16.3 Major Enhancements in Release 12.2.1.3.180713

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.

1.17 Resolved Issues

The following section lists the issues resolved in OIM Bundle Patch 12.2.1.3.220115:

Resolved Issues in OIM Bundle Patch 12.2.1.3.220115
Resolved Issues in OIM Bundle Patch 12.2.1.3.211001
Resolved Issues in OIM Bundle Patch 12.2.1.3.210713
Resolved Issues in OIM Bundle Patch 12.2.1.3.210329
Resolved Issues in OIM Bundle Patch 12.2.1.3.210107
Resolved Issues in OIM Bundle Patch 12.2.1.3.201006
Resolved Issues in OIM Bundle Patch 12.2.1.3.200627
Resolved Issues in OIM Bundle Patch 12.2.1.3.0 (ID:200108.2108)
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

1.17.1 Resolved Issues in OIM Bundle Patch 12.2.1.3.220115

Applying this bundle patch resolves the issues described in Table 1-2.

Table 1-2 Resolved Issues in OIM Bundle Patch 12.2.1.3.220115

Bug	Bug Abstract
31155251	REQUESTS GETS FAILED IN IDENTITY MANAGER
32065363	PREVENT SELF CERTIFICATION IS NOT WORKING ON REASSIGNMENT OF ENT TYPE CERT
32390472	OIG PRE-UPGRADE REPORTS INCORRECTLY IDENTIFIES 19C DB AS UNSUPPORTED VERSION FOR OIM 11GR2PS3 WHILE UPGRADING TO 12C
32670128	ADDING ADDITIONAL ENTITLEMENTS TO AP DOESN'T RE-EVALUATE AND ADD TO USER
32717850	DISABLED USERS SHOULD NOT BE EVALUATED BY ACCESS POLICY
33066536	OIM TRUSTERD DELETE RECON UNEXPECTED TO DELETE OIM USERS
33171625	CHALLENGE QUESTIONS GIVES ERROR WHEN USER DEFINED IS SELECETD IN PASSWORD POLICY
33276969	POST UPGRADE 12CPS4 OIM SERVERS GOING TO WARNING STATE AND AUTO-HEALED
33407956	Fix for Bug 33407956
33417218	OIG 12CPS4 OCT BP , ROLLBACK REAPPLY IS CHANGING THE STATUS OF CERTIFICATION TO STALE
33419121	MODIFY ADF CACHE SIZE CONFIGURATION FOR TABS
33428494	UPDATES TO USER (USR) NOT PROPAGATED TO ACCOUNTS IN 'PROVISIONING' STATUS
33452123	USER ROLE GOT REVOKED, FOR A VALID 'USER MEMBERSHIP RULE'
33462000	JPS-CONFIG.XML CONTAINS LEFT OVER OAM 11G INFO CAUSING ISSUES WITH 12C
33465669	NPE ERROR WHILE STARTING OIM AFTER UA IF ORACLE_HOME IS INVALID
33471784	BOOTSTRAP PROCESS FAILS DURING DEPLOYSOACOMPOSITES DUE TO CONNECTION NOT AVAILABLE
33474286	VALIDATION OF OPSS VERSION NEEDED IN PRE-UPGRADE REPORT

1.17.2 Resolved Issues in OIM Bundle Patch 12.2.1.3.211001

Applying this bundle patch resolves the issues described in Table 1-3.

Table 1-3 Resolved Issues in OIM Bundle Patch 12.2.1.3.211001

Bug Number	Description
28545612	ENT_ASSIGN_HIST DOESN'T SAY HOW THE USER ACCESS IS PROVISIONED
29660851	REGRESSION ON BUG 27532579 - WRONG ENTRY IN AUDIT_EVENT FOR ROLEMANAGER.REVOKE
30043034	OIM USER FORM DATE UDF ATTRIBUTE NOT FUNCTIONING PROPERLY IN SSO ENV
30110645	AOB: REMOVAL OF A CHILD FORM REMOVES TASKS FROM OTHER APPLICATIONS
30155470	OIG 12.2.1.3.190624 REST API REQUESTS RETURNING ERROR WITH CUSTOM COMPOSITE
30161980	Fix for Bug 30161980
30930007	EXPERIENCING VERY SLOW PERFORMANCE WHEN SCANNING SOD POLICIES WITH 4.5K RULES.
30952309	ENTITLEMENT REQUEST STUCK IN REQUEST AWAITING DEPENDENT REQUEST COMPLETION
31038511	CERTIFICATION REASSIGNED OR DELEGATED RESETS TIME SEE EH 27284033
31342188	USER IS NOT CREATING IN LDAP POST SOA APPROVAL
31464255	SOD VALIDATION AGAINST ENTITLEMENTS WHICH ARE REQUESTED
31928115	SSO INCREMENTAL RECON CAUSES OBPASSWORDEXPIRYDATE TO DECREASE BY ONE DAY
32245266	ORGANIZATION TYPE NOT TRANSLATED TO BROWSER LOCALE IN SEVERAL AREAS OF THE UI
32258285	PROVISIONING OPEN TASKS SEARCH DOES NOT GET THE TASK STATUS TRANSLATED TO POLISH
32288237	PERFORMANCE ISSUE WITH PASSWORD RESET IN SSO ENVIRONMENT (12C) . Note: For details, see Improving Reset Password Performance on AD Integration.
32322591	AUTO-LOGIN FUNCTIONALITY NOT WORKING FOR OIM OAM INTEGRATED ENVIRONMENT
32324514	INTERFACE PROVISIONINGSERVICE.GETACCOUNTSPROVISIONEDTOUSER THROWS NPE
32386512	PRE-UPGRADE REPORT SHOWS "OBSELETE" REPORTS NO LONGER REQUIRED.
32393962	SSOTARGET PROVISIONING TRANSFORMATION SCRIPT TRUNCATING DATE CAUSING INCONSISTENCY BETWEEN USR_PWD_EXPIRE_DATE AND OBPASSWORDEXPIRYDATE
32441440	ORGANIZATION TYPE NOT TRANSLATED TO BROWSER LOCALE IN SEVERAL AREAS OF THE UI
32461462	OIM API NOT EXPOSING METHOD TO DECRYPT ENCRYPTED UDF
32586438	PROCESS TRIGGER NOT FIRING FOR END DATE
32710741	SSOTRUSTEDFORSSOTARGET RECON EVENT FAILS WITH INVALID MANAGERLOGIN ERROR
32739454	PRE-UPGRADE REPORTS CONTAINS UNWANTED OIM12CPS3 BP02 INFORMATION
32747711	OAM / OIM AD MODIFIED USER IS RECONCILED LIKE {BASE=DISPLAYNAME}
32764414	REST REQUEST FOR PENDINGAPPROVAL AND TASKID NOT WORKING AS DOCUMENTED
32764420	NEED WORKING EXAMPLE OF SCHEDULERSERVICE.CREATESCHEDULEDTASK(ST)
32806846	MULTIPLE MANUAL REVOKE ENTITLEMENT TASKS GENERATED FOR ACCESS POLICY DISABLE
32843595	ORGANIZATION TYPE/STATUS IN MANAGE - APPLICATION AREA PAGES NOT TRANSLATED TO BROWSER LOCAL
32903652	UNINSTALLCONNECTOR DELETE ONE RESOURCEOBJECT RESULT IN ALL ITRESOURCE OF SAME CONNECTOR TYPE REMOVED
33000675	DIAG: NEED DIAGNOSTIC PATCH IN ACCESSPOLICYSERVICEIMPL.UPDATEACCESSPOLICY/PROCESSWITHOUTRESULT
33005552	NPE IN DELAYED DELETE USER WITH JOB HISTORY JOB USERAUDITHANDLER
33089742	ROLES DISPLAY EVEN WITH OIG.DEFAULTUSERSEARCHDISABLED = TRUE
33119876	NEED TO SHOW APPLICATION INSTANCE DISPLAY NAME IN THE ERROR MESSAGE SHOWN IN UI (AS PER BUG 30952309)
33120542	PREUPGRADEUTILITY IS FAILING WITH COMPATABLE_PARAMETER_CHECK ERROR
33165095	ORGANIZATION SEARCH ERROR IN OIM 12.2.1.4.210428
33214891	USER CREATION FAILS IN OIM 12C WHEN REQUESTENTITY API IS USED
33225499	DISABLED USERS WITH PAST END DATE NOT GETTING USR_AUTOMATICALLY_DELETE_ON SET
33321617	UNABLE TO CREATE ROLE WHEN ENFORCESINGLEACCOUNTPERAPPLICATIONREQUEST IS SET TO TRUE
33330315	PROPERTIES TRANSLATED FOR POLISH ARE DIFFERENT THAN WHAT IT TRANSLATED EARLIER

1.17.3 Resolved Issues in OIM Bundle Patch 12.2.1.3.210713

Applying this bundle patch resolves the issues described in Resolved Issues in OIM Bundle Patch 12.2.1.3.210713.

Table 1-4 Resolved Issues in OIM Bundle Patch 12.2.1.3.210713

Bug Number	Description
28193520	STRESS:OIM LOGIN TAKING MORE THAN 5MINS FOR MGR WITH MANY DIRECT REPORTS
28882181	ARM_AUD TABLE NOT UPDATED DURING ADMIN ROLE ASSIGNMENT
30235801	PASSWORD RESET IN MYINFORMATION CLEARS FIELDS MOST OF TIME AND APPLY INACTIVE
30265046	OIG SUBMIT BUTTON OF IDENTITY FIRST LOGIN PAGE SHOULD BE THE LAST READING ORDER
30516224	IDENTITY AUDIT RULES CONTAINING SPECIAL CHARS DO NOT RAISE POL. VIOLATION
31397729	DIAG:QUARTZTRIGGERLISTENER.TRIGGERMISFIRED DOES NOT DISPLAY TRIGGER NAME
31525878	OIM 12C SSO USER TARGET RECON OVERWRITING "ORGANIZATION NAME" VALUE WITH "XELLERATE USERS" DEFAULT VALUE
31656655	MISSING REQESTER ID LEADS TO REQUEST FAIL
31683884	"FOR REPORTEES" OPTION IS NOT TRANSALATED TO BROSWER LANAGUGE
31724255	Fix for Bug 31724255
31732078	IAM-3054101 : THE LOGGED-IN USER DOES NOT HAVE VIEWSEARCHENTITY PERMISSION
31784882	CUSTOM TASKFLOW MESSAGE OVERWRITTEN BY DEFAULT MESSAGE
31984036	CANNOT DISABLE OBJECT INSTANCE AS IT IS ALREADY DISABLED
32018230	DISAPPEARING REPORTS IN BI PUBLISHER - ONLY IDENTITY AUDIT REPORTS SHOW WHEN UI
32178264	"BULK LOAD POST PROCESS" JOB SETTING DIFFERENT PWDS FOR OIM USER -VS- SSOTARGET
32285418	TRACK REQUEST FOR REPORTEES NOT TRANSLATED TO POLISH
32513700	INCONSISTENCY DATE FORMAT BETWEEN TRACK REQUESTS AND REQUEST DETAILS FOR REQUESTED DATE FIELD
32408854	PUMA: TEST CONNECTION FAILS FOR DBUM INSTANCE
32527571	WRONG KEY WHEN FETCH THE ERROR MESSAGE TRIGGERS MISSINGRESOURCEEXCEPTION
32534109	CAN'T CHANGE/UPDATE ATTRIBUTES ON AOB SCHEMA
32535086	ORGANIZATION SEARCH IS NOT WORKING FOR END USER OTHER THAN XELSYSADM
32549885	BUG IN ACCESSPOLICYSERVICE API, FUNCTION GETACCESSPOLICY LIMIT TO 1024
32635254	OIM CN GENERATION LOGIC FAILS TO GENERATE UNIQUE CN USING SPECIAL CHARS
32704620	REVOKING ROLE VIA CERTIFICATION PROCESS IS NOT GENERATING REQUEST TO REMOVE ROLE
32705847	ATTRIBUTE VALUES IS NOT VISIBLE IN PENDING VIOLATION TASK VIEW
33098284	AOB SCHEMA UI IS NOT RENDERRED FOR AUTHORITATIVE TARGET

1.17.4 Resolved Issues in OIM Bundle Patch 12.2.1.3.210329

Applying this bundle patch resolves the issues described in Table 1-5.

Table 1-5 Resolved Issues in OIM Bundle Patch 12.2.1.3.210329

Bug Number	Description
16755363	IDMUPG:PS5-PS6:OIM UPGRADE SCRIPT THROWS NPE AFTER APPLYING PATCH 16609934
28027119	REVOKELDAPENTITLEMENTPOSTPROCESSHANDLER FAILING WHILE PARSING THE ENT NAME
28583697	INABILITY TO ADD COMMENTS FOR APPROVALS IN REST API
28608373	OIG 12C REST SEARCH SERVICE DOES NOT LIST THE USER.
28819255	CREATION OF THOUSANDS OF UNEXPLAINED UPDATE TASKS
28974361	COM.ORACLE.CIE.SERVICE-TABLE-SCHEMA LIBRARY ERROR AFTER 19C UPGRADE ON LATEST IDM
30054791	ADMIN ROLE ACCESS POLICY VIEWER ALLOWS USER TO START CHANGING
30141533	CREATE ADMIN ROLE ERROR
30272992	FEW REQUESTS MOVED TO FAILED STATUS WITH AUTO APPROVAL WORKFLOW
30586440	NPE ERRORS WHILE CREATE ADMIN ROLE ERROR
30674852	ROLE CERTIFICATION FAILS USING ACCESS POLICY WITH MULTIPLE APPLICATION INSTANCES WITH THE SAME ENDPOINT
30773475	OIM ORGANIZATION GETTING DISABLED INTERMITTENTLY IN PRODUCTION .
30959040	IMPORT OF THE EXPORTED ACCESS POLICY ASSIGNS TO DIFFERENT APPLICATION INSTANCE
31070814	OIM DATA PURGE JOB FAILS WHILE PURGING THE RECON DATA FROM RA TABLES
31467891	ACCESS POLICY EVALUATION INITIATES PROCESS TASKS FOR NULL CHECKBOX VALUES
31626677	OIMDBPLUGIN NOT INTERPRETING ESCAPED PARENTHESIS IN GROUP NAMES IN LDAP QUERY CORRECTLY
31838518	AUTOMATICALLY UNLOCK USER SCHEDULE JOB RESETS OBLOGINTRYCOUNT BUT NOT OBLOCKEDON
31855240	ACCESS POLICY CACHE IS NOT UPDATED AFTER A CHANGES
31903352	OIM HANDLING OF DISABLED USERS IN WORKFLOWS
31916340	LDAPCONTAINERRULES.XML NOT HONORING CREATE AND MODIFY OPERATIONS MOVING USER BACK TO DEFAULT OU
31922997	PUMA:UNABLE TO PROVISION/REVOKE ENTITLEMENT FROM FLAT FILE DISCONNECTED APP
31941035	EXCEPTIONS ARE LOGGED DURING EXECUTION OF SCRIPT OIMBULKLOAD FOR AOB
31988511	REQUEST ID AFTER BEING APPROVED IS CREATED AGAIN UNDER PENDING APPROVAL
32012695	12C ACCOUNTS BULK LOAD FROM DB TO AOB APPINST FAILS WITH: JAVA.LANG.REFLECT.INVOCATIONTARGETEXCEPTION
32485920	CERTIFICATION TASK ASSIGNED ONLY TO PROXY OF MANAGER OF MANAGER DISABLED BUT NOT TO MANAGER OF MANAGER DISABLED
32523570	ACTION COMMENTS DUPLICATED FOR REJECT,ESCALATE OPERATIONS DURING APPROVALS THROUGH REST API

1.17.5 Resolved Issues in OIM Bundle Patch 12.2.1.3.210107

Applying this bundle patch resolves the issues described in Table 1-6.

Table 1-6 Resolved Issues in OIM Bundle Patch 12.2.1.3.210107

Bug Number	Description
24512950	OIM 11.1.2.2.6 - UPGRADE TASK FOR 2ND DISCONNECTED APPLICATIONS NOT TRIGGERED
25790911	JAVA SCHEDULERSERVICE:GETLASTHISTORYOFJOB API CAUSING OUT OF SEQUENCE ISSUES WITH RAC DB
26380382	HETEROGENEOUS REQUEST DETAILS PAGE PERFORMANCE ISSUE FOR 100+ CHILD REQUESTS
27177000	STRESS:OIM RECON JOB IS NOT PROCESSING REQUESTS/EVENTS WHEN RESTART OIM SERVERS
27511207	ACCOUNT END-DATE IS NOT CLEARED POST ENABLING THE ACCOUNT
27599841	WE ARE LOOKING TO MODIFY ROLE REVOCATIONS TO DE-PROVISION ALL ACCESS
27692108	OIM 11G TO 12 G UPGRADE UNIQUE CONSTRAINT (DEV_OIM.UK_ENTITY_TYPE) VIOLATED
28025965	LIBRARIES (.JAR)FOR MANAGED BEANS AND TASK FLOWS ARE MISSING IN 12C
28209451	NLS: NON-ENGLISH USER CAN NOT VIEW CONTENT/PERFORM ACTION OF USER CERTIFICATION
28338775	ADFCONTEXT LEAK COMING FROM ORACLE.RULES
28361656	EMPEMPLOYMENT.STARTDATE INVALIDDATAFORMATEXCEPTION
28374155	12C SCIM API RETURNS ITEMSPERPAGE INSTEAD OF TOTALRESULTS
28415601	CONDITION MODIFIEDUSER.CURRENTVALUE.IDENTITYSTATUS IS IDENTITYSTATUS.ACTIVE ISSU
28944383	PROV TASK REST API TO UPDATE NOTE AND RESPONSE
29133050	PROVISIONING FAILING WITH NULL ERROR IF ITRESOURCE HAS ENCRYPTED FIELD
29502576	NULLPOINTEREX WHEN CERTIFICATION TASK EXPIRES FOR A ROLE CERTIFIER RECIPIENT
29744520	CUSTOM PASSWORD VALIDATION EVENT HANDLER MESSAGE DOES NOT WORK ON THE MY INFO
29945486	CONTINUATION OF BUG 29635993 - EXCESSIVE TIME ON CALLS TO /IDENTITY CONTEXT
30446841	IDENTITY AUDIT RULES CONTAINING SPECIAL CHARACTERS DO NOT RAISE POLICY VIOLATION
30484714	REFRESHROW ISSUE WITH OJDBC8
30587375	DEADLOCK CAUSING STUCK THREADS
30517242	OIMADMINPASSWD_WLS.SH FAILS ON IBM AIX WITH IBM JAVA JRE
30808736	RECONCILIATION OF A USER STATUS FROM ACTIVE DIRECTORY DOES NOT SET OBUSERACCOUNTCONTROL IN LDAP
30835811	APPROVAL CHILD TASKS STATUS DOES NOT SHOW WITH BROWSER IN ITALIAN LANGUAGE
30883086	UNSUPPORTEDOPERATIONEXCEPTION ON MODIFYING USER WHEN USING UDF NUMBER IN ROLE MEMBERSHIP RULE
30910129	DUPLICATE ACCESS POLICY NAME ERROR NOT CLEAR
30932205	OIM REQUEST FAILED WITH MESSAGE IAM-2050126 : INVALID OUTCOME COM.ORACLE.BPEL.CLIENT.BPELFAULT
30978612	AP HARVESTING SYNC ATTRIBUTES/ENTITLEMENTS TO MATCH WITH THE ACCESS POLICY
30992823	Fix for Bug 30992823
31161987	PASSWORD RESET IN MYINFORMATION SUBMIT BUTTON
31193971	ENTITLEMENT CERTIFICATIONS ARE NOT GETTING GENERATED FOR SOME OF THE CERTIFIERS.
31316925	ENT CERT SHOULD BE CREATED FOR CERTIFIER FOR REMAING ENT WHICH ARE CORRECT
31373822	NEED SPECIAL HANDLING OF INT ON FORM WHEN NO VALUE PASSED
31420786	ACCESS POLICY DOES NOT REMOVE ENTITLEMENT WHEN 2 CHILDFORMS ARE UPDATED TOGETHER
31622015	WRONG NUMBER OF ROWS DISPLAYED ON THE CERTIFICATION TABLE
31641120	CONFIG UPGRADE FAILING IF SCHEMA SUFFIX OTHER THAN _OIM USED
31645106	HARVESTED ENTS INCLUDED WHEN ENTITLEMENTS PROVISIONED BY AP UNCHECKED
31668539	EVALUATE USER ACCESS POLICY JOB STUCK AND CAUSING OIM SERVER TO GO INTO WARNING
31678727	OAM OIM 12CPS3 USER IS SHOWING STATUS AS UNLOCKED IN OIM CONSOLE EVEN IT IS LOCKED
31956134	ATTEMPT TO PACK THE DOMAIN AFTER 12.2.1.3 UPGRADE FAILS DUE TO COMPONENT VERSION MISMATCHES
31723765	DISABLEPOWEREDBYHEADER, SOAPRESTART BOOTSTARP FAILED WITH LOCALSVCTBLDATASOURCE DS ERROR
32102761	PRE UPGARDE REPORT FAILS IF STAGING-MODE IS EMPTY
31979466	PUMA: ACCOUNT CHOOSER POPUP DURING CHECKOUT KEEPS EXPANDING TILL REACH THE WINDOW LENGTH
32103803	UPGRADE WITH REMOVED ITR PASSWORDS LEAD TO POST CREATE EVENT HANDLER KEEPS TRIGGERING
32103891	IPF.JAR INCORRECT IN DOMAIN_HOME/CONFIG/CONFIG.XML
32085862	FAILED TO REGISTER LIBRARY EXTENSION-NAME: ORACLE.IDM.IDS.CONFIG.UI: MUST PROVIDE SPECIFICATION-VERSION FOR LIBRARY
32254565	WHEN USER HAS NO ACCOUNT, CALL MADE TO INVOKE TRIGGERPOSTPROCESSHANDLER FAILS
32282814	JPS EXCEPTION IS LOGGED DURING THE EXEUTIONG OF PREUPGRADE REPORT UPG PATH 11GR2PS3 TO 12CPS3
32328405	NO EXCEPTION THROWN FOR USER CERTIFICATION WITHOUT ACCOUNT LOGIN NAME

1.17.6 Resolved Issues in OIM Bundle Patch 12.2.1.3.201006

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

Table 1-7 Resolved Issues in OIM Bundle Patch 12.2.1.3.201006

Bug Number	Description
26308544	DELETED ENTITLEMENTS IN ACCESS POLICY ARE NOT REMOVED IN TARGET APPLICATION
26355008	GETTING ERROR MESSAGE ON SEARCH ENTITLEMENT ON REQUEST PAGE
26452240	AP HARVEST NOT WORKING FOR RECONCILED ENTITLEMENTS FOR ACCOUNT PROV BY AP
26498488	ENTS BY AP HARVESTED INCLUDED WHENENTITLEMENTSPROVISIONEDBYACCESSPOLICY UNCHECK
26498535	ONLY HIGH-RISK ENTITLEMENTS OUTSIDE ROLES SELECTED BUT CERT SHOW MID RISK ENTS
26572790	PREVENTIVE SOD NOT TRIGGERED WHEN A ROLE WITH AP AND STANDALONE ENT IN SAME CART
26950406	TRACK REQUESTS BENEFICIARY AND REQUESTER WRONG LAYOUT
27157083	UNLOCK ACCOUNT THROWS POP-UP ERROR WITH PREVIOUS USER SELECTION
27267069	UNABLE TO FILTER ROLE MEMBERS IF THERE ARE MORE THAN 28 IN ROLE.
27531372	REQUEST JUSTIFICATION IS GETTING DELETEDIN IE11 UPDATING REQUEST FORM
28433121	VARIABLES ARE NOT BEING RESOLVED IN OIM OOTB NOTIFICATIONS
29404814	CERTIFYING 20K USERS WITH 20K ACCOUNTS AND 100K ENTITLEMENTS FAILS IN SELF-SERVICE
29476323	OIM 12C SSOTARGET APPLICATION ORGANIZATION MODIFY NOT TAKING PATH IN LDAPCONTAINERRULES
29603087	SELF REGISTRATION DOES NOT TRIGGER ROLE MEMEBERSHIP
29657726	Fix for Bug 29657726
30062969	TRUSTED RECON OF MANAGER DOES NOT PROPAGATE TO SSOTARGET
30145982	12C ACCOUNTS BULK LOAD TO AOB APPINST FAILS: "ONE OR MORE INPUT REQUIRED PARAM.. Note: See Bulk Load Utility for Loading Accounts for information about the input required for loading account data by using the Bulk Load Utility.
30202020	[ROLECERT]: NO CERTIFICATION TASK CREATED FOR PROXY USER'S MANAGER
30239831	CONT: ADAPTER FACTORY GENERATING INVALID JAVA CODE.
30278057	ORGANIZATION NAME IS CHANGED CAPS WHILE SEARCHING IT IN ORGANIZATION TILE
30414695	ISSUE WITH OFFLINE CERTIFICATION COMMENTS FIELD LENGTH WHEN UPDATING FROM EXCEL
30500178	XL.CATALOGSEARCHRESULTCAP NOT ONLY AFFECT THE UI BUT ALSO INTERNAL PROCESSING
30546975	WHILE WITHDRAWING A REQUEST, THE CONFIRMATION BOX IS APPEARING WITH A BIG DIALOG
30716490	UNABLE TO PROCESS BATCH UPDATE IF ANY SSOTARGET IN PROVISIONING STATUS FOR USER
30717640	RULEENGINEEXCEPTION: INVALID RULE EXPRESSION - NOT_IN
30738489	REQUESTS/PENDING REQUESTS GET ERROR IF SECOND MANAGER IS DISABLED
30838859	[ROLECERT]: FUTURE STARTING PROXY USER RECEIVES CERTIFICATION
30843613	APP INSTANCE DOES NOT APPEAR IN CART IF IS_REQUESTABLE IS 0 FOR AN ENDUSER
30865103	DELETE TASK NOT TRIGGERED ON ATTRIBUTE SET AS NOT ENTITLEMENT IN CHILD FORM
30925400	CRYPTIC ERROR MESSAGE WHEN REQUEST FAILS
30942250	CREATE ADMIN ROLE THROWS: JBO-29000: UNEXPECTED EXCEPTION CAUGHT: JAVA.LANG.NULLPOINTEREXCEPTION
30977436	USER ASSIGNED TO A ROLE WITH THE "+" CHAR IN THE NAME CAN'T ACCESS WORKLISTAPP
31057153	OIM 12C SSOTARGET APPLICATION PROFILE MODIFY NOT TAKING PATH IN LDAPCONTAINERRULES
31111401	ADMIN ROLE: JUMPING FROM SUMMARY PAGE BACK TO FIRST PAGE RESULTS IN LOST DATA
31114189	INTEGER FIELDS WITH NO VALUE DEFAULTING TO 0 FOR APPS CREATED USING AOB
31162758	OIM 12C SSO USER TARGET RECON OVERWRITING ROLE VALUE SAVED ON OIM USER WITH DEFAULT VALUE Note: See Steps to Map the Role and employeeType Attributes for information about the manual steps required for the bug fix to work.
31177214	UNABLE TO ADD EMPLOYEE TYPE AS DISPLAY DATA IN THE INFORMATION WINDOW
31180365	UPGRADE FROM 11.1.2.3 TO 12.2.1.3: STRINGINDEXOUTOFBOUNDSEXCEPTION: STRING INDEX OUT OF RANGE: -19
31254720	DIAG: POOR LOGGING IN OIMDATAPROVIDER
31292576	PASSWORD CHANGE FLOW ISSUES AFTER FIX 30809484
31351771	INCONSISTENT VALUES IN THE REQUEST STATUS FILTER FROM TRACK REQUESTS PAGE
31375771	SSO TARGET APPLICATION FAILS TO GET PROVISIONED WITH MANAGER ATTRIBUTE.
31434988	ENT_ASSIGN_HIST DOESN'T SAY IF THE ENTITLEMENT WAS PROVISIONED OR INPROGRESS
31441427	UPG DOESN'T UPDATE OIM-CONFIG.XML OR WORKFLOWS WITH VERSION6 DEFAULT COMPOSITES
31449106	ACCESS POLICY ADDING UNTOCHED BOOLEAN FIELDS AS 0 IN POF TABLE ON SAVING APPLICATION
31464420	DISABLE USER TASK IS GETTING TRIGGERED FOR PROVISIONING ACCOUNTS

1.17.7 Resolved Issues in OIM Bundle Patch 12.2.1.3.200627

Applying this bundle patch resolves the issues described in Table 1-8.

Table 1-8 Resolved Issues in OIM Bundle Patch 12.2.1.3.200627

Bug Number	Description
21054580	NO OPTION TO CLOSE TABS OPENED VIA DIRECT URLS
25418103	END USER NOT ABLE TO SUBMIT ANOTHER REQUEST FOR A FAILED ADD ENTITLEMENT REQUEST
28644113	TRIED TO CREATE UDF ROLE AND PUSH TO OUD BUT FAILED
29044697	OIM 12C UPGRADE BOOTSTRAP FAILURE WITH DISABLE POWERED BY HEADER FOR OIM FAILED
29427738	MANAGER DOES NOT HAVE PROXY ON THE DAY PROXY IS REMOVED
29758939	CHANGING GRANT DATES IN APPROVAL WITHOUT CLICKING UPDATE ALLOWED TO PROCEED
29772810	OIM12C: REQUEST STATUS SHOULD BE DISPLAYED AS EXPIRED NOT FAILED WHEN TASK IS EXPIRED
30005722	OIG12C: PERFORMANCE ISSUE WITH LARGE LOOKUPS IN ACCESS POLICIES WITH CHILDS
30007378	REASSIGN THE REVIEWER ON CERTIFICATION FAILED ON PREVENTING SELF CERTIFICATION
30097140	SLOWNESS OPENING USER DETAILS ADMIN ROLES TAB
30153927	APPROVAL DETAILS INCORRECT AFTER REVOKING ROLE BY XELSYSADMIN AND ANOTHER USER
30216857	SETCHALLENGERESPONSESFORLOGGEDINUSER - CHALLENGE QUESTIONS PROVIDED ARE NOT DEFI
30343249	WHILE DELETING ORGANIZATION USERS REMAIN IN ACTIVE STATE
30343784	ACCESS POLICY NOT REVOKING ENTITLEMENTS ON ALREADY DISABLED USERS
30376706	ROLEMANAGER GRANTROLE SQLEXCEPTION: EXCEEDED MAXIMUM VARRAY LIMIT
30391615	ROLE WITH RULE FOR DATE FIELD IS NOT ASSIGNED TO USER
30420218	OIM/OAM INTEGRATION USER SESSION LOST AFTER ANY USER DATA EDITED
30439939	AP HARVESTING DOES NOT WORK FOR RESROUCES WITH MULTIPLE PROVISIONING WORKFLOWS
30506899	DELETE RECONCILIATION LEAVES PROVISIONING OPEN TASKS IN LIMBO STATE.
30517366	DELEGATE THE REVIEWER ON CERTIFICATION FAILED ON PREVENTING SELF CERTIFICATION
30632245	REST API : REVOKE ENTITLEMENT FOR INVALID USER ERROR MESSAGE CORRECTION
30717793	CLONED DISCONNECTED PROVISIONING COMPOSITE FAILS AT ASSIGNREQUESTINPUT STAGE
30757297	DISCONNECTED APPLICATION NOT TRIGGERING UPDATE TASK ON CHILD FORM
30788834	DIAG: NEED SOME TRACE LOGGING IN THE SCIM FUNTIONALITY
30866653	ACCESS DENIED ERROR WHEN CALLING CREATEITRESOURCEINSTANCE FROM SCHEDULED TASK
30896936	PUMA: CUSTOM MESSAGE NOT DISPLAYED WHEN COMPLETING MANUAL TASK
30959255	OIM 12C UPGRADE: ERRORS WHEN OIM APPLICATIONS FAIL TO DEPLOY (DOC ID 2389943.1)
31184149	PERFORMANCE ISSUE IN OIMDATAPROVIDER.GETARRAYFORHIERAR
31243937	POOR RESPONSE TIME ON HOMEPAGE CAUSED BY THE SOACALLS FOR THE COUNTERS DISPLAYED

1.17.8 Resolved Issues in OIM Bundle Patch 12.2.1.3.0 (ID:200108.2108)

Applying this bundle patch resolves the issues described in .

Table 1-9 Resolved Issues in OIM Bundle Patch 12.2.1.3.0 (ID:200108.2108)

Bug Number	Description
26859255	OIM SELF SERVICE - OOTB FIELD PRECISION EXCEPTION
27580895	CONNECTION LEAK IN OIMPOSTCONFIGMANAGER.CONFIG.OIMCONFIGURATION.LOADCONFIGURATIO
28048402	UPGRADE ASSISTANT FAILS AT EXAMINE STEP - UPGRADE OF DOMAIN COMPONENT
28126864	NOTIFICATION EMAIL SUBJECT LINE NOT DISPLAYING PROPERLY IF $USERLOGINID IS USED
28375545	DIAG: CATCH ALL DETAILED EXCEPTIONS IF POSSIBLE TO SHOW THE CAUSES
28563380	DOBPROVISIONINGUTIL.POPULATEENTITLEMENTINSTANCES DEADLOCK IN OIM 11.1.2.3.180331
28777983	Fix for Bug 28777983
28919213	DIAG: HANDLE THE EXCEPTION PROPERLY IN INITPOSTCONFIGTASKS
28930943	CHANGING BROWSER LANGUAGE MODIFIES PROVISIONED DATE FORMAT TO DD/MM/YYYY
29042515	AFTER APPLYING OCT 2018 BP, THEN IAM-40600010 ERRORS IS FOUND FOR PROVISIONING.
29227955	ERROR MESSAGE CONTAINS NULL INSTEAD OF CERTIFIER NAME WHEN USING PROXY
29272568	SORT ORDER IN USER CERTIFICATION NOT ALPHABETIC FOR ENTITLEMENTS WITH CERTIFIABLE CAT UDF
29311886	ROLE CERTIFICATION: IDENTITY STATUS NOT POPULATED
29339597	PREVENT SELF CERTIFICATION [ROLE] IS NOT WORKING AS EXPECTED WHEN THERE IS A PROXY USER
29361127	EDIT MODE ROLE MEMBERSHIP RULE CONDITION IS DISPLAYED AS UNKNOWN
29430550	MANAGER SELECTING FOR REPORTEES IN TRACK REQUESTS CAUSES OIM TO BECOME UNSTABLE
29455507	OIM 12C REST SUPPORT FOR CORS
29472570	CUSTOMIZATION LOST PATCHING FROM 11.1.2.3.160419 TO 11.1.2.3.190103
29554380	OAM/OIM/OUD 12C INTEGRATION OBLOCKEDON WRONG FORMAT
29555940	SSO INTEGRATED ENVIRONMENT - ORCLACTIVESTARTDATE, ORCLACTIVEENDDATE
29641875	OAM/OIM 12C INTEGRATION: SSO RECON WRONG DATE FORMAT
29656504	CONNECTOR AOB ON WIONDOWS IS FAILING WITH "COULD NOT CREATE THE TMP DIRECTORY"
29742938	REST API: REVOKE ENTITLEMENTS FROM USER
29900727	AD FORM `USER MUST CHANGE PASSWORD AT NEXT LOGON¿ CHECK BOX IS ALWAYS CHECKED
29908447	Fix for Bug 29908447
29942217	IMPLEMENT BLIND/FILTERED SEARCH "FOR A REPORTEE" FOR A MANAGER
29966832	ERROR SEEN IN SELF CERTIFICATION [ROLE] CASE EVEN THOUGH ROLE CERTIFICATION IS CREATED
29967546	REQUEST STATUS STUCK IN "REQUEST APPROVED FULFILLMENT PENDING"
29972923	STEPS TO ROLLBACK AUTOCOMMITED DDL OPERATIONS IN DB
30007320	NPE IN ROLECERTIFICATIONHELPERIMPL.CREATEROLECERTIFICATION
30105406	ENH DOMAIN UPGRADE STAGE DELETES SOA CLUSTER
30119475	ENH OIM 12C UPGRADE - NOT GETTING FULL VIEW OF IMPORT/EXPORT PAGE
30325576	PARTIAL FIX FOR BUG 28777983
30679886	DEPLOYMENT CHECKER RESULTS ARE UNEXPECTED WITH 12CPS3 PATCH
30680152	ORGANIZATION SEARCH IN TRACK REQUESTS PAGE: ALL REQUESTS NOT DISPLAYED FOR ORGANIZATION NAME SEARCH IF NUMBER OF REQUESTS GREATER THAN 25
30680286	ORGANIZATION SEARCH IN TRACK REQUESTS PAGE: DOES NOT EQUAL OPERATOR NOT WORKING AS EXPECTED
30717520	ORGANIZATION SEARCH IN TRACK REQUESTS PAGE: BENEFICIARY NAME NOT LISTED

1.17.9 Resolved Issues in Release 12.2.1.3.190624

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

Table 1-10 Resolved Issues in Release 12.2.1.3.190624

Bug Number	Description
25695572	ENTITLEMENT NAME IS MISSING IN REQUEST SUMMARY REPORT FOR REVOKE ENTITLEMENT TYPES Note: See Copying the Oracle Identity Governance Reports ZIP Directory for information about copying the Oracle Identity Governance reports ZIP file for the bug fix to work.
26135785	NOTIFICATION TEMPLATE SHOULD SUPPORT EMAIL TEXTS OF SIZE > 4000
27601939	DIAG: LOGGING FOR OIM SERVER DOES NOT START UP BECAUSE OF INVALID CREDENTIALS
27738259	AFTER APPLYING PATCH 22005210 DATA IN HISTORY TAB SHOWS ESCAPING CHARS
27810515	LINKS IN OIM APPROVAL EMAILS NOT WORKING
28144322	DIAG: UPLOADJAR SHOULD THROW CORRECT ERROR INSTEAD OF NPE
28144399	DIAG: DOWNLOADJARS SHOULD THROW CORRECT ERROR INSTEAD OF NPE
28201867	DELETING APPINSTANCE DELETES ROLES THAT SHARE ENTITY_KEY WITH ENT DELETED
28222151	DIAG: NEED DIAGNOSTIC IN ICFCOMMON CONFIGURATION SETUP
28527669	DC FAILED TO CREATE RECON PROFILE:ATTRIB NOT PRESENT IN ENTITYDEFINITION OF USER
28553584	DIAG: IMPROVE THE MESSAGE TO PROVIDE MORE USEFUL DATA
28577886	INCREASE FIELD LENGTH OF SCHEMA ATTRIBUTE FOR AN APPLICATION
28642312	LOADFROMURL TAG IS NOT WORKING FOR TEST CONNECTION IN AOB TEMPLATE
28650960	CERTIFYING 20K USERS WITH 20K ACCOUNTS AND 100K ENTITLEMENTS FAILS
28674046	REVOKE MANUAL FULFILLMENT TASKS ARE TRIGGERING MULTIPLE TIMES
28674152	DEPLOYMENT MANAGER ISSUE IMPORTING HUGE DATA
28715293	MINIMUM CHALLENGE QUESTIONS ERROR IS NOT LOCALIZED
28737144	OIM 12C -IT RESOURCE VALUES ENCRYPTED AFTER EXPORTING AOB APP INSTANCE FROM DM
28770544	CUSTOM UI CALL TO CREATE-USER-TF DOES NOT RETURN TO CALLING PAGE CORRECTLY
28777965	Fix for Bug 28777965
28872568	ORGANIZATIONS CREATED IN OIM DO NOT SHOW AS AN ATTRIBUTE IN OUD
28879742	REVOKE FUTURE_GRANT ENTITLEMENTS FAILS IN OIG 12C WITH OID 12C AOB CONNECTOR
28939483	IMPROPER ERROR MESSAGES IN LDAP CREATE/DELETE/MODIFY ORCHESTRATION HANDLERS
28992260	EXCEPTION RAISED DURING ROLE PROVISIONING WHEN ENTITLEMENTS HAVE SIMILAR NAMES
29012343	REST API RETURNS WRONG ENTITYID FOR ENTITLEMENT IN REVOKE ENTITLEMENT REQUEST
29029439	USER SEARCH FAILS WITH ERROR "EXCEEDED MAXIMUM VARRAY LIMIT"
29217761	MEMORY LEAK WHEN CALLING PROVISIONINGSERVICE.GETACCOUNTSPROVISIONEDTOUSER() API
29260747	ROLE HISTORY TAB SHOWS ESCAPING CHARS
29351177	ENTITLEMENT CERTIFICATION WITH CRITERIA: INDEXOUTOFBOUNDSEXCEPTION: INDEX: 0, SIZE: 0
29390412	RE-CREATE ROLE FAILURE IN OIM/OAM INTEGRATED ENVIRONMENT
29409849	FUTURE DATED USER CAN NOT BE PROVISIONED FUTURE DATED ROLE
29753875	FUTURE ROLE GRANT START DATE CANNOT BE MODIFIED TO CURRENT FOR DISABLED UNTIL START DATE USER

1.17.10 Resolved Issues in Release 12.2.1.3.190109

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

Table 1-11 Resolved Issues in Release 12.2.1.3.190109

Bug Number	Description
26556110	PROCESS TASK EMAIL NOTIFICATION RESPONSE CODE AND RESPONSE DESCRIPTION NOT MATCH
26860614	Fix for Bug 26860614
26935701	USER CERTIFICATION REVOKED ACCOUNTS SHOULD NOT BE SHOWN
27337702	OIM_ORACLE_HOME/SERVER/PLATFORM/ DIRECTORY MISSING FROM 12C BINARY
27479814	TARGET ACCOUNT SELECTION LIMITED TO 300 VALUES
27486132	BACKPORT OF 25948984 TO PS3
27498869	FETCHED SIZE UPDATE BREAKS ADDING MEMBERS TO ROLE
27607542	UDF DISAPPEAR FROM CERTIFICATION USER CRITERIA
27624103	SPMLWS DISCLOSES PASSWORD OF USER RESET IN AD INCASE OF SUCESS/FAILURE
27675628	CREATING USERS WITH SCIM IN POPULATED ORGANIZATIONS TAKE A LONG TIME
27733085	MEMBERSHIP RULE UI SUPPORT FOR LOGICAL OPERATORS SUPPORTED BY JAVA API
27763398	STRESS:OIM SQLEXCEPTION SEEN WHILE APPROVING MODIFY ROLE REQUEST
27806960	PERFORMANCE ISSUE ON ORGANIZATION TAB
27828814	"APPLY" BUTTON GETTING ENABLED THOUGH NO CHANGES DONE TO ROLE ATTRIBUTES
27931832	THE LOGGED-IN USER 1 DOES NOT HAVE ADDROLEMEMBERSHIPS PERMISSION ON ROLE
27986715	MULTIPLE CHANGE TASKS ARE GETTING TRIGGERED INSTEAD OF ONE CHANGE TASK
28056465	WITHDRAWING A PARENT REQUEST OF THE HETEROGENOUS REQUEST
28142729	ORA-00917: MISSING COMMA AFTER APPLYING PATCH 26165573 MONTHS AGO
28238704	SECURITY ANSWERS ARE ALLOWED DUPLICATE WHEN "ALLOW DUPLICATE RESPONSE" UNCHECKED
28297906	ROLE NOT ADDED BY MEMBERSHIP RULE AFTER BEING REMOVED.
28316082	MYINFO_SAME_VALUE_MODIFY NOT CUSTOMIZABLE
28354933	STEPS TO ROLLBACK BUG 27098131 - ENTITLEMENTS OUTSIDE ROLES OPTION NOT SHOWING
28366280	WHEN A USER IS CREATED, OIM DOES NOT ASSIGN ROLE TO USER WITH RULE MEMBERSHIP
28369024	BOOTSTRAP FAILURE, ORA-00942
28542619	CONNECTION LEAK IN DOBPROVISIONINGUTIL.POPULATEENTITLEMENTINSTANCES IN 12CPS3
28891498	PROBLEM REVOKING ACCOUNT WITH REJECTED TASKS
28961310	ADVANCED ROLE SEARCH GIVING INCORRECT RESULTS WITH LATEST PATCH
29006080	CHANGE IN ROLE ASSIGNMENT BEHAVIOR FROM BUG 28366280
29044105	ALL USERS UNDER CHILD ORGANIZATION NOT RETRIEVED WITH SCIM

1.17.11 Resolved Issues in Release 12.2.1.3.180920

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

Table 1-12 Resolved Issues in Release 12.2.1.3.180920

Bug Number	Description
26418875	GETTING INCORRECT OUTPUT FOR PROCESS RESPONSE DESC VALUE IN EMAIL NOTIFICATION
26663859	USER CERTIFICATION FAILS WITH NPE WITHOUT CREATING ANY TASKS
26670135	ACCOUNTS IN WAITING STATUS CAUSE IDA SCAN "ORA-00903: INVALID TABLE NAME" ERROR
26785853	REQUESTS ARE GOING IN TO POST OPERATION PROCESSING INITIATED STATUS
26865173	TARGET TRUSTED RECON FAILED WITH OOTB TIME ZONE ATTRIBUTE
26935680	CREATE USERS CERTIFICATION TASKS FOR THOSE USERS WITH DISABLED MANAGER
26957145	Fix for Bug 26957145
27024554	IDENTITY AUDIT SCAN PICKING DISABLED POLICIES
27241253	OIM USERS PAGE DOES NOT REFRESH PROPERLY WHEN USING COLUMN SORT AND ADVANCING
27302510	OST_KEY IS WRONGLY MAPPED AFTER AD TARGET RECON UPDATE
27311536	Fix for Bug 27311536
27581965	MERGING 27282628 TO MAIN - STARTSOA3_R1 BLOCK SPRING JARS ISSUE
27617132	ACCOUNT CERTIFICATION DEFAULT SORTING IS NOT ALPHABETICAL
27624252	JBO-25020 ERROR WHEN TRYING TO SEARCH FOR AN ENTITLEMENT IN THE CATALOG
27626291	ERROR CLASSNOTFOUNDEXCEPTION DURING EXECUTION OF CUSTOM PLUGINS
27629691	UNNECESSARY UPDATE PROVISIONING TASKS ARE BEING TRIGGERED FOR DISCONNECTED APP
27656612	CONNECTION LEAK IN ORACLE.IAM.PROVISIONING.SCHEDULETASKS.USERPROCESSTHREAD .<INIT
27712069	MULTIPLE REDUNDANT CALLS TO OIM EJBS DURING LOAD OF MY INFORMATION PAGE
27771411	AOB: NO VALIDATION CHECK FOR UDF EXISTENCE AGAINST THE ATTRIBUTE USIND IN ICR
27777600	MANUAL FULLFILMENT IS NOT GETTING TRIGGERED FOR ENTITLEMENT VIA ACCESS POLICY
27779926	PROVISIONING DOES NOT WORK AFTER ACCOUNT WAS REVOKED TWICE
27817160	COM.THORTECH.XL.DATAACCESS.TCDATASETEXCEPTION COLUMN 'UD_XXX' NOT FOUND
27833180	USER CERTIFICATION LAST DECISION REVOKED
27860018	BULK LOAD ROLEMEMBERSHIP SHOWING ZERO RECORDS PROCESSED EVEN THOUGH SUCCESSFULLY
27920700	Fix for Bug 27920700
27927397	PROVISIONING ENGINE FAILS TO PROCESS USER ATTRIBUTE CHANGE
28031831	AOB:APP CREATION FAILING ON MAPPING SAME ID ATT TO MULTIPLE ACCOUNT ATT
28155722	VALUES ARE NOT REFRESHED CORRECTLY IN "DETAILED INFORMATION" TAB
28186972	COLUMN USR_AUTOMATICALLY_DELETE_ON IS NOT CLEARED AFTER ENABLING THE USER
28239186	AOB:UPGRADE- INCORRECT MASTER TEMPLATE STORED IN CASE OF MULTIPLE TEMPLATES
28377433	AOB: AUDIT DATA NOT GETTING GENERATED FOR ANY OPERATION PERFORMED AGAINST APP
28433832	PROCESS TASKS ARE NOT TRIGGERED WHEN THERE ARE DUPLICATE ENTRIES IN LOOKUP

1.17.12 Resolved Issues in Release 12.2.1.3.180713

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

Table 1-13 Resolved Issues in Release 12.2.1.3.180713

Bug Number	Description
27000479	JAVA.LANG.NOCLASSDEFFOUNDERROR: COM/ORACLE/OIM/GCP/RESOURCECONNECTION/RESOURCECO
27067961	ENTITLEMENTS OUTSIDE ROLES OPTION NOT WORKING WITH DISPLAYNAME TRAILING SPACES
27078300	ENTITLEMENTS OUTSIDE ROLES CERT OPTION NOT TAKING INTO ACCOUNT INDIRECT ROLES
27098131	ENTITLEMENTS OUTSIDE ROLES OPTION NOT SHOWING APPLICATION INSTANCE
27100241	UNABLE TO DISPLAY DATA IN THE INFORMATION WINDOW
27177740	CLEAR TEXT PASSWORD CAUSING SRGSECCHECK/PSWDCHECK DIF (40+)
27181614	SCIM - CREATE USER FAILS IF ACTIVE ATTRIBUTE IS INCLUDED IN THE REQUEST
27196097	ROLE HIERARCHY TAB NOT SHOWING ALL PARENT ROLES
27273838	ROLE CAN'T BE ASSIGNED TO A DISABLED USER, IF UNCHECK GRANT DURATION CHECKBOX
27350190	ADD CONNECTOR VERSION PARAMETER TO AUTOMATION SCRIPT
27366933	REGRESSION FOR BUG 27040809
27423854	INCORRECT DEFAULT LOCATION OF CONNECTOR BUNDLE IN SSOINTG-CONFIG.PROPERTIES
27423992	SSOINTG-CONFIG.PROPERTIES SHOULD BE IGNORED WHEN RUNNING A SINGLE COMMAND
27438385	BI REPORT ORPHANED ACCOUNT SUMMARY NOT WORKING
27439501	PREUPGRADE ADMIN USERS UNABLE TO EDIT IT RESOURCES AFTER UPGRADE
27466871	ATTRIBUTE MODIFICATION INCONSISTENT FOR MYPROFILE AND USERS SECTION
27558461	OIM UNEXPECTED REVOKE ROLES
27564325	REGRESSION FOR PSE 27542629 FOR BASE BUG 27139050 ON TOP OF 11.1.2.3.170718OIMBP
27567365	CONFIGURELDAPCONNECTOR.SH FAILS - INVALID VERSION
27567443	ERROR IAM-3040026 OCCURES WHENEVER THE CHOOSEN QUESTIONS IS INTERNATIONALIZED
27617274	PARAMETER OIM_SERVER_NAME MISSING IN CONFIG FILE
27626487	NO ATTRIBUTE ORACLECONTEXT IN AD SHOULD NOT BE AN ERROR
27638151	ADDMISSINGOBJECTCLASSES HAS NO CONFIG FILE AND ASSUMES CONNECTION PARAMETERS
27638236	CONFIGURESSOINTEGRATION FAILS - COMMAND NOT FOUND
27697060	NO ATTRIBUTE SYSTEMIDPOLICY IN AD SHOULD NOT BE AN ERROR
27712164	OIM-OAM: IDM STAGE 8 SHIPHOME CAN NOT RUN OIGOAMINTEGRATION.SH
27719473	CONFIGURESSOINTEGRATION DOES NOT RETURN WRONG STATUS WHEN IDENTITY SERVER DOWN
27762094	WEBLOGIC_IDM DID NOT ADD IN IDM ADMINISTRATORS GROUP WHEN PREPAREIDSTORE FOR AD
27772143	ICONS MISSING FROM UI CONSOLE
27799154	OIM_SERVER_NAME VALUE IS NOT EFFECTIVE
27806091	OIM-OAM-AD: CONFIGURELDAPCONNECTOR FAILED WITH FILENOTFOUNDEXCEPTION
27939257	USRPROCESSTRIGGER IS GETTING NULL POINTER EXCEPTION

1.17.13 Resolved Issues in Release 12.2.1.3.180413

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

Table 1-14 Resolved Issues in Release 12.2.1.3.180413

Bug Number	Description
25323654	AOB: TEST CONNECTION IS SUCCESS EVEN IF INVALID VALUES IN BASIC CONFIG
25996056	NOTSERIALIZABLEEXCEPTION EXCEPTIONS BEING LOGGED WHEN ACCESSING WORKFLOW
26165573	EXTENSION TO THE FOLLOWING BUG 25727240 (REFRESH MATERIALIZED VIEW) Note: For manual steps on how to apply changes done for Bug Fix 26165573, see My Oracle Support document ID 2383245.1.
26186971	Fix for Bug 26186971
26188366	Fix for Bug 26188366
26288324	THE ENTITLEMENT GETPROVISIONED EVEN IF GRANT END DATE IS PASSED AT APPROVE TIME
26427097	DELETING APP INSTANCE RESULTS IN JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
26474713	AOB: PROVIDE FEATURE TO ADD NEW CONFIGURATION PROPERTIES IN ADVANCED SETTINGS
26500524	AOB: SAP AC UM AND UME FORM FIELDS ARE UPDATED BLANK AFTER RUN USER RECON
26522972	AOB: REVOKE ACCOUNT IS NOT WORKING IN SAP AC UM & UME
26616250	TARGET USER RECON IS FAILING FOR CI BASED INSTALLATION
26681376	PUBLISH IN TOP AND SUB ORGANIZATIONS BY OIM API IS TAKING LONG TIME
26729272	NOTSERIALIZABLEEXCEPTION RETURNVALUEROW WHILE EDIT WORKFLOW RULES IN OIM CLUSTER
26932665	DEPENDENT REQUEST DETAILS NOT VISIBLE DUE TO SCROLLBAR MISSING
26967104	AOB: DISPLAY NAME OPTION NOT COMING WHILE ADDING NEW ADVANCED CONFIG ATTRIBUTE
26967178	AOB: OPTION NOT COMING TO ADD ADV CONFIG ATTRIBUTE IF NO ATT EXISTS IN TEMPLATE
26982896	MANAGER INFORMATION SHOWING BLANK IN USER CERTIFICATION ON THE UI
27025473	LIGHT WEIGHT AUDIT PUREGE - REMOVE AUDIT LOG ENTRIES JOB IS RUNNING TOO LONG
27026427	KSS NOT UPDATED FROM DEFAULT-KEYSTORE.JKS BREAKS JWT
27113693	UPGRADE ASSISTANT READINESS CHECK FAILED DUE TO OIM 11.1.1.3.0 TEMPLATE
27119830	RECONFIG DOMAIN DOESN'T TAKE OIM 11.1.1.X VERSION APPS INTO CONSIDERATION
27145500	ERROR DUE TO CHANGES IN "SOAOIMLOOKUPDB" DATASOURCE IN 12CPS3
27166581	RESOURCE HISTORY SHOWS INCORRECT ENTITLEMENT NAME AFTER BP 26858666 (OCT-17)
27168000	LIBRARY ORACLE.IDM.IPF WAS TARGETED TO OIM AND SOA CLUSTER INSTEAD OF ADMINSERVE
27200817	SEARCH SELECTIONS DO NOT WORK FOR CREATE/MANAGE USER IF CLICK BACK TO USERS LIST
27279346	AOB: APPLICATION CREATION FAILING WITH USER NOT HAVING SYSTEM ADMIN PERMISSION
27384225	AFTER APPLYING OCTOBER BP POLICY VIOLATIONS IS NOT DETECTING ANY VIOLATIONS
27510030	POLICY VIOLATION NOT THROWN FOR DISABLED ACCOUNT
27564429	AOB: SAP UM USER DELETE RECON IS NOT WORKING IN 12C WITH LATEST BP
27567130	CONFIGURELDAPCONNECTOR.SH FAILS

1.17.14 Resolved Issues in Release 12.2.1.3.180109

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

Table 1-15 Resolved Issues in Release 12.2.1.3.180109

Bug Number	Description
23110063	IMPLEMENTATION OF BULK ATTRIBUTES UPDATE FOR AN ACCOUNT IMPACTS OTHER ACCOUNTS
23337308	CERTIFICATION COLUMN NAME "CREATED BY" AND "UPDATED BY" DISPLAYS USR_KEY
25540355	PS3PARITY:"USER TYPE" VALUE DOESN'T GET SELECTED ON FIRST ATTEMPT
26164709	LOG4J.JAR NOT UPDATED IN SETENV.BAT
26434476	WAITING ON ENTITLEMENT STATUS, PATCH 25292874
26592805	USERS SHOULD NOT BE ABLE TO REVOKE ENT THAT IS PART OF ROLE FROM THEIR MY ACCESS
26615293	SEARCH ON CERTIFICATION DEFINITION CONTENT SELECTION PAGE RETURNS ONLY 28 ROLES
26625354	CERTIF ROLE POLICY TAB CATALOG INFO ENTITLEMENT URL SHOW NO ENTITLEMENT DETIALS
26639196	REPLACE EXISTING SEARCH IN CERT. DEF FLOW RESULTS IN ERROR PAGE AND NPE
26732357	CERTIFCATION RESET STATUS CAUSING NPE
26808282	DATASOURCE CONNECTION LEAK AFTER BUG 20293874
26811926	LIBRARIES FOR MANAGED BEANS AND TASK FLOWS ARE MISSING IN 12C
26863966	SEARCH RETURNS REQUESTS FOR REPORTEES AND NON-REPORTEES FOR R2PS2
26895672	OAM_OIM_OVD_OID_UPG: USER CREATION IS FAILED
27025966	THIS IS THE TRACKER BUG FOR EPIC OIM-11380
27037128	Fix for Bug 27037128
27110896	BE CONSISTENT WITH SPECIFYING PARAMETERS IN OAM/OIM INTEGRATION
27112593	ERROR WHEN GETTING CONNECTOR SERVER DETAILS BY NON SYSTEM ADMINISTRATOR
27119849	NLS : ISSUE WHILE SETTING CHALLENGE QUESTIONS WHEN FIRST LOGIN
27133948	OIM-OAM-OUD: ADMIN FAILED TO UNLOCK A SELF LOCKED ACCOUNT
27139528	Fix for Bug 27139528
27175826	OIM-OAM-AD: CONFIGURELDAPCONNECTOR FAILED CONNECTOR PACKAGE IS NOT AVAILABLE
27203691	OIM-OAM-OUD: SSO GROUP MEMBERSHIP INCREMENTAL RECONCILIATION DO NOT WORK
27298564	REPLACE EXISTING SEARCH IN CERT DEF FLOW RESULTING CERT IS NOT GETTING GENERATED
27300245	OIM-OAM-OID: USER SESSION IS NOT TERMINATED WHEN IT IS DELETED BY ADMIN
27313843	12C BP01: USER SESSION IS NOT TERMINATED WHEN IT IS LOCKED OR DISABLED BY ADMIN

1.18 Known Issues and Workarounds

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

Note:

Some known issues listed in the Release Notes for Oracle Identity Management may have been resolved by this Bundle Patch (OIM Bundle Patch 12.2.1.3.220115). Compare the issues listed in Resolved Issues of this document when reviewing the Release Notes for Oracle Identity Management.

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
Errors Related to the For Reportees Feature
Identity Self Service and Identity System Administration Not Accessible
Issues Related to User Login Creation with Special Characters

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

Issue

Impacted Releases: 12c Release (12.2.1.3.0)

When Oracle Identity Governance Release 11.1.2.3 deployment is integrated with Oracle Access Management, libOVD, and Oracle Unified Directory, and upgraded to Release 12c (12.2.1.3.0), the LDAP User Create and Update Reconciliation scheduled job run fails with the following error when a new user is created and its status is set to locked in the system:

[2017-06-05T23:39:53.833-07:00] [oim_server1] [ERROR] []
[oracle.iam.ldapsync.scheduletasks.user] [tid: OIMQuartzScheduler_Worker-8]
[userId: oiminternal] [ecid: b2fc7981-724e-474c-b009-8a5e2d915d52-000008e9,0]
[APP: oim] [partition-name: DOMAIN] [tenant-name: GLOBAL] An error occurred
while processing the data that is retrieved from LDAP to create a
reconciliation event.[[
oracle.iam.ldapsync.exception.ReconEventCreationException:
Thor.API.Exceptions.tcAPIException: Exception occurred while inserting data
into table RA_LDAPUSER due to java.sql.SQLException: execute, Exception =
null
        at
oracle.iam.ldapsync.scheduletasks.user.LDAPUserChangesReconTask.createUserReco
nciliationEvent(LDAPUserChangesReconTask.java:435)
        at
oracle.iam.ldapsync.scheduletasks.user.LDAPUserChangesReconTask.processResult(
LDAPUserChangesReconTask.java:179)
        at
oracle.iam.ldapsync.scheduletasks.user.LDAPUserChangesReconTask.execute(LDAPUs
erChangesReconTask.java:132)
...
Caused by: Thor.API.Exceptions.tcAPIException: Exception occurred while
inserting data into table RA_LDAPUSER due to java.sql.SQLException: execute,
Exception = null
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.createReconciliation
Event(ReconOperationsServiceImpl.java:431)
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.createReconciliation
Event(ReconOperationsServiceImpl.java:418)
...
Caused by: oracle.iam.reconciliation.exception.ReconciliationException:
Exception occurred while inserting data into table RA_LDAPUSER due to
java.sql.SQLException: execute, Exception = null
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl$1.process(ReconOpera
tionsServiceImpl.java:489)
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl$1.process(ReconOpera
tionsServiceImpl.java:467)
        at
oracle.iam.platform.tx.OIMTransactionCallback.doInTransaction(OIMTransactionCa
llback.java:13)
        at
oracle.iam.platform.tx.OIMTransactionCallback.doInTransaction(OIMTransactionCa
llback.java:6)
        at
org.springframework.transaction.support.TransactionTemplate.execute(Transactio
nTemplate.java:130)
        at
oracle.iam.platform.tx.OIMTransactionManager.executeTransaction(OIMTransaction
Manager.java:47)
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.reconEvent(ReconOper
ationsServiceImpl.java:467)
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.createReconciliation
Event(ReconOperationsServiceImpl.java:406)
        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.createReconciliation
Event(ReconOperationsServiceImpl.java:429)
        ... 44 more
Caused by: oracle.iam.platform.utils.SuperRuntimeException:
java.sql.SQLException: execute, Exception = null
        at
oracle.iam.reconciliation.dao.event.EventMgmtDao.create(EventMgmtDao.java:244)

        at
oracle.iam.reconciliation.impl.ReconOperationsServiceImpl$1.process(ReconOpera
tionsServiceImpl.java:478)
        ... 52 more
Caused by: java.sql.SQLException: execute, Exception = null
        at
weblogic.jdbc.wrapper.JDBCWrapperImpl.invocationExceptionHandler(JDBCWrapperIm
pl.java:143)
        at
weblogic.jdbc.wrapper.Statement.invocationExceptionHandler(Statement.java:142)

        at
weblogic.jdbc.wrapper.PreparedStatement.invocationExceptionHandler(PreparedSta
tement.java:100)
        at
weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:125)
        at
oracle.iam.reconciliation.dao.event.EventMgmtDao.create(EventMgmtDao.java:234)

        ... 53 more
Caused by: java.lang.NullPointerException
        at
oracle.jdbc.driver.OracleSql.setNamedParameters(OracleSql.java:174)
        at
oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.jav
a:4229)
        at
oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatem
entWrapper.java:1080)
        at
weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:119)
        ... 54 more

Workaround

As a workaround to this issue, before running the LDAP User Create and Update Reconciliation scheduled job:

Login to My Oracle Support website at:

https://support.oracle.com
Search and download JDBC patch p26400304_122130_Generic.zip.
Apply the JDBC patch.
Run the LDAP User Create and Update Reconciliation scheduled job.

1.18.2 IT Resource Password is Updated as Null

Issue

Impacted Releases: 12c Release (12.2.1.3.0)

When Oracle Identity Governance is upgraded from Release 11g (11.1.2.3.0) to Release 12c (12.2.1.3.0), password of IT resources like Directory Server, Email Provider Definition - UMS, and OIA-ITRes are updated in Credential Store (CSF) as Null. This causes LDAP operations associated with these IT resources to fail.

Workaround

After upgrade, bring OIG Server up and immediately reset password for these IT resources types, Directory Server, Email Provider Definition - UMS, and OIA-ITRes.

To reset the IT resources password:

Login to Oracle Identity System Administration.
Locate the IT Resource for which you want to reset the password.
For Directory Server edit the Admin Password parameter value and for Email Provider Definition - UMS and OIA-ITRes edit the Password parameter value.

For detailed steps on how to search and modify IT Resources parameters, see Managing IT Resources in Administering Oracle Identity Governance.

1.18.3 Recommendations for Upgrade

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.

1.18.4 Oracle Identity Governance Server URL is Inaccessible After Rollback

Issue

Impacted Releases: 12c Release (12.2.1.3.0)

When Oracle Identity Governance Bundle Patch is rolled back, the previous version of Oracle Identity Governance is restored. When you try to access the OIG Server URL it is inaccessible as the /db/oim-config.xml file is overwritten.

Workaround

Workaround for this problem is to restore the base version of the /db/oim-config.xml file. For example, if you want to rollback Oracle Identity Governance Bundle Patch 12.2.1.3.180413, then before rollback, import the Oracle Identity Governance 12.2.1.3.0 base version /db/oim-config.xml file from the backup created before applying the Oracle Identity Governance Bundle Patch 12.2.1.3.180413. Then rollback the bundle patch.

1.18.5 Role Hierarchy Tab Shows Only 301 Roles

Issue

Impacted Releases: 12c Release (12.2.1.3.180713)

In the Role Hierarchy page, the Define Role Hierarchies panel shows only 301 roles.

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

Issue

Impacted Releases: 12c Release (12.2.1.3.190109)

When customizing the Add Members tab in Roles page, if the Fetch Size field is modified and the fetch size range is set to more than 25, then the search operation does not function as expected.

Workaround

To workaround this issue, make sure to set the fetch size value below 25.

1.18.7 Refresh Materialized View Scheduled Job Fails

Issue

Impacted Releases: 12c Release (12.2.1.3.190109)

When you run the Refresh Materialized View scheduled job manually by following steps in My Oracle Support document ID 2383245.1, the process fails.

Workaround

To workaround this issue, execute the below steps:

Download the patch.
Unzip the patch to <patchid>/files/oracle.oim.server/12.2.1.3.0/oracle.oim.symbol/server/db/oim/oracle/Upgrade/oim12cps3/list/Eval_trigger.sql
Login into OIM DB.
Execute the sql Eval_trigger.sql
Restart the OIM Server.

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

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

1.18.9 Errors Related to the For Reportees Feature

While using the Organization Name search criteria, at least one direct reportee should be associated with the organization. When organization name outside the reportee's organization is entered, the following error message is displayed:

IAM-2053037 : An error occurred while searching for the reportees as the organization name is invalid or not associated with any reportee (This is EXPECTED). Atleast 1 direct reportee should belong to the org name being searched.

The total number of direct reportees and indirect reportees must not exceed 1000. For Reportees does not work if number of direct reportees and indirect reportees are more than 1000, and the following error message is displayed:

“IAM-2053036 : An error occurred while searching for the reportees as the reportee size exceeded the limit 1,200. Please retry with other search criteria”

1.18.10 Identity Self Service and Identity System Administration Not Accessible

After applying this bundle patch, OIG server deployments for Identity Self Service and Identity System Administration fails with oracle.iam.ui.view and oracle.iam.ui.model applications.

When you apply the bundle patch and update the Oracle Identity Governance web applications, the OIG system libraries oracle.iam.ui.model(1.0,11.1.1.5.0) and oracle.iam.ui.view(11.1.1,11.1.1) goes to the Prepared state. The oracle.iam.console.identity.self-service.ear and oracle.iam.console.identity.sysadmin.ear are referencing these two libraries, and therefore, cause the deployment failure.

To workaround this issues, manually delete the oracle.iam.ui.model(1.0,11.1.1.5.0) andoracle.iam.ui.view(11.1.1,11.1.1) libraries from deployments, and redeploy them in WebLogic Server Administration Console. To do so:

In WebLogic Server Administration Console, go to Deployments, and click Lock and Edit.
Select the oracle.iam.ui.model(1.0,11.1.1.5.0) library, and click Delete. Do the same for the oracle.iam.ui.view(11.1.1,11.1.1) library.
Click Activate Changes.
In Deployments, click Lock and Edit.
Click Install, install the oracle.iam.ui.model(1.0,11.1.1.5.0) as a library by following all the default settings, and select the OIM cluster/server as the target. Click Finish and Save. Repeat for the same for the oracle.iam.ui.view(11.1.1,11.1.1) library.
Click Activate Changes. The libraries are running in Active state.
In Deployments, click Lock and Edit, and then click the Control tab.
Select oracle.iam.console.identity.sysadmin.ear, which is in the Prepared state, and then select Start / Serving all requests.
Select oracle.iam.console.identity.self-service.ear, which is in the Prepared state, and then select Start / Serving all requests.
After the two applications go to the Active state, click Release configuration.

After the referenced libraries and the oracle.iam.console.identity.self-service.ear and oracle.iam.console.identity.sysadmin.ear applications go to the Active state, the system is up and running.

1.18.11 Issues Related to User Login Creation with Special Characters

Issue

When a new user is created with a single quote ( ‘ ) in the first name or last name, there are 2 cn entries created in the OUD target attributes. When the reconciliation scheduled job is run, it fails to recon the user changes from the target to OIG.

Workaround

To workaround this issue, remove the cn entry with the \ appended before the single quote and then run the reconciliation scheduled job.

1.19 Related Documents

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.

1.20 Documentation Accessibility

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.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Title and Copyright Information

Oracle Fusion Middleware Oracle Identity Governance Bundle Patch Readme, OIM Bundle Patch 12.2.1.3.220115

F51341-01

January 2022