Fwd: BTS index on HDR Secondary usable?

Thanks Mike! So there's the proof that I didn't RTFM closely enough ;) BTS + HDR don't mix. ---------- Forwarded message ---------- From: Michael Lowe Date: Thu, Oct 16, 2008 at 2:02 PM Subject: Re: BTS index on HDR Secondary usable? BTS is not supported in any replication environment. >From the reference manual (IBM Informix Database Extensions User's Guide): Replication is not supported: Enterprise Replication and high availability solutions (High-Availability Data Replication, Remote Standalone secondary servers, and Shared Disk secondary servers). Regards, Mike Mike Lowe Education Planning and Development IBM Information Management informix-list-bounces@iiug.org wrote on 10/16/2008 11:45:49 AM: > On Thu, Oct 16, 2008 at 12:14 PM, Jim Tranny <jimtranny@gmail.com> wrote: > > 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. > > > > So I've tried it and as expected the secondary's copy of the extspace > didn't get updated when updates are made to the indexed column and > thus the BTS index on the secondary is now out of sync. > > So are we seeing a bug here or is this expected behaviour? We can use > a BTS index on a secondary (so long as we copy over the extspace), but > it won't get created or updated automatically. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list