My Oracle Support Banner

OID 10g LDAP Replication Bootstrap Fails With: Replication BOOTSTRAP_ERROR mode detected (Doc ID 1232455.1)

Last updated on NOVEMBER 12, 2019

Applies to:

Oracle Internet Directory - Version 9.0.4 to 10.1.2 [Release 10gR1 to 10gR2]
Information in this document applies to any platform.
***Checked for relevance on 30-July-2013***

Symptoms

Oracle Internet Directory (OID) 10g (i.e., 10.1.2.x)

Installation of a LDAP replica completes successfully with no errors in remtool.log.

However, the bootstrap by replication server on the replica following fails with:

Replication BOOTSTRAP_ERROR mode detected


The $ORACLE_HOME/ldap/oidrepld00.log keeps being updated with the following, for example:

oidrepld: Release 10.1.2.3.0 - Production on fri oct 1 10:24:02 2010

Copyright (c) 1982, 2007, Oracle. All rights reserved.

2010/10/01:10:24:02 * Starting OIDREPLD against <REPLICA_HOSTNAME>:<PORT>...
2010/10/01:10:24:14 * Starting scheduler...
2010/10/01:10:24:14 * Start to BootStrap from supplier=<MASTER_HOSTNAME>_<MASTER_SID> to consumer=<REPLICA_HOSTNAME>_<REPLICA_SID>
2010/10/01:10:24:14 * Replication BOOTSTRAP_ERROR mode detected for replica(<REPLICA_HOSTNAME>_<REPLICA_SID>)

BootStrap Trouble Shooting Tip(s)
OPTION #1: Identify the cause of Bootstrap failure and fix the cause, then
restart bootstrapping by setting consumer replica's
orclreplicastate to BOOTSTRAP mode
OPTION #2: Identify the naming context(s) that are failed to be bootstrapped,
and use oidreconcile tool to reconcile.Then resume replication by
setting consumer replica's orclreplicastate to ONLINE mode
Notes: OIDREPLD is now in BOOTSTRAP_ERROR mode, you'll need to reset consumer
replica's Replica State(orclreplicastate)
Please refer to as the Replication trouble shooting section in OID admin
guide for details
2010/10/01:15:35:11 * osdrepld got shutdown signal. Exiting.
2010/10/01:15:35:12 * OID Replication Server exiting.


No further details about the bootstrap failure is logged in the oidrepld00.log even when stopping and restarting replication server with higher debug level.


However, when the following steps are performed, the debug level on replication server then takes effect:

- Stop replication server on the replica, i.e.:

oidctl connect=<REPLICA_CONNECT_STRING> server=OIDREPLD instance=1 flags="-h <REPLICA_HOSTNAME> -p <PORT>" stop


- Backup and remove the oidrepld00.log.

- Follow documentation steps to set the replica's orclreplicastate to 0 to reinitialize bootstrap:

Oracle Internet Directory Administrator's Guide, 10g Release 2 (10.1.2) B14082-02
    Chapter 25 Oracle Internet Directory Replication Administration
       Example 25-13 Modifying the orclReplicaState Attribute for a Particular Replica

(Note: In the above log case example, the value for <unique_replicaID> would be <REPLICA_HOSTNAME>_<REPLICA_SID>.)

- Restart replication server on the replica with replication-specific debug level, i.e.:

oidctl connect=<REPLICA_CONNECT_STRING> server=OIDREPLD instance=1 flags="-h <REPLICA_HOSTNAME> -p <PORT> -d 4194304" start


- Allow the bootstrap error to reoccur, and the oidrepld00.log should now log more detail about the bootstrap failure(s).


For this case scenario, the oidrepld00.log then shows bootstrap (sync) completed for some contexts, i.e.:

2010/10/06:10:25:28 * gslrbssSyncDIT:Sync done successfully for namingctx: cn=oraclecontext, 687 entries matched

 

2010/10/06:10:25:28 * gslrbssSyncDIT:Sync done successfully for namingctx: cn=server configurations, 5 entries matched

 

2010/10/06:10:30:29 * gslrbssSyncDIT:Sync done successfully for namingctx: cn=oracleschemaversion, 11 entries matched



But fails for one context, i.e.:

2010/10/06:10:30:29 * gslrbssSyncDIT:Sync failed for namingctx: dc=com, only 15322 entries retrieved


And the log later on reports again:

2010/10/06:10:30:29 * gslrbsbBootStrap: Failure occured when bootstrapping 1 out of 4 namingcontext(s) from the supplier
BootStrap Trouble Shooting Tip(s)
OPTION #1: Identify the cause of Bootstrap failure and fix the cause, then
restart bootstrapping by setting consumer replica's
orclreplicastate to BOOTSTRAP mode
OPTION #2: Identify the naming context(s) that are failed to be bootstrapped,
and use oidreconcile tool to reconcile.Then resume replication by
setting consumer replica's orclreplicastate to ONLINE mode
Notes: OIDREPLD is now in BOOTSTRAP_ERROR mode, you'll need to reset consumer
replica's Replica State(orclreplicastate)
Please refer to as the Replication trouble shooting section in OID admin
guide for details

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
Cause
Solution


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