DB2 may write uncommitted data to dasd. If a long running transaction updates more pages than the size of the buffer pool assigned to the underlying tablespace, uncommited pages will be flushed to disk. Wayne Driscoll Product Developer Western Metal Supply NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of R.S. Sent: Thursday, July 14, 2005 3:50 AM To: [email protected] Subject: Re: DB2 and flashcopy2 Hal Merritt wrote: > What about the work in progress in DB2 buffers that is not yet > committed > (flushed) to DASD? The I/O might be consistent, but how would the data? Data written to DASD will be consistent. DB2 is *transactional* database. All uncommitted operations (transactions) will be rolled off. It prevents DB2 database from data errors in case of hardware failure. Consistent point-in-time copy will create similar image of DB2 datasets. Data is consistent, but "consistency point in time" is a little bit earlier than time of copy. You cannot predict the delta. You can cause the delta to be zero: set log suspend. -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
