search cancel

How to fix Tombstones related error messages?


Article ID: 20782


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On



After importing an smdif file, these errors might be found in the SiteMinder and directory logs.

Smps log :

 [CA.XPS:LDAP0014][ERROR] Error occurred during "Search" for "Tombstones", text: Operations error     
 [CA.XPS:XPSIO040][ERROR] Delete of Tombstones failed. 

Corresponding LDAP error log:

 [01/Apr/2011:12:45:24 +1100] - ERROR<21006> - conn=-1 op=-1 msgId=-1 - could not open index xpsTombstone for range query     
 [01/Apr/2011:12:45:24 +1100] - ERROR<20775> - Backend Database - conn=4 op=1075 msgId=1076 - database error 2 



SiteMinder Policy Server: R12 SP3

Policy store: Oracle Directory Server Enterprise Edition (formerly Sun Directory Server Enterprise Edition) 6.3.1

Policy server OS: Windows Server 2003 SP2



This error occurs because the index for xpsTombstone field in LDAP directory is not created. To fix it, you need to regenerate the index.

  1. Log onto Java System Directory Service Control Center and select Directory Servers tab

    <Please see attached file for image>

    Figure 1
  2. Select the directory that is the policy store

    <Please see attached file for image>

    Figure 2
  3. Select Suffixes tab

    <Please see attached file for image>

    Figure 3
  4. Tick the suffix that starts with ou=Netegrity, and select Regeneration Indexes from the drop-down list

    <Please see attached file for image>

    Figure 4
  5. An Index Regeneration window will open. Click on Add All button to select all attributes to be re-indexed. You may choose xpsTombstone only, but the options used in this case ,were to re-build all indexes.

    <Please see attached file for image>

    Figure 5
  6. Click OK

    <Please see attached file for image>

    Figure 6
  7. The indexing will start running.

    <Please see attached file for image>

    Figure 7
  8. And finish

    <Please see attached file for image>

    Figure 8
  9. Restart the policy server and verify the error no longer happens.


Component: SMPLC


1558717014375000020782_sktwi1f5rjvs16ue5.gif get_app
1558717011989000020782_sktwi1f5rjvs16ue4.gif get_app
1558717005241000020782_sktwi1f5rjvs16ue3.gif get_app
1558717003132000020782_sktwi1f5rjvs16ue2.gif get_app
1558717001113000020782_sktwi1f5rjvs16ue1.gif get_app
1558716999121000020782_sktwi1f5rjvs16ue0.gif get_app
1558716997176000020782_sktwi1f5rjvs16udz.gif get_app
1558716995094000020782_sktwi1f5rjvs16udy.gif get_app