DSCC CAN NOT CREATE NEW DIRECTORY SERVER INSTANCE AFTER APPLYING ODSEE 11.1.1.7.160719 BP (Doc ID 2223482.1)

Last updated on FEBRUARY 15, 2017

Applies to:

Oracle Directory Server Enterprise Edition - Version 11.1.1.7.160719 to 11.1.1.7.160719 [Release 11gR1]
Microsoft Windows x64 (64-bit)

Symptoms

The DSCC can not create a new Directory Server instance after applying the ODSEE 11.1.1.7.160719 Bundle Patch on Windows platform.

And we see the following error message in the dscc agent log when the dscc agent starts up.

<dscc agent log>
***************
[21/Dec/2016:20:24:21 +0900] - 1 - Starting DSCC agent
[21/Dec/2016:20:24:21 +0900] - 1 - Java Version: 1.6.0_38 (Java Home: c:\sun\odsee11.1.1.7\dsee7\jre)
[21/Dec/2016:20:24:21 +0900] - 1 - Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
[21/Dec/2016:20:24:21 +0900] - 1 - Java HotSpot(TM) Client VM (build 20.13-b02, mixed mode)
[21/Dec/2016:20:24:21 +0900] - 1 - Creating dsadm mbean
[21/Dec/2016:20:24:21 +0900] - 1 - Creating dpadm mbean
[21/Dec/2016:20:24:21 +0900] - 1 - Creating utils mbean
[21/Dec/2016:20:24:22 +0900] - 1 - JMX connector server started on port 3997
[21/Dec/2016:20:27:08 +0900] - 12 - Exception javax.naming.CommunicationException thrown:
[21/Dec/2016:20:27:08 +0900] - 12 - simple bind failed: milk.jp.oracle.com:3999
javax.naming.CommunicationException: simple bind failed: milk.jp.oracle.com:3999 [Root exception is javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair]
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:195)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2720)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
:
***************



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms