Postby ConvertFromOldNGs » Fri Aug 07, 2009 12:35 pm
by Jade Support >> Mon, 31 May 2004 22:30:05 GMT
In this instance the error has been caused by running the database against the wrong binaries.
A record-level checksum mechanism has been implemented so that corrupted records are detected when they are read from disk. This mechanism is implemented with hot-fix 5.2.8.192 included in this 5.2.8.220 consolidated release.
The checksum mechanism imposes no space or I/O overheads, and while the checksum calculation incurs a slight CPU burden, sensible use of database cache settings minimises the overhead because the mechanism is implemented at the disk file I/O interface.
When an updated record is flushed from the database cache, a record checksum is calculated and stored with the record; that is, checksums are applied gradually as objects are updated. If you want immediate proliferation of checksums to a file or the entire database, perform file-level operations; for example, compaction or re organization, which update all records.
When a check summed record is read into the database cache, the checksum is recalculated and compared. A mismatch will generate a 3114 exception ("Checksum mismatch in fetched data"). When this exception is raised during normal processing, the affected data is inaccessible. While it is possible for you to continue operations with degraded access to your data, to reinstate data integrity you must restore your database from backup and perform a roll-forward recovery. When a checksum error is detected during recovery processing, the recovery process is terminated.
For further information regarding this check summing, please review the readme.txt file supplied with consolidated patch 220 for JADE release 5.2.08.
The latest help files available are those PDF and Online Help documents shipped with 5.2.08.