I kind of held off on a reply for a bit, but I wanted to offer one other
challenge to the situation.
A place where I worked had data stored in DB2 (on the IBM i in a local data
center), in Oracle (in a locally hosted data center server), and in MS
Sequel Server (in AWS). Admittingly, the MS Sequel Server instance was used
for SSRS, meaning data was "pushed" to that environment, and other reporting
so the refresh plan didn't have to include any special provisions. However,
due to the layout, a data refresh needed to consider how to "snapshot" both
DB2 and Oracle (within a moment of each other) or the data would be
out-of-sync when looking across platforms.
There was a "free flow" of data between DB2 and Oracle. RPG and Java
programs on the IBM i would read from Production Oracle tables as well as
write to Oracle work tables, and the middleware processes (Java, web pages,
etc.) would do the same with the DB2. Our hard and fast rule was that no
off-platform process was allowed to directly update a Production table in
the other environment to allow for proper "scrubbing" of any one-off kind of
data situations, hence the writing to work tables for localized additional
processing.
My point here is that when considering your data refresh strategies don't
get too "IBM i centric" or tunnel-visioned. We live in an ever changing
world where coordinating between multiple environments on multiple platforms
in multiple locations becomes increasing more complex, and common.
As Gad put it, my 2 cents.
Steve
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Gad
Miron
Sent: Sunday, September 29, 2024 6:20 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Replicating Data Between IBM i Prod and Dev
Our method is pretty basic.
On a Quarterly basis we take the Prod daily backup and manually execute a CL
on the Test/Dev machine that scans a file with libraries to replicate,
clears them and then restores from the A/M backup.
my 2 cnts
Gad
from: Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
subject: Replicating Data Between IBM i Prod and Dev
HI All,
Customer wants to regularly refresh data between Production and Dev
systems. (Once every few weeks be able to refresh)
Please give me some ideas on best practices.
I can think of:
-Replication software. (Probably the MOST up to date) -Save/restore
libraries between systems with save files -Use DDM files to move data.
Please share your strategies to keep test data relatively fresh on
your dev systems.
Thanks in advance.
Regards,
Richard Schoen
Web: http://www.richardschoen.net<http://www.richardschoen.net/>
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
midrange.com
