OpenLDAP / Oracle LDAP: naming collision for ldap_set_option/ldap_get_option

[Peter Steiert <psteiert@netsys-it.de>]

Hello alltogether,

i'm not quite sure whether this list is the correct place to discuss the 
following topic but I hope so.

I recently had an issue after compiling and running freeradius with 
oracle and openldap support.

The error is as following:
Thu May 12 10:06:42 2011 : Debug:   [ldap] (re)connect to
	ldaps.localnet.local:636, authentication 0
Thu May 12 10:06:42 2011 : Error:   [ldap] Could not set
	LDAP_OPT_NETWORK_TIMEOUT 1: Bad parameter to an ldap routine
Thu May 12 10:06:42 2011 : Debug:   [ldap] setting TLS mode to 1
Thu May 12 10:06:42 2011 : Error:   [ldap] could not set LDAP_OPT_X_TLS
	option Bad parameter to an ldap routine:
Thu May 12 10:06:42 2011 : Debug:   [ldap] bind as cn=RADIUSADMIN,
	c=DE/PASSWORD to ldaps.localnet.local:636
Thu May 12 10:06:42 2011 : Debug:   [ldap] waiting for bind result ...
Thu May 12 10:06:42 2011 : Debug:   [ldap] ldap_result()
Thu May 12 10:06:42 2011 : Error:   [ldap] cn=RADIUSADMIN, c=DE bind to
 	ldaps.localnet.local:636 failed: Can't contact LDAP server
sgslufread: Hard error on read, OS error = 32
sgslufread: Hard error on read, OS error = 32

After longer investigation i found out that the routines:
	ldap_set_option
	ldap_get_option

are defined in OpenLDAP/ldap.h as well as in Oracle/ldap.h
and are locatable in Oraclelib/libclntsh.so.11.1 as well as in
OpenLDAP/libldap_r.so.

So the ld-loader is sometimes offering the oracle code to the client and 
sometime the openldap code. This causes failure in the application.

Now my question to the community here:
Is there a global naming definiton about these routines to avoid such a 
conflict?
Wouldn't it be better if Oracle would use it's own namespace convention 
as well as OpenLDAP?


Kind regards
Peter

If the list is wrong please tell me the correct one to discuss this topic.
Btw: We did a workaround by using the LD_PRELOAD path :)