This document describes Bundle Patch 12.2.1.4.200204 for Oracle Unified Directory.
This readme document requires base installation of Oracle Unified Directory 12c (12.2.1.4.0). It contains the following sections:
Note:
For issues documented after the release of OUD Bundle Patch 12.2.1.4.200204, log into My Oracle Support. In the Search Knowledge Base field, enter 2602696.1. This is the ID of the document that describes the Oracle Fusion Middleware 12.2.1.4.0 Known Issues.1.1 Understanding Bundle Patches
This section describes bundle patches and explains differences between bundle patches, interim patches (also known as patch set exceptions), and patch sets.
1.1.1 Bundle Patch
A bundle patch is an official Oracle patch for Oracle Unified Directory. 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 libraries and files that have been rebuilt to implement one or more fixes. All of the fixes in a bundle patch are tested and certified to work with one another. Each bundle patch is cumulative. That is, the latest bundle patch includes all fixes in earlier bundle patches for the same release.
1.1.2 Interim Patch
In contrast to a bundle patch, an interim patch addressed only one issue for a single component. Although each interim patch was an official Oracle patch, it was not a complete product distribution and did not include packages for every component. An interim patch included only the libraries and files that had been rebuilt to implement a specific fix for a specific component.
You may also know an interim patch as: security one-off, exception release, x-fix, PSE, MLR, or hotfix.
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 Bundle Patch Recommendation
Oracle has certified the dependent Middleware component patches for Identity Management products and recommends that Customers apply these certified patches. For more information on these patches, see the note 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
This section describes the OUD bundle patch requirements for this release.
Complete the following steps before you apply or remove the bundle patch:
-
Verify that the OPatch version is 13.9.4.2.2 or higher.
-
Access and log into My Oracle Support at the following location:
-
In the Search Knowledge Base field, enter 1587524.1. This is the ID of the document that describes Using OUI NextGen OPatch 13 for Oracle Fusion Middleware 12c.
-
In the search results, click the link corresponding to document ID 1587524.1.
-
In the document, click the Patch 28186730 link which will take you to the screen where you can obtain the OPatch 13.9.4.2.2.
-
-
Verify the OUI Inventory:
OPatch needs access to a valid OUI inventory to apply patches. Validate the OUI inventory with the following commands:
Unix
$ opatch lsinventory
Windows
opatch.bat lsinventory
If the command throws errors than contact Oracle Support and work to validate and verify the inventory setup before proceeding.
-
Confirm the executables appear in your system
PATH.
Unix
$ which opatch
Windows$ which unzip
where opatch.bat
where unzip
If the command errors out, contact Oracle Support and work to validate and verify the inventory setup before proceeding. If either of these executables do not show in the
PATH
, correct the problem before proceeding. -
Create a location for storing the unzipped patch. This location will be referred to later in the document as
PATCH_TOP
.
1.4 Before Applying the Bundle Patch
This section describes the requirements before applying the bundle patch.
The following are the prerequisites before applying this bundle patch:
-
Prepare the application server instance for patching OUDSM.
Stop the Administration Server (the WebLogic domain used for OUDSM).
Note:
You must read about the OUDSM auto redeployment instructions in Documentation Updates before applying this bundle patch. -
Set
ORACLE_HOME
environment variable to Oracle Middleware Home Location (under which OUD is installed).For example:
Unix
$ <bash> export ORACLE_HOME="Oracle Middleware Home Location"
Windows
<prompt> set ORACLE_HOME="Oracle Middleware Home Location"
-
Verify that
ORACLE_HOME
is set correctly by running the following command.Unixls $ORACLE_HOME/OPatch/opatch
Windows
dir %ORACLE_HOME%\OPatch\opatch.bat
-
Stop all the Directory Server instances and domains where Oracle Unified Directory Services Manager (OUDSM) is installed, depending upon the domain configuration.
Stop Standalone Oracle Unified Directory Server
If you installed Oracle Unified Directory in a Standalone Oracle Unified Directory Server (Managed independently of WebLogic server) mode, stop all the Directory Server instances using the
start-ds
command.UnixORACLE_HOME/INSTANCE_NAME/OUD/bin/stop-ds
Windows
ORACLE_HOME\INSTANCE_NAME\OUD\bat\stop-ds.bat
Stop Collocated Oracle Unified Directory Server
If you installed Oracle Unified Directory in a Collocated Oracle Unified Directory Server (Managed through WebLogic server) mode, complete the following steps:
- Stop the OUD instance by running
the following command from command line
interface.
Unix
DOMAIN_HOME/bin/stopComponent.sh INSTANCE_NAME
Windows
DOMAIN_HOME\bin\stopComponent.bat INSTANCE_NAME
- Stop the node manager.
Unix
DOMAIN_HOME/bin/stopNodeManager.sh
Windows
DOMAIN_HOME\bin\stopNodeManager.cmd
- Stop the Oracle WebLogic
Administration Server.
Unix
DOMAIN_HOME/bin/stopWebLogic.sh
Windows
DOMAIN_HOME\bin\stopWebLogic.cmd
Stop the Oracle Directory Integration Platform and OUDSM Configured in a Single Domain
If you added OUDSM and Oracle Directory Integration Platform in a single domain, you must stop the Admin Server and Managed Server.
-
Stop the Oracle Directory Integration Platform Managed Server:
UnixDOMAIN_HOME/bin/stopManagedWebLogic.sh
Windows
DOMAIN_HOME\bin\stopManagedWebLogic.cmd
-
Stop the Oracle WebLogic Administration Server:
UnixDOMAIN_HOME/bin/stopWebLogic.sh
Windows
DOMAIN_HOME\bin\stopWebLogic.cmd
- Stop the OUD instance by running
the following command from command line
interface.
Note:
See Understanding the Oracle Unified Directory Installation Directories to know about OUD installation directories.1.5 Using the Oracle Patch Mechanism (Opatch)
Note:
You must have the latest version of Opatch (version 13.9.4.2.2 ) from My Oracle Support. Opatch requires access to a valid Oracle Universal Installer (OUI) Inventory to apply patches. The patching process uses both unzip and Opatch executables. After
sourcing the ORACLE_HOME
environment, Oracle recommends that you
confirm that both of these exist before patching. Opatch is accessible at:
$ORACLE_HOME/OPatch/opatch
When Opatch starts, it validates the patch to ensure there are no conflicts with the software already installed in your $ORACLE_HOME:
- If you find conflicts with a patch already applied to the
$ORACLE_HOME
, stop the patch installation and contact Oracle Support Services. - If you find conflicts with a subset patch already applied to the
$ORACLE_HOME
, continue Bundle Patch application. The subset patch is automatically rolled back before installation of the new patch begins. The latest Bundle Patch contains all fixes from the previous Bundle Patch in$ORACLE_HOME
.
This Bundle Patch is not -auto
flag enabled. Without
the -auto
flag, no servers need to be running. The Machine Name
& Listen Address can be blank on a default install.
See Also:
Patching with OPatchIdentifying the Version of OPatch
In general, there is a version of OPatch available for each version of the Oracle Universal Installer software.
- Change directory to the following
directory:
cd ORACLE_HOME/OPatch/
- Run the following
command:
./opatch version
For example:
./opatch version OPatch Version: 13.9.4.2.2 OPatch succeeded.
1.6 Applying the Bundle Patch
ORACLE_HOME
.
-
Conflicts with a patch already applied to the
ORACLE_HOME
.In this case, stop the patch installation, and contact Oracle Support Services.
-
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
.
1.7 After Applying the Bundle Patch
You need to perform certain tasks after applying the bundle patch
1.8 Creating the File based Access Control Log Publisher
This step is optional. You can create a File Based Access Control Log publisher for diagnosing ACI evaluation. This publisher should be disabled as soon as diagnostic is over as it impacts server performance.
Note:
Once this publisher is created, the de-installation of this patch will not be possible as the server would no longer be able to start.To create the File Based Access Control Log publisher, a server administrator must invoke the following dsconfig
command against a server instance that is already up and running:
dsconfig create-log-publisher \ --publisher-name "ACI logger" \ --type file-based-access-control \ --set enabled:true \ --set log-file:logs/acilog \ --hostname serverHostName --port 4444 \ --trustAll --bindDN cn=Directory\ Manager \ --bindPasswordFile passwordFile \ --no-prompt
The following entry is created in the config.ldif:
server
configuration file:
dn: cn=ACI logger,cn=Loggers,cn=config objectClass: ds-cfg-log-publisher objectClass: ds-cfg-access-control-log-publisher objectClass: ds-cfg-file-based-access-control-log-publisher objectClass: top ds-cfg-enabled: true ds-cfg-java-class: org.opends.server.loggers.accesscontrol.TextAccessControlLogPublisher ds-cfg-asynchronous: true cn: ACI logger ds-cfg-log-file-permissions: 640 ds-cfg-log-file: logs/acilog
1.9 Removing the Bundle Patch
If you experience any problems after installing the bundle patch, you can remove the bundle patch.
Execute the following commands to remove the bundle patch:
1.10.1 Resolved Issues in OUD Bundle Patch 12.2.1.4.200204
The following table lists the issues resolved in OUD Bundle Patch 12.2.1.4.200204:
Table 1-1 Issues Resolved in OUD Bundle Patch 12.2.1.4.200204:
Bug Number | Description |
---|---|
30645038 | OUD 12.2.1.3 JAN'20 BP - COUPLE OF NEWLY ADDED CORE-ENTRYCACHE TESTS FAILING IN FARM EXECUTION |
30265103 | OUD11G - BEFORE BP DS-RLIM-IDLE-TIME-LIMIT ATT. WAS IN SECS AFTER BP IS MS |
30367492 | UNINSTALL FAILS DUE TO RESOLVING HOST TO 0.0.0.0 |
29885985 | OUD ALLOWS ADDING USER INTO GROUP EVEN IF USER DOESN'T EXIST WHEN RI IS ENABLED |
29661762 | CUSTOM PASSWORD POLICIES REQUIRE A INDIVIDUAL "PASSWORDSTORAGESCHEME" |
30074000 | Fix for Bug 30074000 |
29682036 | FORKJOIN WFE WITH LEFT-OUTER-JOIN DOES NOT WORK |
28135591 | UNABLE TO SPECIFY A DENIED-CLIENT HOSTNAME THAT BEGINS WITH A NUMERIC VALUE |
29945677 | ISMEMBEROF SUBSTRING SEARCH FILTER RETURNS NO ENTRIES |
30094884 | REGRESSION FOR BUG 29724794 |
29418242 | (JE 7.0.7) ENVIRONMENT MUST BE CLOSED, CAUSED BY: COM.SLEEPYCAT.JE.THREADINTERRU |
1.11 Known Issues and Workarounds
This section describes about the known issues in the current release.
Known issues and their workarounds in Oracle Unified Directory Release 12c (12.2.1.4.0) are described in the Oracle Unified Directory 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/en/middleware/idm/suite/12.2.1.4/idmrn/index.html
For issues documented after the release of this OUD Bundle Patch Release (12.2.1.4.200204), refer to My Oracle Support Document 2602696.1 at https://support.oracle.com
For information about OPatch issues, see My Oracle Support and use the OPatch version provided with the product.
1.12 Documentation Updates
This section describes documentation updates for this release.
Note:
See SCIM REST API for Oracle Unified Directory and REST API for Oracle Unified Directory Data Management at the following URL: https://docs.oracle.com/en/middleware/idm/unified-directory/12.2.1.4/oudsr/index.html and https://docs.oracle.com/en/middleware/idm/unified-directory/12.2.1.4/ouddr/index.htmlOUDSM Auto Redeployment Instructions
The oudsm.ear
file is shipped along with the OUD Bundle
Patch 12.2.1.4.200204 at:
bppatchnumber/files/oracle.idm.oud.odsm/12.2.1.4.0/oracle.idm.oud.odsm.symbol/odsm/oudsm.ear
It would be patched at the following location:
ORACLE_HOME/oud/odsm/oudsm.ear
When you restart the Server for the first time after applying the patch,
it will automatically redeploy the new oudsm.ear
file. Therefore,
you might experience a slower restart of the Server. You must look at the logs
related to oudsm.ear
file deployment.
If for any reason the oudsm.ear
file deployment fails
during the first restart of the Server, then you manually need to redeploy the
file.
1.13 Related Documents
For more information, see the following resources:
-
Oracle Fusion Middleware Documentation
This contains documentation for all Oracle Fusion Middleware 12c products.
-
This site contains additional documentation that is not included as part of the documentation libraries.
1.14 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.
Oracle Fusion Middleware Oracle Unified Directory Bundle Patch Readme, 12c (12.2.1.4.200204)
F25670-03
January 2020
Copyright © 2020, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.