Hal,
Well here's an interesting note about DB2 Log Suspend: "The backup that is made between the SET LOG SUSPEND and the SET LOG RESUME window might contain uncommitted data. If you must restore the entire DB2 subsystem to the time when the log was suspended, restore the entire database and logs from the backup, and then restart DB2 to recover the entire DB2 subsystem to a consistent state. For details, see DB2 Administration." Seems to me that Log Suspend just flushes the buffers, takes a system checkpoint, and then stops your application from writing anything until you do a resume. Rollback of in-flight transactions is still going to take place. It is a nifty way of getting a point in time across you DB2 Logs and tables when the hardware can't do it. A quote from the DB2 Listserv describes Log suspend/resume on RVA using Snapshot: "The 'snapped images' are just the system at a given point in time. Restarting to them is just like doing a restart after a power failure: in-flights will be backed out, in-aborts will be aborted and in-commits will be committed by the normal DB2 start process." Does not sound like a clean copy of the Database to me. In fact it still looks like DB2 crashed. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Hal Merritt > Sent: Thursday, 14 July 2005 10:41 PM > To: [email protected] > Subject: Re: DB2 and flashcopy2 > > You and Ron are right. I was in a mindset of a totally clean environment > where DB2 would not have to go through its cleanup. But I can now see > where such a strategy might make business and technical sense. > > Still, I would rather hold DB2's ability to recover in reserve as > opposed to having to play my trump card every time. Besides, there might > be the rare situation were DB2 will not be able to recover. More, I > would not want folks to think that other DBMS's or applications could be > expected to recover the same way. > > So, in a larger context, DB2, IMS, and such could be said to be > anomalies. > > I am wrong about DB2. But I still argue that recovery begins and ends > with the application. > > Hal > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
