My Oracle Support Banner

OUD12c Attempting to Initialize Multiple Suffixes Results in the Message "Unexpected error during the initialization of suffix dc=xyz,dc=com." (Doc ID 2478171.1)

Last updated on MARCH 12, 2019

Applies to:

Oracle Unified Directory - Version 12.2.1.3.0 to 12.2.1.3.180829 [Release 12c]
Information in this document applies to any platform.

Symptoms

1) Oracle Unified Directory 12.2.1.3.180806 with two Directory Server instances with a large amount of backends; Example of the base DNs:

- dc=a,dc=example,dc=com
- dc=b,dc=123,dc=example,dc=com
- dc=345,dc=example,dc=com
- dc=apps,dc=us,dc=example,dc=com
- dc=au,dc=example,dc=com
- dc=boom,dc=in,dc=example,dc=com
- dc=c,dc=example,dc=com
- dc=cc,dc=example,dc=com
- dc=d,dc=example,dc=com
- dc=e,dc=example,dc=com
- dc=emea,dc=123,dc=example,dc=com
- dc=equity,dc=uk,dc=example,dc=com
- dc=equity,dc=us,dc=example,dc=com
- dc=example,dc=com
- dc=f,dc=example,dc=com
- dc=g,dc=uk,dc=example,dc=com
- dc=h,dc=example,dc=com
- dc=hh,dc=us,dc=example,dc=com
- dc=i,dc=example,dc=com
- dc=i,dc=ch,dc=example,dc=com
- dc=japan,dc=example,dc=com
- dc=k,dc=example,dc=com
- dc=m,dc=example,dc=com
- dc=ml,dc=bom,dc=in,dc=example,dc=com
- dc=o,dc=example,dc=com
- dc=p,dc=example,dc=com
- dc=r,dc=example,dc=com
- dc=rush,dc=example,dc=com
- dc=s,dc=example,dc=com
- dc=s,dc=uk,dc=example,dc=com
- dc=t,dc=example,dc=com
- dc=t,dc=us,dc=example,dc=com
- dc=uk,dc=example,dc=com
- dc=us,dc=example,dc=com
- dc=wfd,dc=us,dc=example,dc=com
- dc=123,dc=example,dc=com
- dc=w,dc=example,dc=com
- dc=x,dc=example,dc=com

  

2) After replication is configured dsreplication initialize must be completed in order for replication to work as directed by the below output.

<SNIPPED>
Reading Updated Configuration ...... Done.

Initializing registration information on server
HOST:5444 with the contents of server
HOST:4444 ..... Done.

Initializing schema on server HOST:5444 with the schema
of server HOST:4444 ..... Done.

Initializing integration suffixes on server HOST:5444
with the contents of server HOST:4444 ............................................................................................... Done.

Replication has been successfully enabled. Note that for replication to work
you must initialize the contents of the base DN's that are being replicated
(use dsreplication initialize to do so).

See /tmp/oud-replication-5792034250041645573.log for a detailed log of this
operation.

$

  

3) Perform an initialization as directed in the previous output and this fails.

Initializing the contents of a base DN removes all the existing contents of
that base DN. You have chosen to initialize the following base DNs:
- dc=a,dc=example,dc=com
- dc=b,dc=123,dc=example,dc=com
- dc=345,dc=example,dc=com
- dc=apps,dc=us,dc=example,dc=com
- dc=au,dc=example,dc=com
- dc=boom,dc=in,dc=example,dc=com
- dc=c,dc=example,dc=com
- dc=cc,dc=example,dc=com
- dc=d,dc=example,dc=com
- dc=e,dc=example,dc=com
- dc=emea,dc=123,dc=example,dc=com
- dc=equity,dc=uk,dc=example,dc=com
- dc=equity,dc=us,dc=example,dc=com
- dc=example,dc=com
- dc=f,dc=example,dc=com
- dc=g,dc=uk,dc=example,dc=com
- dc=h,dc=example,dc=com
- dc=hh,dc=us,dc=example,dc=com
- dc=i,dc=example,dc=com
- dc=i,dc=ch,dc=example,dc=com
- dc=japan,dc=example,dc=com
- dc=k,dc=example,dc=com
- dc=m,dc=example,dc=com
- dc=ml,dc=bom,dc=in,dc=example,dc=com
- dc=o,dc=example,dc=com
- dc=p,dc=example,dc=com
- dc=r,dc=example,dc=com
- dc=rush,dc=example,dc=com
- dc=s,dc=example,dc=com
- dc=s,dc=uk,dc=example,dc=com
- dc=t,dc=example,dc=com
- dc=t,dc=us,dc=example,dc=com
- dc=uk,dc=example,dc=com
- dc=us,dc=example,dc=com
- dc=wfd,dc=us,dc=example,dc=com
- dc=123,dc=example,dc=com
- dc=w,dc=example,dc=com
- dc=x,dc=example,dc=com

Initializing base DN dc=a,dc=example,dc=com with the contents from
HOST:4444:
950 entries processed (47.45% complete).
> Time elapsed: 1 seconds.
1806 entries processed (90.21% complete).
> Time elapsed: 12 seconds.
2002 entries processed (100.00% complete).
> Time elapsed: 20 seconds.
Base DN initialized successfully.
The operation completed in 19 seconds.

Initializing base DN dc=e,dc=uk,dc=example,dc=com with the contents from
HOST:4444:
949 entries processed (47.40% complete).
> Time elapsed: 1 seconds.
1985 entries processed (99.15% complete).
> Time elapsed: 7 seconds.
Base DN initialized successfully.
The operation completed in 12 seconds.

Initializing base DN dc=w,dc=example,dc=com with the contents from
HOST:4444:
0 entries processed (0.00% complete).
> Time elapsed: 1 seconds.
0 entries processed (0.00% complete).
> Time elapsed: 1 seconds.
0 entries processed (0.00% complete).
> Time elapsed: 1 seconds.
0 entries processed (0.00% complete).
> Time elapsed: 1 seconds.
0 entries processed (0.00% complete).
> Time elapsed: 1 seconds.
0 entries processed (0.00% complete).
> Time elapsed: 1 seconds.

Unexpected error during the initialization of suffix dc=w,dc=example,dc=com.
Last log details: [13/Sep/2018:16:27:51 +0100] severity="NOTICE" msgCount=0
msgID=9896349 message="Initialize Backend task Initialize server
HOST:5444 with server HOST:4444
for base DN dc=wscc,dc=example,dc=com-5 started execution"
[13/Sep/2018:16:27:51 +0100] severity="NOTICE" msgCount=1 msgID=15138959
message="Local directory server 20049 is starting online full update for
exporting 2002 entries from suffix dc=w,dc=example,dc=com to remote directory
server 4011"
[13/Sep/2018:16:27:52 +0100] severity="NOTICE" msgCount=2 msgID=15139015
message="Resending a new initialization start for an initialization of a
remote server due to the root error : The following servers did not
acknowledged initialization in the expected time. They are potentially down or
too slow. Servers list: [4011]"
[13/Sep/2018:16:27:52 +0100] severity="NOTICE" msgCount=3 msgID=15138960
message="Local directory server 20049 has finished online full update for
exporting suffix data dc=w,dc=example,dc=com to remote directory server 4011.
The following servers did not acknowledged initialization in the expected
time. They are potentially down or too slow. Servers list: [4011]"
[13/Sep/2018:16:27:52 +0100] severity="SEVERE_ERROR" msgCount=4 msgID=14942401
message="The following servers did not acknowledged initialization in the
expected time. They are potentially down or too slow. Servers list: [4011]"
[13/Sep/2018:16:27:52 +0100] severity="NOTICE" msgCount=5 msgID=9896350
message="Initialize Backend task Initialize server
HOST:5444 with server HOST:4444
for base DN dc=w,dc=example,dc=com-5 finished execution". Task state:
stopped_by_error. Check the error logs of HOST:4444 for
more information.
See /tmp/oud-replication-2059547258605990188.log for a detailed log of this
operation.
$

  

The last lines of the debug log:

[13/Sep/2018:16:50:50 +0100] 1411872 message info thread={Replication Heartbeat Monitor on RS HOST/IP:9989 32011 for dc=e,dc=uk,dc=example,dc=com in DS 15279(4653)} threadDetail={parentThread=Replication State Saver for server id 15279 and domain dc=equity,dc=uk,dc=example,dc=com(3839) isDaemon=false } method={run(HeartbeatMonitor.java:182)} Heartbeat monitor is exiting.Exception (HeartbeatMonitor.java:182)
[13/Sep/2018:16:51:01 +0100] 1432544 message info thread={Replication Heartbeat Monitor for Connected Replica HOST 2041,cn=Replication Server 9989 HOST 32011,cn=dc_g_dc_uk_dc_example_dc_com,cn=replication(4657)} threadDetail={parentThread=Replication Server Listener 32011(2316) isDaemon=false } method={run(HeartbeatMonitor.java:182)} Heartbeat monitor is exiting.Exception (HeartbeatMonitor.java:182)
[13/Sep/2018:16:51:01 +0100] 1432614 message info thread={Replication Heartbeat Monitor on RS HOST/IP:9989 32011 for dc=g,dc=uk,dc=example,dc=com in DS 2041(4661)} threadDetail={parentThread=Replication State Saver for server id 2041 and domain dc=g,dc=uk,dc=example,dc=com(3891) isDaemon=false } method={run(HeartbeatMonitor.java:182)} Heartbeat monitor is exiting.Exception (HeartbeatMonitor.java:182)
[13/Sep/2018:16:53:34 +0100] 1695030 caught error thread={LDAP Request Handler 0 for connection handler LDAP Administration Connector 0.0.0.0 port 5444(27)} threadDetail={parentThread=main(1) isDaemon=false } method={readMessage(LDAPReader.java:100)} caught={org.opends.sdk.DecodeException: Cannot decode the provided ASN.1 integer element because the length of the element value was not between one and four bytes (actual length was 84)}
at org.opends.sdk.DecodeException.fatalError(DecodeException.java:87)
[13/Sep/2018:16:53:34 +0100] 1695031 caught error thread={LDAP Request Handler 0 for connection handler LDAP Administration Connector 0.0.0.0 port 5444(27)} threadDetail={parentThread=main(1) isDaemon=false } method={run(LDAPRequestHandler.java:229)} caught={org.opends.server.types.LDAPException: Cannot decode the provided ASN.1 sequence as an LDAP message because the first element of the sequence could not be decoded as an integer message ID: org.opends.sdk.DecodeException: Cannot decode the provided ASN.1 integer element because the length of the element value was not between one and four bytes (actual length was 84)}
Caused by: org.opends.sdk.DecodeException: Cannot decode the provided ASN.1 integer element because the length of the element value was not between one and four bytes (actual length was 84)
at org.opends.sdk.DecodeException.fatalError(DecodeException.java:87)
WRITE ASN.1 OCTETSTRING(type=0x4, length=329, value=Cannot decode the provided ASN.1 sequence as an LDAP message because the first element of the sequence could not be decoded as an integer message ID: org.opends.sdk.DecodeException: Cannot decode the provided ASN.1 integer element because the length of the element value was not between one and four bytes (actual length was 84))
LDAPMessage(msgID=0, protocolOp=ExtendedResponse(resultCode=2, errorMessage=Cannot decode the provided ASN.1 sequence as an LDAP message because the first element of the sequence could not be decoded as an integer message ID: org.opends.sdk.DecodeException: Cannot decode the provided ASN.1 integer element because the length of the element value was not between one and four bytes (actual length was 84), oid=1.3.6.1.4.1.1466.20036))

 

Changes

N/A

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.