Like others in the forum, we are using db.search and also retrieving a profile document in our search results. The same db.search functionality did not return any profile documents on a 5.0.11 server.
Does anyone know if this has been reported to Lotus’ Quality Group and if there is a corresponding technote? I performed a search on www.lotus.com/support for the following keywords: db.search and profile document. Unfortunately, there were no relevant documents. Please let me know if there is a corresponding technote in case I just overlooked it. Thanks for your help!
Subject: RE: db.search and profile documents - Is there a technote for this bug?
I am having the same problem. I have the same exact copy of the data base on a R5 dev server and it works fine. The copy on a R6 dev server pulls in all profile docs along with the docs you would expect. I even tried just using a simple formula such as just SELECT Form = “Person”. The result on the R6 server is to also select profile docs where form is NOT equal to “Person”. If I make a local replica of the R6 database and run on my local (which is an R5 client) it works fine. I also had a similar experience on another database but was able to search a view instead. This time I need to do a dynamic search and cannot run off a view.
Subject: RE: db.search and profile documents - Is there a technote for this bug?
I am having the same problem, but with a slightly different twist: I have 2 production servers, both running R6, both running the same application. A db.Search on one of them always works fine, but a db.search on the other returns different results depending on the release of the client! An R6 client always gets the correct results; an R5.0.11 client will get profile documents in addition to the results – and, yes, I’m CERTAIN they are profile documents! Can someone from Lotus/Iris respond?
Subject: RE: db.search and profile documents - Is there a technote for this bug?
I finally found a tech note on this. I also have upgraded to R6 and all is fine on R6, but if run from an R5 client, the problem persists.The technote is 1152867. Here is the info:
Abstract
If the search method is involked from a database other than the one it is searching it will return profile documents even if they do not match the search criteria.
This is not the case in ND6. Therefore the fix is an upgrade to 6 and the workaround is to loop through all the documents in the collection created by the search and check their ‘isProfile’ value.
Subject: db.search and profile documents - Is there a technote for this bug?
Our server is R7 and this unanticipated result led to a huge problem.
db.search in a scheduled agent is definitely returning our profile documents. The agent does archiving based on a db.search result with a number of criteria. The agent has been sporadically moving the configuration profile document to the archive database, adversely affecting the application.
They are still profile documents in the Archive db, and they have the same name (and no username, same as before). (there are more than one because every time one disappeared, I created another.) There is no form by the name of the profile doc, in the archive’s design.
This occurs in a very large, very active database. (2 GB in 500,000 documents, with 20,000 new ones per day and as many departing for the archives.) Possibly the DB is being compacted in place at the time the agent runs ; perhaps that is part of the scenario that leads to this unexpected result.
Subject: RE: db.search and profile documents - Is there a technote for this bug?
Hi Joe,
I agree with you that theoretically db.search should return only notes documents, but for some strange reason it is also returning profile documents in the collection when the db is on an R6 server. Many others have reported the same issue in this forum.
My question was is Lotus aware of this bug and is there a corresponding technote?