MIMIX Replication Oddities

15 pts.
Tags:
MIMIX
What could explain why random objects have different object sizes on replicated system using MIMIX? Creation date/time and source are all identical? Any explanations for this?


Software/Hardware used:
AS400; MIMIX
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Splat
    In between meal snacking?

    Seriously though, how great are the differences?  If they're not substantial it might depend on how the object is distributed across the disks.

    If files have a larger size on the primary than on the backup I'd look into the number of deleted records on the primary version.
    12,915 pointsBadges:
    report
  • LBorders
    I had to laugh, no I wasn't bored or snacking :) --- I didn't think about the disk distribution as a reason but that sounds the most logical. Some objects are bigger on the source and some are bigger on the target. I've spot checked the objects and they have the same number of records, including deleted records, the same compile date/time, same source, same operating version, same compression features. It just doesn't make logical sense that they are different. After someone raised the concern that there were mirroring problems, I've done this research. All in all, I think everything is okay with the random spot checking that I've done. I would just like to add a logical explanation for the size difference.
    15 pointsBadges:
    report
  • Splat
    What's the difference as a percentage?  If it's low single digits I wouldn't be overly concerned.
    12,915 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: