Thanks Jim. On Jan 21, 11:30 am, Jim Idle <[email protected]> wrote: > jlogdup wrote:Hello Jbase group. On my company we are using Transaction > Journaling to replicate from Machine1 to machine2 using the command: jlogdup > -v -m 1000000000 input set=current terminate=wait output set=database > rename=e:,z: where z: is a mapping of drive e: in Machine2 Yesterday I ran on > Machine1: create-index File1 index1 by-ar id.umber Looking in jbase.com I > read that Index definitions are not journaled or replicated, so I ran the > same command on Machine2: create-index File1 index1 by-ar id.umber The index > was created successfully. Today I notice that when I add a record on > Machine1,File1 it is replicated on Machine2,File1 but the index on Machine2 > is not updated. I tested for other files whose index definitions were set > before the replication using jlogdup was started , and those indexes have > been updated ok. Should I stop the process jlogdup and restart it again to > have the index in File1 updated? or how can I force it without stop jlogdup > ?Once the file has been opened, any such changes are ignored. It would be > incredibly inefficient to check for the addition of indexes and triggers > before every operation on an open file. Hence you must restart the process. > You can build indexes online but you cannot add indexes online. > Realistically, you are not likely to be adding indexes to a file that is > being used by the application on a system that is live replicating. > Jim
--~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
