This document describes the bug fixes that are included with Bundle Patch 12c Release (12.2.1.3.210115) for Oracle Internet Directory and the procedure to install it. It contains the following topics:

New Features and Enhancements in OID Bundle Patch 12.2.1.3.210115

Oracle Internet Directory 12.2.1.3.210115 BP includes the following new enhancement:

Support for Running the Oracle Internet Directory Server Diagnostic Command-Line Tool without SYS User Password

You can now run the Oracle Internet Directory Server Diagnostic command-line tool (oiddiag) without providing the SYS database user password. When you do so, the tool only collects diagnostics data that does not require sysdba privileges.

Additional Information About OID Bundle Patch 12.2.1.3.210115

The following table lists the MOS notes that you can refer to for additional information about the OID bundle patch 12.2.1.3.210115. You can view all the MOS notes listed in this table by searching for the Doc ID in My Oracle Support.

Bug Number Doc ID Description

32250901

2743483.1

OID 12c Doc 32250901 - oiddebuglogsetter.sh Script in OID12cPS3 Jan'21 and OID12cPS4 Jan'21 Bundle Patches

32250993

2743489.1

OID 12c Doc 32250993 - Manual Addition of <Hostname> in $domain_home/config/config.xml

32296821

2535934.1

OID 12c Creating an Instance Using Same Instance Name From a Prior Failed Configuration Attempt Fails to Start: [Server start command for OID server '<INSTANCE NAME>' failed due to: [Server failed to start up but Node Manager was not aware of the reason]

Understanding Bundle Patches

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

Stack Patch Bundle

Stack patch Bundle deploys the IDM product and dependent FMW patches using a tool. For more information about these patches, see Quarterly Stack Patch Bundles (Doc ID 2657920.1) at https://support.oracle.com.

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.

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.

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.

Using the Oracle Patch Mechanism (Opatch)

OPatch is a Java-based utility that runs on all supported operating systems and requires installation of the Oracle Universal Installer. It is used to apply patches to Oracle software.

Note:

Oracle recommends that you have the latest version of Opatch (version 13.9.4.2.5 or higher) 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 Your Environment Using OPatch in Patching with OPatch.

Identifying the Version of OPatch

In general, there is a version of OPatch available for each version of the Oracle Universal Installer software.

To identify the version of OPatch:

  1. Change directory to the following directory:
    cd ORACLE_HOME/OPatch/
  2. Run the following command:
    ./opatch version

    For example:

    ./opatch version
OPatch Version: 13.9.4.2.5

OPatch succeeded.

Obtaining Patches Required for Your Installation

You can search for and download the patches required for your installation from My Oracle Support.

After you sign in to My Oracle Support, click the Patches & Updates tab, which provides various tools that allow you to quickly locate the patches important to your Oracle Internet Directory.

Before Applying the Bundle Patch

This section describes the requirements before applying the bundle patch.

Complete the following prerequisites before applying this bundle patch:

  1. If Oracle Internet Directory is installed then stop all OID server instances using shutdown()command:
    shutdown(name='instance-name',type='OID')

    Or you can also run the following script to stop OID server instances:

    UNIX

    stopComponent.sh 'instance-name'

    Windows

    stopComponent.cmd 'instance-name'
  2. If Oracle Directory Integration Platform is installed:
    1. Stop the Oracle Directory Integration Platform using the WLST command:
      stopApplication ("DIP")

    2. Stop the Oracle WebLogic Administration Server:

      UNIX

      DOMAIN_NAME/bin/stopWebLogic.sh

      Windows

      DOMAIN_NAME\bin\stopWebLogic.cmd

      Note:

      Where DOMAIN_NAME is the root directory of the domain. (The name of this directory is the name of the domain.). By default, this directory is ORACLE_HOME\user_projects\domains\DOMAIN_NAME.

    3. Stop the Oracle WebLogic managed components, such as Oracle Directory Integration Platform and Oracle Directory Services Manager:

      UNIX

      DOMAIN_NAME/bin/stopManagedWebLogic.sh managed_server_name admin_url

      Windows

      DOMAIN_NAME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

      Where managed_server_name specifies the name of the Managed Server (The default value is wls_ods1.) and admin_url specifies the listen address (host name, IP address, or DNS name) and port number of the domain's Administration Server.

      Example

      c:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopManagedWebLogic.cmd wls_ods1 http://AdminHost:7001

    Note:

    The above steps are followed only when there is a technical need to manually stop the Oracle Directory Integration Platform application.

  3. Before you run OPatch, ensure that you set the ORACLE_HOME environment variable to Oracle home location (under which Oracle Internet Directory or Oracle Directory Integration is installed).

    Example

    UNIX

    <bash> export ORACLE_HOME="/install_location/Oracle_Home/OID_Dir"
    Windows
    <prompt> set ORACLE_HOME="\install_location\Oracle_Home\OID_Dir

  4. Verify that ORACLE_HOME is set correctly by running the following command.

    UNIX

    ls $ORACLE_HOME/OPatch/opatch
    Windows
    dir %ORACLE_HOME%\OPatch\opatch.bat

Applying the Bundle Patch

You can apply the bundle patch for Oracle Internet Directory or Oracle Directory Integration Platform either in an existing or in a new installation.

Applying the Bundle Patch for an Existing Installation

Perform the following steps to apply the bundle patch for an existing Oracle Internet Directory or Oracle Directory Integration Platform installation:
  1. Unzip the patch zip file into the PATCH_TOP, where PATCH_TOP is a directory path that temporarily contains the patch for installation.
    $ unzip -d PATCH_TOP p32388309_122130_Linux-x86-64.zip

    Note:

    In Windows, the unzip command has a limitation of 256 characters in the path name. In scenarios where you face this issue, use an alternate ZIP utility like 7-Zip to unzip the patch.
  2. Set your current directory to the directory where the patch is located.

    UNIX

    $ cd PATCH_TOP/32388309

    Windows

    PATCH_TOP\32388309
  3. Run OPatch to apply the patch.

    UNIX

    $ [ORACLE_HOME]/OPatch/opatch apply

    Windows

    [ORACLE_HOME]\OPatch\opatch.bat apply

    Note:

    When OPatch starts, it validates the patch and makes sure that there are no conflicts with the software already installed in the ORACLE_HOME. OPatch categorizes two types of conflicts:

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

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

Applying the Bundle Patch for a New Installation

Perform the following steps to apply the bundle patch for a new Oracle Internet Directory or Oracle Directory Integration Platform installation:
  1. Install Oracle Internet Directory binaries.
    For more information about installing the binaries, see Installing the Oracle Internet Directory Software in Installing and Configuring Oracle Internet Directory.
  2. Apply patch, as described in Applying the Bundle Patch for an Existing Installation.
  3. For Oracle Internet Directory, you must configure it after you install Oracle Internet Directory binaries. For more information, see Configuring Oracle Internet Directory Domain in Installing and Configuring Oracle Internet Directory.

    After you install and configure Oracle Internet Directory, see in Getting Started With Oracle Internet Directory in Administering Oracle Internet Directory.

  4. For Oracle Directory Integration Platform, you must configure it after you install Oracle Internet Directory binaries.
    For more information, see Configuring Oracle Directory Integration Platform in Installing and Configuring Oracle Internet Directory.

After Applying the Bundle Patch

Based on the type of product installed, follow the instruction given below:

  • If Oracle Internet Directory is installed, then restart all Oracle Internet Directory Server instances using WLST start()command: 

    start(name='instance-name',type='OID')

  • If Oracle Directory Integration Platform is installed, then perform the following steps:

    1. Restart the Oracle WebLogic Administration Server.

      UNIX

      DOMAIN_NAME/bin/startWebLogic.sh

      Windows

      DOMAIN_NAME\bin\startWebLogic.cmd

      Note:

      Where DOMAIN_NAME is the root directory of the domain. (The name of this directory is the name of the domain.). By default, this directory is ORACLE_HOME\user_projects\domains\DOMAIN_NAME.

    2. Restart the Oracle WebLogic managed components, such as Oracle Directory Integration Platform and Oracle Directory Services Manager.

      UNIX

      DOMAIN_NAME/bin/startManagedWebLogic.sh managed_server_name admin_url

      Windows

      DOMAIN_NAME\bin\startManagedWebLogic.cmd managed_server_name admin_url

      Where managed_server_name specifies the name of the Managed Server (The default value is wls_ods1.) and admin_url specifies the listen address (host name, IP address, or DNS name) and port number of the domain's Administration Server.

      Example

      c:\Oracle\Middleware\user_projects\domains\base_domain\bin\startManagedWebLogic.cmd wls_ods1 http://AdminHost:7001

  • If you are using Oracle Directory Server Enterprise Edition as the back-end directory for Oracle Directory Integration Platform synchronization, then update Oracle Directory Server Enterprise Edition plug-in:

    1. Change to the directory where the patch was unzipped.

    2. Select either dip-plugin.so (UNIX) or dip-plugin.dll (Windows) from the following directory in the Oracle Identity Management distribution package.

      UNIX

      ORACLE_HOME/dip/utils/dip-plugin

      Windows

      ORACLE_HOME\dip\utils\dip-plugin

    3. Copy it into your Oracle Directory Server Enterprise Edition installation:

      UNIX

      32-bit system

      INSTALL-PATH/dsee7/lib

      64-bit system

      INSTALL-PATH/dsee7/lib64

      Windows

      32-bit system

      INSTALL-PATH\dsee7\lib

      64-bit system

      INSTALL-PATH\dsee7\lib64
    4. Restart Oracle Directory Server Enterprise Edition instance using the dsadm command:
      $ dsadm restart instance-path

Removing the Bundle Patch

If you experience any problems after installing this patch, remove the patch as follows:

  1. Make sure to follow the same Prerequisites or pre-install steps (if any) when you uninstall a patch. This includes setting up any environment variables like ORACLE_HOME and verifying the OUI inventory before uninstalling.

  2. Run OPatch to uninstall the patch:
    $[ORACLE_HOME]/OPatch/opatch rollback -id 32388309

  3. If you are using Oracle Directory Server Enterprise Edition (ODSEE) as the back-end directory for Oracle Directory Integration Platform (DIP), you must roll back the ODSEE plug-in.

  4. If you are using ODSEE or OUD as the back-end directory for Oracle Directory Integration Platform, please contact your ORACLE support incase your password is encrypted by the plug-in while the new plug-in is running.

    Note:

    This can be in scenarios where you are using ODSEE or OUD as the DIP backend directory and you are also using the feature Password Translate.
  5. Start the NodeManager and the AdminServer with the following commands:
    $DOMAIN_HOME/bin/startNodemanager.sh
$DOMAIN_HOME/bin/startWeblogic.sh

    Note:

    It is not required to start the Admin Server for Standalone installations.
  6. If OID is installed, restart all Oracle Internet Directory Server instances using startComponent.sh command:
    $DOMAIN_HOME/bin/startComponent.sh instance-name
    or you can start the Oracle Internet Directory Server instances by connecting to the AdminServer via WLST and executing the WLST start()command.
    start(name='instance-name',type='OID')
    If DIP is installed, restart the Weblogic Managed server DIP was deployed to
    $DOMAIN_HOME/bin/startManagedWeblogic.sh <managed server>

    or you can start the Weblogic Managed server DIP was deployed to by connecting to the AdminServer via WLST and executing the WLST start()command. 

    start('managedServerName','Server')

Resolved Issues

This section lists the issues resolved in 12c Release.

Issues Resolved in 12c Release (12.2.1.3.210115)

The following table lists the issues resolved in OID Bundle Patch 12.2.1.3.210115:

Table 1-1 Resolved Issues in 12c Release (12.2.1.3.210115)

Bug Number Bug Name
20360006 LOADBALANCER PING CAUSES "SGSLUFREAD: HARD ERROR ON READ, OS ERROR = 104"
24464510 OID BECOMES UNRESPONSIVE INTERMITTENTLY
25557873 IN DIP PROFILE, "UPDATE SEARCH COUNT" SEEMS TO CAUSE SKIPPING OF CHANGES SYNCH
26828926 INCORPORATE ISW RESYNC CAPABILITIES INTO DIP
27253930 DIP ERROR WHEN SAVING SYNCHRONIZATION PROFILE IN EM PASSWORD MORE THEN 15 CHARS
27825430 FEATURE TO RUN OIDDIAG WITHOUT SYS USER
28502265 UNABLE TO RUN PROVSUBTOOL AGAINST OUD SERVER TO OBTAIN SUBSCRIPTION LIST
28678501 BUGS 27568073 27911420: OID 12C REPLICATION FAILS AFTER WLS ADMIN SERVER RESTART
29656196 NEED CORRECT /ETC/HOSTS CONFIGURATION FOR ALIASES
29692493 OID 11.1.1.9.160719 PORT STOPS RESPONDING
29946589 DIP SYNC FOR MODDN OR MODRDN GIVES NEWSUPERIOR A NULL VALUE
30091360 IMPORT USER DATA FROM LDIF FILE VIA ODSM FAILS
31040001 OID INTERNAL PRODUCTION MT - REPLICATION BETWEEN ADC AND UCF NOT WORKING FOR ORG GROUPS
31421942 OID CLEAN UP - OS RESOURCE AND SAME INSTANCE NAME FROM A PRIOR FAILED CONFIGURATION ATTEMPT FAILS TO START:(DOC ID 2535934.1)
31422015 OID11G: HOW TO AUDIT/TRACE AND CAPTURE MODIFICATION OF AN OBJECTCLASS NAME (DOC ID 2471961.1)

Issues Resolved in 12c Release (12.2.1.3.200526)

The following table lists the issues resolved in OID Bundle Patch 12.2.1.3.200526:

Table 1-2 Resolved Issues in 12c Release (12.2.1.3.200526)

Bug Number Bug Name
29547874 12C DIP WHEN USED WITH DNCONVERT DELETES ALL USERS FROM GROUPOFUNIQUENAMES IN OUD
30104525 OIDLDAPD PROCESS CRASHING IN OID 12C ON SOLARIS 11 (SPARC 64-BIT)
27347619 LRGPPR, PASSWORD POLICY REFRESH IS FAILING ON MULTI SERVER[FIX FOR REGRESSION IN FIX FOR BUG#22334103]
28790589 OID 12C REMTOOL PCHGPWD AND PRESETPWD DOES NOT APPLY TO CONSUMER NODES
28581199 ENTRY INCLUDING UPPERCASE BEHIND RDN FAILES TO SYNC AFTER APPLY PATCH 28437599
27625817 DIP FAILS TO SYNC UPDATE WITH 'B CANNOT BE CAST TO JAVA.LANG.STRING'
27547104 ANONYMOUS SASL BIND TO OID POPULATES PWDFAILURETIME IN ROOTDSE

Issues Resolved in 12c Release (12.2.1.3.180621)

The following table lists the issues resolved in 12c Release (12.2.1.3.180621):

Table 1-3 Resolved Issues in 12c Release (12.2.1.3.180621)

Bug Number Bug Name

27901525

OID MBEAN PROPERTY - SETEMPROPERTIES IS MISSING

26880404

BUG TO TRACK ROOT CAUSE OF NULL VALUES COMING TO MANDATORY VALUE IN OID

27275840

DI: ADD TRACING TO ALL ERROR CASES IN GSLDPSEARCHSTART

25095598

CAN NOT SYNC THE USER ENTRY'S MULTIBYTE VALUE FROM OUD TO AD

27442306

CACHING ISSUE WITH THE SUBSCRIBED USERS FOR EBS IN OID

27336338

TECHPLAT: JAVA_HOME IN PROVSUBTOOL POINT TO NON-EXIST ORACLE_HOME/JDK IN OID 12C

25598301

REPLICATION NOT SUPPORTED IN OID WITH TLSV1.2 AND WITHOUT NO-AUTH CIPHERS

27457322

SIM: CDC - US2 - OID THREAD RESTART ON CHCLMX0010

27306630

MS25:RE12:P2T[EEEF->EEEF-TEST] FAILED AT START IDM SERVERS

27472046

GSE: 17D: LDAPSEARCH RETURNING WRONG ATTRIBUTES FOR DN IN SDI

Issues Resolved in 12c Release (12.2.1.3.180413)

The following table lists the issues resolved in 12c Release (12.2.1.3.180413):

Table 1-4 Resolved Issues in 12c Release (12.2.1.3.180413)

Bug Number Bug Name

26943632

BULKDELETE IMPROVEMENT: FAST DELETE HUGE AMNT OF ENTRIES W/ FILTER SUPPORT

23236277

OID 11G PROCESS HANGS

25989135

A 'REPLACE' OF USERCERTIFICATE ON SUPPLIER RESULTS IN 'ADD' ON REPLICA(S)

27150568

NOT LOADING CORRECT DEFAULT VALUE FOR THE ATTRIBUTE ORCLECACHEMAXENTSIZE ON 12C

25729334

OIDLDAPD PROCESS SHUTS DOWN AND RESTARTS INTERMITTENTLY PRODUCING STACK DUMPS

26922555

REMTOOL -BACKUPMETADATA PARAMETER NOT AVAILABLE IN 12.2.1.3.0

27099047

TOTALTIME AND OPTIME WRONGLY SWAPPED IN ALERT*.LOG

26650058

OID INSTANCE CONFIG MBEAN ATTRIBUTES NOT IN READ WRITE MODE

26176227

CONFIG.SH FAILS TO CREATE OID INSTANCE, OID NOT STARTING

26883409

SCHEMA CORRUPTION AFTER CUSTOM OBJECTCLASS GETS REPLICATED

26770219

OID: REALM "DC=US,DC=ORACLE,DC=COM" CREATION FAILED FOR INSTANCE "OID1

27588675

OID SCHEMA LOAD IN RCU FAILS WITH LDAP_LINUX-X64:12.2.1.3.0.1-180221.1418

26268699

Fix for Bug 26268699

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.