Stopping the Bulk Import Tool
You can stop Bulk Import Tool by creating a .Stop file or a .Shutdown file in the directory where the tool was started.
About this task
In-flight batch is stopped after any in-flight subBatches complete. The file extensions are changed to .err with information in the .err file and in the Journal file. The sub-batches which completed prior to the .Stop remain in the object store. To recover or restart, the user would manually determine which files are present as documents. The unprocessed files are then arranged into a new batch and resubmitted.
When you use the .Shutdown file, all of the batches that were locked at the start of the processing cycle are completed before Bulk Import Tool is shut down. Use of the .Shutdown process is recommended.
.Shutdown allows the in-progress batch to complete, including any in-flight and not yet processed subBatches. At the end of .Shutdown, in-process batches have normal .pass, .rpt, and confirm files. No additional batches that were not in-flight are processed, as indicated by the message "Detected CEBIShutdown, removing remaining tasks from work queue."
- In the directory where the tool was started, create a .CEBI.Stop file by
using the following examples for each operating system.
When the Bulk Import Tool is started, if the process finds a .CEBI.Shutdown or a .CEBI.Stop file, the file is automatically deleted and processing proceeds as requested.Operating system Example UNIX touch .CEBI.Stop Windows echo > .CEBI.Stop - In the directory where the tool was started, create a .CEBI.Shutdown file
by using the following examples for each operating system.
When the Bulk Import Tool is started, if the process finds a .CEBI.Shutdown or a .CEBI.Stop file, the file is automatically deleted and processing proceeds as requested.Operating system Example UNIX touch .CEBI.Shutdown Windows echo > .CEBI.Shutdown