Are $= And $\ Supposed To Supersede Each Other? (Doc ID 2759003.1)

Last updated on MARCH 09, 2021

Applies to:

Goal

Are $= and $\ supposed to supersede each other?

The goal is to have a mapping table do an LDAP lookup.
The value used in the query needs to be shifted to lower case (because the attribute is unfortunately defined as case sensitive, so it is preferred to achieve case-insensitivity by making sure the values are stored in lower case and shifting the query value to lower case) and, it is noted that $= ... $_  (refer here: https://docs.oracle.com/communications/F15020_01/doc.810/f15150.pdf#page=774&zoom=auto,-116,646 )  should always be around such data fed to an LDAP query.

If it is coded as `$=$\$4$_`, the shift to lower case can be observed in the debug log, but not the LDAP quoting.
If it is switched to `$\$=$4$_`, the LDAP quoting is observed, but upper case characters remain upper case.

Here is the mapping table that is being used as a workaround:

This part:

11:00:48.10:   Entry #1 matched, pattern "*", template "$C$\$=$0$_", match #0.
11:00:48.10:   New target "aB%5C2A"

shows that the LDAP quoting of $= was effective. The "*" was translated to %5C2A,
but the $\ was not effective, because the "B" remained a "B" instead of being shifted to "b".

Are $= and $\ supposed to supersede each other?
 

Solution

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