MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2014

RE: Anybody here know anything about Mimix?



fixed

Operator error, plain and simple. :-)

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Norm Dennis
Sent: Thursday, January 30, 2014 6:25 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Anybody here know anything about Mimix?

Oops, apologies, smartphone not so smart.


Norm Dennis

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of nhdennis@xxxxxxxxxxx
Sent: Friday, 31 January 2014 6:39 AM
To: M.C - Midrange-L
Subject: Re: Anybody here know anything about Mimix?

W
Zach
N
Norm Dennis
Z

----- Reply message -----
From: rob@xxxxxxxxx
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Anybody here know anything about Mimix?
Date: Fri, Jan 31, 2014 05:08


Didn't think about the object locks on the target system.
Normally there shouldn't be any. When we do our backups on the target
system we do quiesce Mimix and restart it upon completion, and time audits
accordingly.
We also do not do queries on our target system. Although I hear that's a
popular option. Get some processor utilization out of your target system by
making it your read only query beast.
Hard to figure out what else could be doing the locking.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: AHoerle@xxxxxxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/30/2014 03:47 PM
Subject: Re: Anybody here know anything about Mimix?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I have seen similar issues in our MIMIX environment if there is a job
on
the target system trying to place a lock on the file. MIMIX wants and
expects exclusive locks on all of the objects it replicates. If it is
another job competing for the file, clearing object locks and running
the
audit again at a different time should allow the audit to run
successfully.

I second Rob on staying current and contacting Vision support. They
have
been very helpful when I have faced similar issues.

Good luck!

Amy Hoerle
System Administrator
Think Mutual Bank
5200 Members Pkwy NW, Box 5949
Rochester, MN 55901

507-536-5815 or
800-288-3425 Ext 5815
ahoerle@xxxxxxxxxxxxx

From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 01/30/2014 02:03 PM
Subject: Re: Anybody here know anything about Mimix?
Sent by: midrange-l-bounces@xxxxxxxxxxxx


--------------------------------------------------------------------------

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
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
[1]http://www.dekko.com

From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/30/2014 01:38 PM
Subject: Anybody here know anything about Mimix?
Sent by: midrange-l-bounces@xxxxxxxxxxxx

We have a situation at a customer, with an SQL View that's part of our
Wintouch product, and Mimix.

I know I've heard of Mimix, but I can't remember what it is, or what it
does.

All I know about the problem is what they're telling us:

> This is the file that gives mimix heartburn every night. I can delete
> it on ***B*** and push a fresh copy down and the audit runs clean.
The
> next day the same thing. I just can***t figure out why*********

and a screen shot of "Work with Audited Objects," showing (the names
have been changed to protect the innocent):

> Audited Object
> Opt Status Type Name
> _ *NE *FILE WTFOOBAR/WTACTSV2U
> _ *EQ *FILE WTFOOBAR/WTACTCV1
> _ *EQ *FILE WTFOOBAR/WTACTSV1
> _ *EQ *FILE WTFOOBAR/WTACTSV2C
> _ *EQ *FILE WTFOOBAR/WTADDRV1
and so forth.

and it's WTACTSV2U and its *NE status that they're referring to.

All of the files listed on the screenshot are SQL Views of DDS PFs.
WTACTSV2U in particular is a UNION ALL of three slightly different
joins, tying scheduled activities to their accounts and/or contacts,
and
WTACTSV2C is a very simple view (I don't even remember why it's
necessary) that's defined as "SELECT * FROM WTACTSV2U."

If I understood what MIMIX does, and what the "Work with Audited
Objects" is trying to tell us, I'd know what to tell the customer.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [2]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [3]http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [4]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [5]http://archive.midrange.com/midrange-l.

References

Visible links
1. http://www.dekko.com/
2. http://lists.midrange.com/mailman/listinfo/midrange-l
3. http://archive.midrange.com/midrange-l
4. http://lists.midrange.com/mailman/listinfo/midrange-l
5. http://archive.midrange.com/midrange-l





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact