Re: Mimix - not allowed additional views/index on target tables?

Mimix replicates this fine, but at least one of the audits compares
database relations, and will balk at this difference. Then, when you're
switched, Mimix audits will realize that the new target (formerly the
source) doesn't have the indexes it thinks should be there, and will send
them over. There may be a way to have Mimix ignore the situation, but
that's not normal operations, so I'd have to contact Mimix support to
confirm or deny that possibility.






From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/21/2017 09:29 PM
Subject: Mimix - not allowed additional views/index on target
tables?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



All,

Having never used Mimix before, I was surprised to hear that you couldn't
create additional views and/or index on the target machine; any
additional
views/indexes had to be created on the source machine and replicated down.

Given that the target machine is used for reporting, there's lots of
reasons it might need an index that the source doesn't need.

I can understand the limitation if you wanted to have the view/index in
the
same library on the target as it's physical. But I would have thought
that
Mimix wouldn't notice a view/index created in another schema on the target
box.

Any of you Mimix gurus (looking at you Rob ;) want to confirm or deny?

Thanks!
Charles