Bug 693519 - cannot use localized matching rules
cannot use localized matching rules
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Rich Megginson
Chandrasekar Kannan
: screened
Depends On: 693451
Blocks: 639035 389_1.2.8
  Show dependency treegraph
Reported: 2011-04-04 17:10 EDT by Rich Megginson
Modified: 2015-01-04 18:47 EST (History)
5 users (show)

See Also:
Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 693451
Last Closed: 2011-05-19 08:43:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rich Megginson 2011-04-04 17:10:44 EDT
+++ This bug was initially created as a clone of Bug #693451 +++

configuring an index entry to generate localized matching rules using the collation plugin does not work

nsMatchingRule: 2.16.840.1.113730.

after adding this, and re-indexing/re-importing, the description.db4 index does not contain entries like

--- Additional comment from rmeggins@redhat.com on 2011-04-04 17:10:12 EDT ---

Created attachment 489856 [details]
Comment 4 Amita Sharma 2011-04-26 08:16:29 EDT
Hi Rich,

I am testing this bug, followed below steps :

1. [root@rheltest amsharma]# ldapmodify -a -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=description,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
> nsMatchingRule: 2.16.840.1.113730.
> nsIndexType: eq
> nsIndexType: pres
> nsIndexType: sub
> nsSystemIndex: false
> objectClass: top
> objectClass: nsIndex
> cn: description
adding new entry "cn=description,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config"

2. [root@rheltest slapd-rheltest]# ./db2index.pl -D "cn=Directory Manager" -w Secret123 -n userRoot -t description
adding new entry "cn=db2index_2011_4_26_16_29_19, cn=index, cn=tasks, cn=config"

3. [root@rheltest userRoot]# db_dump  description.db4

Result : I am not able to grep 2.16.840.1.113730. from description.db4.

Please guide here.

Comment 5 Rich Megginson 2011-04-26 09:11:44 EDT
Use dbscan instead of db_dump
dbscan -f description.db4 | grep \^\:2.16.840.1.113730.\:
Comment 6 Amita Sharma 2011-04-26 09:18:36 EDT
Thanks for the quick response Rich.

[root@rheltest userRoot]# dbscan -f description.db4 | grep \^\:2.16.840.1.113730.\:

Marking the bug as VERIFIED.
Comment 7 errata-xmlrpc 2011-05-19 08:43:01 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.