Re: Accessing multiple databases on different systems (IBM i 7.1 TR7)

Hi Paul

My concern with your suggestion is that the updates on the target ("SysB")
may not - i.e. probably wouldn't - get the same relative record number as
the source ("SysA"). I can't remember off hand if you can insert by RRN but
if you can I guess you need to make sure you do this. My gut feel is this
is not possible and if you have Re-Use Deleted Records turned on this will
be even more problematic.

You may end up with a situation where the file is logically the same but
physically different - i.e. same data, but in different positions. I
suspect the replication software will still see this as out of synch.

If it was me I would bite the bullet and refresh/re-synch the file in a
vendor approved way.

On Mon, Jan 12, 2015 at 12:25 PM, PaultinNZ <paultormey@xxxxxxxxx> wrote:

I have a table that is replicated from SysA to SysB.

The table on SysB is not in sync with the origin table on SysA - there are
records missing on SysB.

The normal procedure for getting these back in sync would be to take a
backup from SysA, move that to SysB and restore the table. Tape would be
the transfer medium. Once the transfer is done and the table restore
mirroring from SysA to SysB would be restarted.

Or use our Mirror software and force a refresh which can take some time.

I wanted to look at using a SQL insert using remote DB directory entries.
However, it seems that even with the updates till TR7 I can only open 1
database simultaneously.

Anyone know of a way to open the "TableCommon" in both Database1 and
Database2 simultaneously and preferrably from a session on the i.

I'm trying to do a select with except to get back rows that do not exist in
SysB.

Look forward to any suggestions.

Paul
--
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: 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 http://archive.midrange.com/midrange-l.