Set the saveMode property to 2 when debugging a non-transactional DataStore. The debugger stops all threads when single-stepping or when breakpoints are hit. If the saveMode property is not set to 2, this keeps the DataStore daemon thread from saving modified cache data. For more information, see "Controlling how often cache blocks are written to disk".
If you suspect that cache contents were not properly saved on a non-transactional DataStore, you can verify the integrity of the file with the DataStore Explorer. See "Verifying the DataStore" for more information.
There is also a borland.datastore. StreamVerifier class with public static verify() methods that can verify a single stream or all streams in DataStore. For more information, see the DataExpress Component Library Reference.
Note that transactional DataStores have automatic crash recovery when they open. You never need to verify them.
If problems are encountered, use the DataStore Explorer (see "Copying DataStore streams") or the DataStoreConnection.copyStreams method to repair the damage.
Sun Microsystems makes changes to its java.text. CollationKey classes from time to time as it corrects problems. The secondary indexes for tables stored inside a DataStore use these CollationKey classes to generate sortable sort keys if a non-US locale is being used. When Sun changes the format of these CollationKeys, the secondary indexes created by an older Sun JDK may not work properly with a new Sun JDK. The problems resulting from such a situation will manifest themselves in the following ways:
Currently, the only way to correct this is to drop the secondary indexes and rebuild them with the current JDK. The StorageDataSet.restructure method will also drop all the secondary indexes.
As old log files are no longer needed for active transactions or crash recovery, they are automatically deleted. Old log files can be saved by listening to the DataStore.response event for a ResponseEvent.DROP_LOG notification. At that point, you can copy out the log file to another location before it is deleted, or cancel the event to prevent the deletion of the log file.
pubsweb@borland.com
Copyright © 1999, Inprise Corporation. All rights reserved.