it look like lot of work to do (copy check). why don't you just backup the
data and ensure an IPL from a one pack system? Data can then be loaded to
the target dabase engine in case of severe error.
ITschak
On Sat, Jan 3, 2009 at 11:17 PM, Magen Margalit syste...@gmail.com wrote:
Hi,
Sorry
Hi,
Sorry if I wasn't so clear, of course that the replicated copies will be
checked.
The plan to replicate 3 times:
1 copy will be untouched.
1 copy will be IPL'ed to make sure it's ok (some appl checks will be taken to)
if not... you will have the untouched copy from prvious period
Magen,
Phisical dumps will not keep your referential integrity. U must use
utlities. Have a look at DR/Expert from OpenTech systems at
http://www.opentechsystems.com/drdb2.php. You can call me if you need more
info. Same phone.
Itschak
On Fri, Jan 2, 2009 at 9:44 AM, Binyamin Dissen
snip---
Binyamin Dissen wrote:
On Thu, 1 Jan 2009 04:08:00 -0600 Magen Margalit syste...@gmail.com wrote:
:We are Z10 with Zos 1.9 shop.
:We recently had a major logic error with DB2 catalog which
:led us to think how can we prepare
Hi List,
We are Z10 with Zos 1.9 shop.
We recently had a major logic error with DB2 catalog which
led us to think how can we prepare and recover quickly in the
event of any (not just DB2) logical error
(In this case the PPRC / HRC copy of the data won't help since the
error was replicated).
On Thu, 1 Jan 2009 04:08:00 -0600 Magen Margalit syste...@gmail.com wrote:
:We are Z10 with Zos 1.9 shop.
:We recently had a major logic error with DB2 catalog which
:led us to think how can we prepare and recover quickly in the
:event of any (not just DB2) logical error
:(In this case the PPRC
6 matches
Mail list logo
