Invalid destinations exist when the SFM is restarted with transactions pending for a removed or invalid destination. When a transaction is submitted to SFM, it is qualified against production objects, if needed, and stored in the log file with a PENDING status. In the log file, the destinations to which the transaction will be dispatched are marked. When the SFM is shut down and restarted, it reloads all pending transactions into memory and puts them back onto the internal queue for dispatch. However, if between the shut down and restart, destinations for pending transactions are removed from the SFM configuration, the SFM cannot dispatch the transactions because the intended destination no longer exists. Transactions that are rerouted to a valid destination are marked REPAIRED in the log file.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
