Anything wrong with having a process that does an INPUT mid way through a transaction, and then KILLing it ? Or just turning the power off to the machine ? Then again, you could kill UV and then fire up a hex editor on the files - or maybe delete a file or 2.
I'd like to think that you couldn't go & repeatedly "corrupt" the environment from a program (hmmm, wonder what impact a 64K key would have ?) Rather than actually "killing" the live machine, for DR I would have thought that bringing up the DR server with appropriate logs etc would have been good enough Ross Ferris Stamina Software Visage an Evolution in Software Development >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:owner-u2- >[EMAIL PROTECTED] On Behalf Of Simon Bole-Brown >Sent: Wednesday, 5 May 2004 12:25 PM >To: '[EMAIL PROTECTED]' >Subject: [U2] How to corrupt UniVerse file(s) for Transaction Logging and >DR te sting. > >Hi Everyone, > >I have a need to be able to corrupt a UniVerse file and to be able to >repeat >the process. This is required for the testing and demonstration of >Transaction Logging to management. > >The next step will include the testing of various methods of replicating >UniVerse databases and DR logs to a remote DR server, crashing UniVerse and >breaking database(s) and being able to fail over to the DR site and recover >the UniVerse databases on the DR site. The testing servers and UniVerse >are >fully available to me to do anything to them (within reason). > > >Can anyone please suggest how best to set up file(s) that I can break as >required? Anything special that needs to be done with keys, key length, >record size, file type, etc? > >Thanks for your help. > > > >Thank you Clif for all your great work over the years and to the new >moderators for continuing with this list. > > >> Regards, >> >> Simon Bole-Brown >> PMS Systems Administrator >> Mobile: 0421 056 451 >> Phone: (03) 9676 1663 >> >> Toll Priority IT. >> 481 Plummer Street >> Port Melbourne VIC 3207 >> Australia >> [EMAIL PROTECTED] >------- >u2-users mailing list >[EMAIL PROTECTED] >http://www.u2ug.org/listinfo/u2-users > > >--- >Incoming mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.677 / Virus Database: 439 - Release Date: 4/05/2004 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.677 / Virus Database: 439 - Release Date: 4/05/2004 ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
