Linear Search error message

davidtg · Post by **davidtg** » Thu Jan 19, 2006 6:11 pm

Hi,

I'm getting something I've not seen before:
"115 /search:1611 Query 'xxxx' would require a linear search".

The search script is customized with a radio buttons to allow users to switch databases to search either the profile's db or a main db that indexes several sites. The error shows when switching to the main db.

Oddly we use the same script with several different profiles and only one of the profiles gives the error when switching to the main db. Also all functioned fine and without error until today.

Any thoughts on this issue? Thanks, David

Post by **John** » Thu Jan 19, 2006 8:56 pm

That means that the index on the table is either missing, is not on the right fields, or the search term is not indexable.

davidtg · Post by **davidtg** » Thu Jan 19, 2006 9:24 pm

I'm sure your correct but there is something else going on because I can search the same term on the database without error when Webinator uses a different profile.

Maybe my code to switch databases which is inserted after the standard code gets the profile's info is not so good though it had appeared to work fine until now:

<A Name=init>
....snip....
<IF $depts eq "all">
<$swpr = "sphcm"> 
<sql max=1 "select String db_sphcm from options where Profile=$swpr and Name='SS_db'"></sql> 
<$dbdir = $db_sphcm>
</IF>
<DB = $dbdir>
...snip....

All our profiles use the same above code and all but one seems to switch and search without error on the switch. This error has got me quite stumped. Maybe when the refresh walks happen tonight it will magically go away. David

Post by **John** » Fri Jan 20, 2006 10:17 am

Each profile has its own database and index, so it could be that the one profile is missing an index. You might try running

texis profile=ProfileName dowalk/reindex.txt

to make sure it is indexed. Are there any other messages immediately before or after the linear search message?

davidtg · Post by **davidtg** » Fri Jan 20, 2006 6:56 pm

Let me try to give a bit more info - I've customized our setup a bit in that we've got 6 profiles - 5 departments and 1 main. The 6 profiles search their own databases without error. The main profile walks a superset of sites relative to the 5 other profiles such that I give the option to search their own database or the larger one availabe in the main profile.

We use separate profiles because each department wants their own look and feel search pages. The vortex search script is the same for each profile - only top/bottom html within profile is different.

I'm not seeing any other errors. Why the switch is only affecting one of the profiles is very odd - the search script is the same for all - seems that all should have the same error. Here are two of the links to our department search pages, the top one has the error when you switch to the main database.

http://apps.sphcm.washington.edu/texis/ ... pr=envhlth
http://apps.sphcm.washington.edu/texis/ ... rch?pr=epi

Post by **John** » Fri Jan 20, 2006 9:30 pm

The two things I would suggest would be to print the database before the search actually happens, e.g. in the search function just before the SQL, and after all the init:

<vxinfo db>
<fmt "" $ret>

so it will print in a comment and not affect the output. If they are the same at that point then you could open a tech support ticket and attach the two scripts and we can take a look if anything else looks out of place.

Post by **John** » Fri Jan 20, 2006 9:32 pm

Another option would be instead of that code to have the radiobutton be called pr, which would set the desired profile automatically.

davidtg · Post by **davidtg** » Tue Jan 24, 2006 6:16 pm

Still stuggling with this one.

I don't want to change the profile=pr (look and feel) but allow the profile to search against another profiles database.

This has been working for all but one of the profiles - which is odd - since all the profiles use the same script file.

I'll work on it some more but may go ahead and start a ticket on this one.

Thanks, David

davidtg · Post by **davidtg** » Wed Jan 25, 2006 3:23 pm

I've got the error fixed but perhaps only temporarily -

I cloned the problem profile and was able to recreate the error so something in the actual profile seems to be causing the linear search error.

I then cloned a new profile from one of our other ones without the linear query error - duplicated the settings from the problem profile - but no error now.

It be nice to know what possible setting in the profile could create the linear query error when quering against a different DB.

Post by **John** » Wed Jan 25, 2006 3:52 pm

The main ones would be Word Definition or Index Fields.