Missing users

I've got an issue with the driver not pulling all users from NDS.  I've
tested with the sample table that's included with the driver.  This
problem has gotten progressively worse and currently about 2/3 of our
users are not showing up when I pull data using the sample table. 
Initially when I set up our ODBC connection all users were showing up; I'm
pulling from 3 separate containers in which we have users set up.

The only item I've found in comparing users in ConsoleOne that seems to be
on the "Other" tab under attribute "Object Class".  For
those not showing
up Object Class has only 2 items, Unknown & Top; for those that do show up
there are 5 items, User, Organizational Person, Person, Top, &
ndsLoginProperties.

Any help is appreciated...

mjanck wrote:
> I've got an issue with the driver not pulling all users from NDS.  I've
> tested with the sample table that's included with the driver.  This
> problem has gotten progressively worse and currently about 2/3 of our
> users are not showing up when I pull data using the sample table. 
> Initially when I set up our ODBC connection all users were showing up; I'm
> pulling from 3 separate containers in which we have users set up.
> 
> The only item I've found in comparing users in ConsoleOne that seems to be
> on the "Other" tab under attribute "Object Class".  For
those not showing
> up Object Class has only 2 items, Unknown & Top; for those that do show
up
> there are 5 items, User, Organizational Person, Person, Top, &
> ndsLoginProperties.
> 
> Any help is appreciated...

I'd look at this from the other direction. What's causing user objects
to not be objects of class User (etc). The search should only find
objects of the class you specify. If you specify user then no objects
that are not of that class will be in the results and that's operating
as specified. OTOH, I would have expected this behaviour to have a

David Mair wrote:

> mjanck wrote:
> > I've got an issue with the driver not pulling all users from NDS. 
I've
> > tested with the sample table that's included with the driver.  This
> > problem has gotten progressively worse and currently about 2/3 of our
> > users are not showing up when I pull data using the sample table. 
> > Initially when I set up our ODBC connection all users were showing up;
I'm
> > pulling from 3 separate containers in which we have users set up.
> > 
> > The only item I've found in comparing users in ConsoleOne that seems
to be
> > on the "Other" tab under attribute "Object Class".
 For those not showing
> > up Object Class has only 2 items, Unknown & Top; for those that do
show up
> > there are 5 items, User, Organizational Person, Person, Top, &
> > ndsLoginProperties.
> > 
> > Any help is appreciated...

> I'd look at this from the other direction. What's causing user objects
> to not be objects of class User (etc). The search should only find
> objects of the class you specify. If you specify user then no objects
> that are not of that class will be in the results and that's operating
> as specified. OTOH, I would have expected this behaviour to have a
> side-effect on login. What happens when you DSREPAIR?


I checked with our network analysts and they're telling me that we can't
currently run DSREPAIR as it causes the server to reboot.  I guess there's
more going on here than just my ODBC issue.  I'll have to wait for them to
get the server issue figured out then try again.  Thanks for your help.

mjanck wrote:
> David Mair wrote:
> 
> 
>>mjanck wrote:
>>
>>>I've got an issue with the driver not pulling all users from NDS. 
I've
>>>tested with the sample table that's included with the driver.  This
>>>problem has gotten progressively worse and currently about 2/3 of
our
>>>users are not showing up when I pull data using the sample table. 
>>>Initially when I set up our ODBC connection all users were showing
up; I'm
>>>pulling from 3 separate containers in which we have users set up.
>>>
>>>The only item I've found in comparing users in ConsoleOne that seems
to be
>>>on the "Other" tab under attribute "Object
Class".  For those not showing
>>>up Object Class has only 2 items, Unknown & Top; for those that
do show up
>>>there are 5 items, User, Organizational Person, Person, Top, &
>>>ndsLoginProperties.
>>>
>>>Any help is appreciated...
> 
> 
>>I'd look at this from the other direction. What's causing user objects
>>to not be objects of class User (etc). The search should only find
>>objects of the class you specify. If you specify user then no objects
>>that are not of that class will be in the results and that's operating
>>as specified. OTOH, I would have expected this behaviour to have a
>>side-effect on login. What happens when you DSREPAIR?
> 
> 
> 
> I checked with our network analysts and they're telling me that we can't
> currently run DSREPAIR as it causes the server to reboot.  I guess there's
> more going on here than just my ODBC issue.  I'll have to wait for them to
> get the server issue figured out then try again.  Thanks for your help.

If DSRepair causes a server reboot then I have to suspect there is
something significant that needs to be fixed. At this point I'd have to
suggest that continuing to run the participating systems may risk loss
of data or service. Be careful to understand that I am not asserting
that this is the case. However, consider the available facts:

1. Some DS objects that are known to be users are not of the User class
even though other are; and
2. Use of DSREPAIR provokes a server reboot (note that this requires a
triple fault on the CPU and that is extremely rare and pretty much