Page 2 of 2

Unstopable dowalk

Posted: Tue Nov 06, 2007 3:44 pm
by mark
Very odd, instead of
Name='SSc_walking'
try
Name matches '%walking%'

Or try reversing the Name and Profile clauses (Name first, Profile second).

Unstopable dowalk

Posted: Wed Nov 07, 2007 9:12 am
by weixel
OK, using the matches operator ("select Name,String from options where Profile='profilename' and Name matches '%walking%'") returns the data. Unfortunately, if I try to use that operator in a delete statement ("delete from options where Profile='profilename' and Name matches '%walking%'"), I get the following errors:

006 Cannot delete value (SSc_walking) from index /INSTALLDIR/texis/testdb/xoptname.btr
006 Cannot delete value (23219) from index /INSTALLDIR/texis/testdb/xoptstr.btr

Unstopable dowalk

Posted: Wed Nov 07, 2007 10:09 am
by mark
Ahah, there's the problem. That index is apparently messed up. That would explain not finding the value. Drop and recreate that index. Let's do a related one as well. Create a file containing the script below. Call it "fixindex" with no extension. Run it with
texis fixindex

<script language=vortex>
<a name=main>
<sql "drop index xoptname"></sql>
<sql "drop index xoptstr"></sql>
<sql "create index xoptname on options(Name)"></sql>
<sql "set max_index_text=128"></sql>
<sql "create index xoptstr on options(String)"></sql>
</a>
</script>

Unstopable dowalk

Posted: Wed Nov 07, 2007 10:12 am
by weixel
Mark,

Do I need to specify the profile for the fixindex script?

Unstopable dowalk

Posted: Wed Nov 07, 2007 11:11 am
by mark
No. The options table contains all profiles and exists in the global database.

Unstopable dowalk

Posted: Wed Nov 07, 2007 11:15 am
by weixel
Ok, ran the script, but it resulted in a Timeout error.

Unstopable dowalk

Posted: Wed Nov 07, 2007 11:43 am
by mark
I guess your options table is rather large. Add
<timeout=-1></timeout>
just below the
<script language=vortex>
line.

Unstopable dowalk

Posted: Wed Nov 07, 2007 11:52 am
by weixel
That's the ticket. Script finished that time.

Now, getting back to the original problem of never-ending walks. Should I try to run a replace walk on this same profile to clean out anything left over from the obviously corrupt walk?

Unstopable dowalk

Posted: Wed Nov 07, 2007 1:04 pm
by mark
Probably not a bad idea.

Unstopable dowalk

Posted: Thu Nov 08, 2007 8:57 am
by weixel
Just as a follow-up: a "new" walk ran smoothly and the profile in question is running better than it has in a long time.

Many thanks for helping to sort this out.