> The only way to guarantee business level data integrity in non-transactional > applications is to force all users off the system briefly while you do steps > 1 - 3.
That's a good point. However, it's important to have a controlled way to do so. I've had people think they were safe to just log everybody off. Of course, there's no way to ensure you're not doing *that* in the middle of a transaction. ;-) Much worse, I've even had people with good intentions of getting everybody off of the system so they could have stable backups. How did they do it? With stopud -f or by doing a kill -9 on each user. Either one could create a mess at least as bad as backing up hot, since processes are not terminated cleanly. Actually, the mess could be worse with the unconditional kill methods, since they could result in corruption of the live database files, while backing up hot only impacts the backup copy. And if you do that while running RFS, head for the hills. Tim Snyder Consulting I/T Specialist U2 Lab Services Information Management, IBM Software Group ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
