Our SCHEMA.NSF is growing out of control. It has over 1 million documents in it. It takes the server ~30 minutes to come up after a shutdown and this is because of the SCHEMA.Even if I remove the LDAP task from the notes.ini and delete SCHEMA.NSF the server recreates it and hangs until it is complete. I think it is getting it from our hub server which owns the address book. Does anyone know why it continues to grow and how to stop it?
Also, do I need to run the Domino LDAP service on any of our domain servers if we are not doing any LDAP lookups to Domino address books? We are doing all LDAP lookups to a seperate LDAP server specified in directory assistance.
If you are not actively servicing up LDAP, you do not need to run the LDAP task - if you are doing a remote look-up via directory assistance only then the task is a waste of resources.As to the schema.nsf: what are all those documents? replication conflicts? new documents? You will likely have to either re-create the schema file from scratch but you don’t need it if you are not actually running the LDAP service.
Thanks Victor, I didn’t think we need to run the LDAP task. The SCHEMA.nsf is continuing to get new documents at the rate of thousands a day. Our Domino domain has been in existence for over 10 years and this just started happening about a month ago. Our domain stretches across multiple countries and no major changes have been made to our knowledge.Here is a sample.
What I would do to clean up is pretty simple:Stop LDAP on all servers - but especially on the adminP server
remove the schema.nsf from ALL servers
Make sure you have the latest schema.ntf (template) for your adminp server version and make sure there is a replica on all servers domain wide
this way, shoudl you ver need to turn on LDAP again in the futre the schema.nsf will be created new from the correct template version. The only server that should be updating the schema.nsf is the adminp server of your directory and it needs to run LDAP to actually do that. If you find you might have multiple servers updating it (even if you don’t need it) that could be an indication that the ACL of the names.nsf is incorrect on some server out there and it thinks it is the adminp server of your domain. That could be a (possible … not sure) reason for this kind of behavior to have happened it he first place.