Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 30 JDBC Backing Store Setup : Handling Entities Deleted from a Write-Behind Backing Store

Handling Entities Deleted from a Write-Behind Backing Store
TIBCO BusinessEvents Express  This section relates to Cache OM functionality and does not apply to TIBCO BusinessEvents Express edition.
This section pertains only if write-behind strategy is used. See Post-RTC and Epilog Handling and Tuning Options in TIBCO BusinessEvents Architect’s Guide for more information about database write strategies, and see CDD Cluster Tab Backing Store Settings Reference for details on the settings.
When write-behind strategy is used, when entities are deleted from the cache, they are marked for deletion at system startup. An application startup process removes the deleted entities from the backing store.
Depending on the number of deleted entities, the cleanup step can make system startup unacceptably slow.
Manual Deletion of Deleted Entities
To deal with slow startup, you can run a script manually, and eliminate the need to run the cleanup action at system startup. The script is called yourname_delete.sql and it is generated when you create the backing store with the be-jdbcdeploy utility.
Disabling Deleted Entity Cleanup at System Startup
You can also disable the cleanup action performed at system startup and perform all cleanup manually, using the deletion script. To do so, add the following property to the CDD file and set it to false:
be.engine.cluster.cleanup

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved