× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We use Mimix to replicate data from our 'Primary' box to our 'Secondary'
box. We perform our backups nightly on the Secondary box. Once a quarter
we do a 'switch' from our primary to our secondary to test fail over and
run over the weekend on that.

What level of Mimix are they on?
LAKEVIEW/WRKPRD
We stay pretty current and that command returns:
Installation Installed
Product Library Version
License Manager LAKEVIEW 7.1.19.00
MIMIX Professional MIMIX 7.1.19.00

What level of the OS are they on on their source system?
What level of the OS are they on on their target system?

Is WRKPTFGRP current on their source system?
Is WRKPTFGRP current on their target system?


I ran this command:
WRKAUD
and I see a pletora of audits. Ours are all clean right now...
Audit Audit ---------Definition--------- Object Objects
Status Rule DG Name System 1 System 2 Diff Selected
*NODIFF #FILDTA BPCS_GDI GDIHQ GDIHQ2 0 *PTY
*NODIFF #IFSATR BPCS_GDI GDIHQ GDIHQ2 0 *PTY
*NODIFF #MBRRCDCNT BPCS_GDI GDIHQ GDIHQ2 0 *PTY
*NODIFF #OBJATR BPCS_GDI GDIHQ GDIHQ2 0 *PTY
*NODIFF #DGFE IFS GDIHQ GDIHQ2 0 *ALL
*NODIFF #DLOATR IFS GDIHQ GDIHQ2 0 *PTY
*NODIFF #FILATR IFS GDIHQ GDIHQ2 0 *PTY
*NODIFF #FILATRMBR IFS GDIHQ GDIHQ2 0 *PTY
*NODIFF #FILDTA IFS GDIHQ GDIHQ2 0 *PTY
*NODIFF #IFSATR IFS GDIHQ GDIHQ2 0 *PTY
More...

But let's look at the *OBJATR audit. So I'll use "14=Audited objects" on
it.
Audited Object
Status Type Name
*EQ *DTAQ DGECAMF/AGAL184002
*EQ *DTAQ DGECAMF/AGAL184032
*EQ *DTAQ DGECAMF/AGAL184111

There may be options in there to ask it why does it think it's not equal.
It might be easier to check if I had some that were out of sync.

The reason that I asked about the levels of Mimix, OS and PTF's is that
often a problem can be resolved by keeping current.
Take this wild example, some obscure thing changes an attribute on the
object on their source system. This attribute change is not recorded in a
file journal entry against the object. It's also not recorded as an
object audit entry change in the system object audit journal. Odd, but
perhaps possible in a system which believes "if it ain't broke don't fix
it" and has fallen behind on OS and PTFs.

On a related note, does your join span libraries? Maybe one of the tables
is in a library that is not 'mimixed' over to the target. When it tries
to add the member it can't.

Anyone running Mimix had better be under Mimix support. They should
easily tell you what attribute on that object is being flagged and give
you some suggestions as to what to do to resolve the situation.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.