How to Manually Delete an OID Node from an ASR Based Replicated Environment (DRG) (Doc ID 1148595.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 10.1.2 to 10.1.2.3 [Release 10gR2]
Information in this document applies to any platform.

Symptoms

1.  The command line tool:  remtool -delnode hangs


2.  If you run remtool -asrverify you get the following output:

ASR SETUP ERROR/WARNING:
ONBHF09.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto04_odsac04".

ASR SETUP ERROR/WARNING:
ONBHF09.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto05_odsac05".

ASR SETUP ERROR/WARNING:
ONBHF09.ORACLE.COM : Replication agreement entry has invalid hostname "neyftwspo01_spsoid1".

ASR SETUP ERROR/WARNING:
ODSAC06.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto04_odsac04".

ASR SETUP ERROR/WARNING:
ODSAC06.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto05_odsac05".

ASR SETUP ERROR/WARNING:
ODSAC06.ORACLE.COM : Replication agreement entry has invalid hostname "neyftwspo01_spsoid1".

ASR SETUP ERROR/WARNING:
ONBHF12.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto04_odsac04".

ASR SETUP ERROR/WARNING:
ONBHF12.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto05_odsac05".

ASR SETUP ERROR/WARNING:
ONBHF12.ORACLE.COM : Replication agreement entry has invalid hostname "neyftwspo01_spsoid1".

ASR SETUP ERROR/WARNING:
ONBHF14.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto04_odsac04".

ASR SETUP ERROR/WARNING:
ONBHF14.ORACLE.COM : Replication agreement entry has invalid hostname "usacpicnto05_odsac05".

ASR SETUP ERROR/WARNING:
ONBHF14.ORACLE.COM : Replication agreement entry has invalid hostname "neyftwspo01_spsoid1".
------------------------------------------------------------------------------

3. "From database prespective, LDAP_REP group had been removed"
- dba_repgroup and dba_objects do not show anything to the removed replicas (therefore the -delnode DID do a partial clean up)

- ldapsearch to "orclagreementid=000001,cn=replication configuration" show the old replication information.

- running asrverify which kicks in below sql ( SELECT entryid, nvl(attrval, '<NULL>') ab, attrkind, attrver FROM ods.ds_attrstore WHERE attrname = 'orcldirreplgroupdsas' AND entryid IN (SELECT entryid FROM ods.ct_dn WHERE rdn = 'orclagreementid=000001' AND parentdn = (select attrval||',' from ods.ds_attrstore where entryid = 1 and attrname = 'orclreplagreements') ;
shows the information of the old replica.

During the db copy procedure in non-prod has shown that remtool -addnode tries to insert the entries into the ods.ds_attrstore store which will fail since entries are already there.


4.  Also, the ods_chg_stat from other nodes still contains entries from the deleted nodes.

Changes

This is a OID release 10.1.2.1 DRG comprised of 3 nodes in New York and 3 nodes in Sacremento, CA.

The data is around 26 million entries.

Generally nodes in the DRG are built using the Database Copy method.

CURRENT ISSUE
=============

1. TWO of the nodes in Sacramento crashed and are in the process of being rebuilt afterwhich, will need to rerun remtool -addnode with replica state set to value = 6.

In preparation of doing so, from the MDS node in NewYork:

The remtool -delnode command was run, at such time it HUNG due to bug 4192400 where you cannot run -delnode on a node that it CANNOT contact.   This only occurs for release 10.1.2.1.  There is no patch for 10.1.2.1.


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