Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Potential image copy issues for a multi client DB2 database

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
ozburt

New User


Joined: 05 Nov 2009
Posts: 5
Location: UK

PostPosted: Fri Dec 07, 2012 9:24 pm    Post subject: Potential image copy issues for a multi client DB2 database
Reply with quote

We have an DB2 mainframe application database that is designed to be a multi client database. Up to now this has not been an issue as there has only been one client in this database.

However, with a new client now coming on board this may present us with a potential problem.

The situation we have will be:

The tables will all contain data for both clients. To distinguish between each client’s data there will be a code unique to each client within the table.

Full image copies are taken for this database daily.

The problem we have:

If there is corruption of one client’s data we may need to recover the data for that client. How do we do this without impacting the data for the other client which must remain unchanged?

Ideally there should be a facility to do selective image copies for data within a table which is client specific. However I don’t think this is available. Also any recovery of one client’s data would mean that the data for that client would be overwritten in the table while the data for the other client is left alone. And would doing a recovery effectively lock the table for the recovery period thus preventing the other client from accessing their data in the table?

Unloading from image copies will not provide the solution as the unload is from the full image copy dataset and cannot be client specific.

We are looking for ways to avoid potential issues with this new client coming on board.

I think possibly the safest way is to unload data for each client to flat files on a daily basis. Then when data is corrupted it can be restored for the affected client by doing the following:

1) Take an image copy for the table & unload the data to flat files for both clients
2) deleting all rows currently in that table for the affected client
3) a load resume for the client concerned to add data to the table without impacting data for the other client

How could we incorporate this within the Disaster Recovery process?

Your advice is appreciated.
Back to top
View user's profile Send private message

Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1753
Location: Bloomington, IL

PostPosted: Fri Dec 07, 2012 9:41 pm    Post subject:
Reply with quote

You can specifiy that only certan records be loaded to a table using the WHEN keyword. See here for an example.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Mail via SMTP with an image? Mike 1304 JCL & VSAM 4 Thu Jan 26, 2017 2:01 pm
No new posts SORTJOIN - Copy Matched and Unmatched... Steve Ironmonger DFSORT/ICETOOL 5 Tue Jan 17, 2017 4:26 pm
No new posts HALDB data refresh/copy from producti... vineetanand2007 IMS DB/DC 1 Mon Jan 02, 2017 11:16 am
No new posts Copy RECFM =VB TO FB file with RECL =... sahil41352 DFSORT/ICETOOL 3 Wed Dec 28, 2016 11:29 pm
No new posts syncsort: copy lines after the keyword shreya19 SYNCSORT 7 Fri Dec 02, 2016 9:47 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us