Jim Tranny said:
> 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.

I'm not sure about this, but I don't think that all UDT indexes get
replicated. Just a guess.

--
Bye now,
Obnoxio

http://obotheclown.blogspot.com/

Obnoxio The Clown wrote:
> Jim Tranny said:
>> 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.
>
> I'm not sure about this, but I don't think that all UDT indexes get
> replicated. Just a guess.
>
Generally, VII indexes do get replicated if they are contained in a
storage space that you can replicate. Since BTS was storing information
in an external (extspace), it could not be replicated. With the next
fixpack of IDS 11.50.xC3 (REAL SOON NOW ;-)), BTS indexes will be able
to be stored in a logged smartblob space that will enable you to
replicate to an HDR secondary, shared disk secondary (SDS), or remote
secondary server (RSS). It will also support DML operations on nodes
that are updatable. The storage in external space will still be
supported on non-HDR systems, as well as HDR primary servers only.
As an added bonus, the XML indexing in BTS has been enhanced to include
the ability to index and search attributes as well as the regular XML tags.

Hope this helps.
--Alan

Alan Caldera
Architect - Informix Datablades
IBM Software Group

On Fri, Oct 17, 2008 at 8:30 AM, Alan Caldera <ajcalder@bellsouth.net> wrote:
> Obnoxio The Clown wrote:
>>
>> Jim Tranny said:
>>>
>>> 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.
>>
>> I'm not sure about this, but I don't think that all UDT indexes get
>> replicated. Just a guess.
>>
> Generally, VII indexes do get replicated if they are contained in a storage
> space that you can replicate. Since BTS was storing information in an
> external (extspace), it could not be replicated. With the next fixpack of
> IDS 11.50.xC3 (REAL SOON NOW ;-)), BTS indexes will be able to be stored in
> a logged smartblob space that will enable you to replicate to an HDR
> secondary, shared disk secondary (SDS), or remote secondary server (RSS). It
> will also support DML operations on nodes that are updatable. The storage in
> external space will still be supported on non-HDR systems, as well as HDR
> primary servers only.
> As an added bonus, the XML indexing in BTS has been enhanced to include the
> ability to index and search attributes as well as the regular XML tags.
>
> Hope this helps.
> --Alan
>
> Alan Caldera
> Architect - Informix Datablades
> IBM Software Group
>

That's great news. So I have the easy but unsupported short term
solution of replicating the extspace by some external method (NFS,
rsync, etc). And that's only until the next fixpack.

Thank you all.

Jim Tranny wrote:
> On Fri, Oct 17, 2008 at 8:30 AM, Alan Caldera <ajcalder@bellsouth.net> wrote:

>
> That's great news. So I have the easy but unsupported short term
> solution of replicating the extspace by some external method (NFS,
> rsync, etc). And that's only until the next fixpack.
>
> Thank you all.

Jim,

The only problem with trying to cross mount the extspace is that the BTS
index updates will not be coordinated with other stuff within the
server. You can think of the log as being something like a clock in
that it shows the changes in an ordered fashion. By having the ordered
events, we are able to coordinate the application of those events on the
secondary.