BTS index on HDR Secondary usable?
Posted in 2008
Jim Tranny found that on IDS 11.50.FC2 (Linux) a Basic Text Search (BTS/CLucene) index created on an HDR primary doesn't actually exist on the secondary: dbschema shows it, but queries fail with "(BTS92) - bts error - CLucene index does not exist". Toggling LOG_INDEX_BUILDS (0 or 1) didn't help, though the log showed the index being 'received'. Suggestions: the index lives in an extspace outside the engine, so it isn't replicated; one poster advised opening a PMR as a likely bug. Manually copying the extspace to the secondary (with activity stopped) made it work, but whether later updates propagate was left untested — no real resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: High Availability & Replication
Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
created a BTS (Basic Text Search) index on the HDR primary, expecting
to see it being created on the HDR secondary as well but the index did
not get created. I can see that the index 'should' have been created
since running dbschema on the secondary shows the index but when I try
to use the index I get: (BTS92) - bts error - CLucene index does not
exist.
I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
Does anyone have any ideas on how to get a BTS index working on the
secondary?
Thanks.
hmmm sorry no answer, however in the past building an index on verity
or excalibur
was done unlogged in an sbspace.
afaikr this was the behaviour which could not be changed.
Therefor unlogged it could not be replicated!!!!!
sounds like this is also true for BTS,
May be somewhere hidden in the release notes it may state how to build
an index
logged so the index is sent to the secondary too.
Superboer.
On 16 okt, 15:25, "Jim Tranny" <jimtra...@gmail.com> wrote:
> Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
> created a BTS (Basic Text Search) index on the HDR primary, expecting
> to see it being created on the HDR secondary as well but the index did
> not get created. I can see that the index 'should' have been created
> since running dbschema on the secondary shows the index but when I try
> to use the index I get: (BTS92) - bts error - CLucene index does not
> exist.
>
> I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
> Does anyone have any ideas on how to get a BTS index working on the
> secondary?
>
> Thanks.
Thanks Superboer, I checked the release notes and I see no hints. The
BTS index is stored in an extspace, but the funny thing is that I
dabbled with this back on V10 a couple of years ago and I could have
sworn that I saw that extspace getting filled up on the secondary
(which isn't being done in V11.50), but my memory could be failing me
here.
On Thu, Oct 16, 2008 at 10:31 AM, Superboer <superboer7@t-online.de> wrote:
> hmmm sorry no answer, however in the past building an index on verity
> or excalibur
> was done unlogged in an sbspace.
>
> afaikr this was the behaviour which could not be changed.
>
> Therefor unlogged it could not be replicated!!!!!
> sounds like this is also true for BTS,
>
> May be somewhere hidden in the release notes it may state how to build
> an index
> logged so the index is sent to the secondary too.
>
>
> Superboer.
>
> On 16 okt, 15:25, "Jim Tranny" <jimtra...@gmail.com> wrote:
>> Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
>> created a BTS (Basic Text Search) index on the HDR primary, expecting
>> to see it being created on the HDR secondary as well but the index did
>> not get created. I can see that the index 'should' have been created
>> since running dbschema on the secondary shows the index but when I try
>> to use the index I get: (BTS92) - bts error - CLucene index does not
>> exist.
>>
>> I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
>> Does anyone have any ideas on how to get a BTS index working on the
>> secondary?
>>
>> Thanks.
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
Hello Jim,
if there are really no hints then i would open a case with ibm/
informix
this sounds like a bug; or could be exploited as one since it does not
say anywhere
that you are not allowed to use BTS with HDR.
Superboer.
On 16 okt, 17:01, "Jim Tranny" <jimtra...@gmail.com> wrote:
> Thanks Superboer, I checked the release notes and I see no hints. The
> BTS index is stored in an extspace, but the funny thing is that I
> dabbled with this back on V10 a couple of years ago and I could have
> sworn that I saw that extspace getting filled up on the secondary
> (which isn't being done in V11.50), but my memory could be failing me
> here.
>
> On Thu, Oct 16, 2008 at 10:31 AM, Superboer <superbo...@t-online.de> wrote:
> > hmmm sorry no answer, however in the past building an index on verity
> > or excalibur
> > was done unlogged in an sbspace.
>
> > afaikr this was the behaviour which could not be changed.
>
> > Therefor unlogged it could not be replicated!!!!!
> > sounds like this is also true for BTS,
>
> > May be somewhere hidden in the release notes it may state how to build
> > an index
> > logged so the index is sent to the secondary too.
>
> > Superboer.
>
> > On 16 okt, 15:25, "Jim Tranny" <jimtra...@gmail.com> wrote:
> >> Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
> >> created a BTS (Basic Text Search) index on the HDR primary, expecting
> >> to see it being created on the HDR secondary as well but the index did
> >> not get created. I can see that the index 'should' have been created
> >> since running dbschema on the secondary shows the index but when I try
> >> to use the index I get: (BTS92) - bts error - CLucene index does not
> >> exist.
>
> >> I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
> >> Does anyone have any ideas on how to get a BTS index working on the
> >> secondary?
>
> >> Thanks.
>
> > _______________________________________________
> > Informix-list mailing list
> > Informix-l...@iiug.org
> >http://www.iiug.org/mailman/listinfo/informix-list
Madison,
any comments???
Superboer.
On 16 okt, 17:01, "Jim Tranny" <jimtra...@gmail.com> wrote:
> Thanks Superboer, I checked the release notes and I see no hints. The
> BTS index is stored in an extspace, but the funny thing is that I
> dabbled with this back on V10 a couple of years ago and I could have
> sworn that I saw that extspace getting filled up on the secondary
> (which isn't being done in V11.50), but my memory could be failing me
> here.
>
> On Thu, Oct 16, 2008 at 10:31 AM, Superboer <superbo...@t-online.de> wrote:
> > hmmm sorry no answer, however in the past building an index on verity
> > or excalibur
> > was done unlogged in an sbspace.
>
> > afaikr this was the behaviour which could not be changed.
>
> > Therefor unlogged it could not be replicated!!!!!
> > sounds like this is also true for BTS,
>
> > May be somewhere hidden in the release notes it may state how to build
> > an index
> > logged so the index is sent to the secondary too.
>
> > Superboer.
>
> > On 16 okt, 15:25, "Jim Tranny" <jimtra...@gmail.com> wrote:
> >> Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
> >> created a BTS (Basic Text Search) index on the HDR primary, expecting
> >> to see it being created on the HDR secondary as well but the index did
> >> not get created. I can see that the index 'should' have been created
> >> since running dbschema on the secondary shows the index but when I try
> >> to use the index I get: (BTS92) - bts error - CLucene index does not
> >> exist.
>
> >> I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
> >> Does anyone have any ideas on how to get a BTS index working on the
> >> secondary?
>
> >> Thanks.
>
> > _______________________________________________
> > Informix-list mailing list
> > Informix-l...@iiug.org
> >http://www.iiug.org/mailman/listinfo/informix-list
Jim Tranny wrote:
> Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
> created a BTS (Basic Text Search) index on the HDR primary, expecting
> to see it being created on the HDR secondary as well but the index did
> not get created. I can see that the index 'should' have been created
> since running dbschema on the secondary shows the index but when I try
> to use the index I get: (BTS92) - bts error - CLucene index does not
> exist.
>
> I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
> Does anyone have any ideas on how to get a BTS index working on the
> secondary?
>
> Thanks.
As the extspace is external to the engine, is it "in-sync" on the secondary machine as regards the primary??
I think you may need to :
Shut the engine down (or stop all insert activity)
Copy across the extspace
Start the engine
Do you still get the error?
On Thu, Oct 16, 2008 at 11:58 AM, TBP <theBP@usenet-news.net> wrote:
> Jim Tranny wrote:
>> Has anyone else seen this? We're using IDS 11.50.FC2 (Linux). I
>> created a BTS (Basic Text Search) index on the HDR primary, expecting
>> to see it being created on the HDR secondary as well but the index did
>> not get created. I can see that the index 'should' have been created
>> since running dbschema on the secondary shows the index but when I try
>> to use the index I get: (BTS92) - bts error - CLucene index does not
>> exist.
>>
>> I have tried setting LOG_INDEX_BUILDS to 0 or 1 but that didn't help.
>> Does anyone have any ideas on how to get a BTS index working on the
>> secondary?
>>
>> Thanks.
>
> As the extspace is external to the engine, is it "in-sync" on the secondary machine as regards the primary??
>
> I think you may need to :
>
> Shut the engine down (or stop all insert activity)
> Copy across the extspace
> Start the engine
>
> Do you still get the error?
> _______________________________________________
Yes, that does work. But what will happen if there are changes to the
indexed column? I doubt that the index on the secondary will get
updated. I'll give it a shot to see what happens with the updates.
When LOG_INDEX_BUILDS is set to 0 I can see that the build command is
being sent to the secondary:
11:24:59 DR: Receiving index mydb:"auser".atable#idx_bts : Started
11:24:59 DR: Receiving index mydb:"auser".atable#idx_bts : Completed.
I find it strange that it's not issuing the build commands to the datablade.