T
temays
Guest
Valeriy is exactly correct in his description of how the new and old versions of bulk load restart logic operate. Pro2 version 5.0.1 introduced a new feature in which ROWID cache (comma delimited list of ROWIDs) was stored for in the bulk load replcontrol record. The Bulk_Max_Cache property controls how many cache entries are stored (bigger is typically better with 25 being the default.) WHEN using ROWID cache, the time to restart from a failure is very quick. In previous versions of Pro2 bulk load (<= 5.0.0), only a count was stored in the bulk load replcontrol record, so upon restart the load program read from the beginning of the table and ignored rows below the counter. If the load was stopped after a large number of rows had been loaded, then you would notice a significant delay associated with firing the old restart logic. Be aware, the bulk load process is running, it's just trying to get back to the record loaded before the failure. Hope this helps, Terry
Continue reading...
Continue reading...