I want test the behavior of various dbsrv16 -ufd option settings when server-level and database-level assertions occur.
I don't care what the assertion codes are, so fakes are OK.
One way to generate assertions would be to create a database and then corrupt it by changing the checksum on one of the database pages.
WARNING: DO NOT DO THIS ON ANY DATABASE WITH REAL DATA !!
dbinit bad.db perl corrupt_the_database.pl bad.db
where corrupt_the_database.pl is the perl script containing:
When you start the database on bad.db (e.g. "dbeng16 bad.db") the server will generate a "Checksum failure" assertion.
Well, the typical EBF readme does contain several bug fixes for (temporary) assertions - some of them are declared with "under very rare circumstances" and the like, others sound reproducable.
Is that a starting point?
Yes, I know, v16 is brandnew, so there are no EBFs and readmes available yet...
answered 14 Mar '13, 10:47