Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issue while searching document only with its description

Status
Not open for further replies.

vino29

Technical User
May 18, 2015
1
Hi,

I'm searching for a particular document in Livelink with its description only and it is not coming in search results. I would like to know how to find/troubleshoot these type of issues in Livelink. I know only the description of the document and don't have the dataid of it and I'm sure that it is already indexed as there is no backlog in Dtreenotify and the document type is valid mimetype for Indexing.
 
Frustrated as it seems old livelink systems 971,10 all do not offer any real ways to debug things.Extremely new livelink servers such as 10.5 gives you tools as well as insight on if the indexing ran into a error etc.The typical protocol for your sitaution is if you kind of know the dataid you can go to the dataid and put a comment in and the sytem will re-index and 9 out of 10 it would work.Like wise one could re-send the dataids into dtreenotify based on a date range,or a ollections search.That si if you do not want to go to OT in many cases they might ask you to do what I have done here.
Code:
MS SQL:
INSERT INTO DTreeNotify ( NType, DataID, VersionNum, OwnerID, Subtype ) SELECT '7', DataID, VersionNum, OwnerID, Subtype FROM DTree WHERE ModifyDate > '2015-05-18'

Oracle:
INSERT INTO DTreeNotify ( NID, NType, DataID, VersionNum,OwnerID, Subtype ) SELECT DTreeNotifySequence.NextVal,'7', DataID, VersionNum, OwnerID, Subtype FROM DTree WHERE ModifyDate > '18-May-2015'
Not many people know but livelink uses a API that is blackboxed to us users,it looks like livelink code is doing the search which is true as well,but the code lines are completely separate.Most problems are due to FileSystem locks as things like AV checks,FileSystem breaks in Tcp/IP etc happen so the search sytem will throw an error.In most companies nobody pays any attention to search related errors so many of the objects even though the software makes an effort to tell the concerned .OT made the search system exactly like a database system albeit it is propretary,but if your db is down somebody is gonna notice,in case of livelink search if you are pro active you can,also you can do things like above which is reactive.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top