Re: dbms_ldap
- From: rjamya <rjamya@xxxxxxxxx>
- To: ganstadba@xxxxxxxxxxx
- Date: Wed, 3 May 2006 08:21:46 -0400
Thanks Mike,
it is funny since I could specify one of the OU and fetch 3900
entries, drop the OU and I get the error. Finally I have my AD admin
send me a CSV and I have an external table that reads it and ingests.
This solution works for me and AD group, so we are both happy now.
Thanks for the suggestion
Raj
On 4/28/06, Michael McMullen <ganstadba@xxxxxxxxxxx> wrote:
Looks like you're being limited by your ldap server. Ours restricts us to
100 values returned. We have to do the following.
Loop through a table with 36 values. These values consists of all the
letters of the alphabet plus the numbers 0-9. This number or letter is
appended to the first bunch of employeed numbers we are interested in. We
then loop through each of the 36 values 26 times appending a letter of the
alphabet. We then use each one of these as our search against ldap.
Cumbersome and slow and not even guaranteed to bring back less than 100
employees but it's working for now.
Mike
--
----------------------------------------------
Got RAC?
--
http://www.freelists.org/webpage/oracle-l
Other related posts:
- » dbms_ldap
- » Re: dbms_ldap
- » Re: dbms_ldap
Looks like you're being limited by your ldap server. Ours restricts us to 100 values returned. We have to do the following. Loop through a table with 36 values. These values consists of all the letters of the alphabet plus the numbers 0-9. This number or letter is appended to the first bunch of employeed numbers we are interested in. We then loop through each of the 36 values 26 times appending a letter of the alphabet. We then use each one of these as our search against ldap. Cumbersome and slow and not even guaranteed to bring back less than 100 employees but it's working for now.
Mike