This document describes how to fix Cisco Agent Desktop (CAD) Lightweight Directory Access Protocol (LDAP) Database when corrupt on both sides.
Contributed by Nebojsa Zdravkovic and Dan Lazich and Edited by Manoj Srinivas, Cisco TAC Engineers.
Cisco recommends you have the knowledge on these topics:
Cisco Unified Contact Center Enterprise (UCCE)
CAD LDAP Database
The information in this document was created from the devices in a specific production environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
In this environment, agents were unable to log in to CAD and none of the CAD services could connect to LDAP.
You will see Slapd bouncing with this error:
DEBUG [0x530] parse_acl: config_back_db_open: line 0: warning: cannot assess the validity of the ACL scope within backend naming context
DEBUG [0x530] bdb_db_open: bdb_db_open: "o=Spanlink Communications"
DEBUG [0x530] bdb_db_open: bdb_db_open: database "o=Spanlink Communications" cannot be opened, err 22. Restore from backup!DEBUG [0x530][0x530] bdb_errcall: bdb(o=Spanlink Communications): txn_checkpoint interface requires an environment configured for the transaction subsystem
DEBUG [0x530] bdb_db_close: bdb_db_close: database "o=Spanlink Communications": txn_checkpoint failed: Invalid argument (22).
DEBUG [0x530] backend_startup_one: backend_startup_one (type=bdb, suffix="o=Spanlink Communications"): bi_db_open failed! (22)
This indicates LDAP database which holds all of the CAD configuration data necessary for agent log ins is corrupt. LDAP Recovery procedure described in CAD troubleshooting guide are not applicable here as there is no good LDAP DB available.
It is still possible to recover the data by this procedure though database on both sides are corrupt.
Since both databases are corrupt, you can start from any side. Steps below assume that side A is chosen for repair first. Before executing these steps, ensure slapd tracing is set to THRESHOLD=OFF, under ...Desktop\Config\slapd.cfg.
Step 1. On side A PG, stop the Cisco LDAP Monitor Service.
Step 2. Open a command window and change directories to ...Cisco\Desktop\bin (the drive and exact location of this directory depends on where the services were installed).
Step 3. Rename ...Cisco\Desktop\database folder to ...Cisco\Desktop\old_database.
Step 4. Create a new folder called ...Cisco\Desktop\database.
Step 5. Copy DB_CONFIG and all files with a *.dat extension from the old_database folder to the new database folder.
Step 6. Copy latest ldif file from ..\Desktop\ldap_archive to ..\Desktop\bin and rename it to backup.ldif
Step 7. In the database folder, create an empty file called rep.log.
Step 8. Open a command window and change directories to ...Cisco\Desktop\bin
Type the following command and press Enter.
slapadd -f slapd.conf -l backup.ldif -c
Step 9. You must see a progress indicator while slapadd is running. Wait until it completes.
Step 10. Start LDAP Monitor service
Step 11. Perform the same steps on side B.
Step 12. When complete, break directory replication in postinstall and recreate it
Step 13. Restart CAD services on side B.
Other possible scenarios are covered in CAD Troubleshooting Guide: