Hold Sweep is a daemon process. To limit the performance
impact on your system, schedule the process to run when the system
usage is low. To run the hold sweep, ensure that you have the required
JRE level.
Important: Before running Hold Sweep, an Administrator
must set the QueryPageMaxSize property value to 150,000 and the Max
Query Time Limit value to 0. See
Configuring Hold Sweep.
To run Hold Sweep:
- Run Hold Sweep or run a specific profile from the RecordsManagerSweep
folder on the machine where you installed the Hold Sweep component.
Profiles allow you to save different configurations and run sweep
using these configurations without the need to reconfigure them. Use
one of the following methods to run the Hold Sweep process:
Option |
Description |
UNIX |
./RecordsManagerSweep.sh -HoldSweep [-profile
"profile name"] |
Windows |
RecordsManagerSweep.bat -HoldSweep [-profile
"profile name"] |
- Additionally, you can run Hold Sweep on an object store
from the RecordsManagerSweep folder on the machine where you installed
the Hold Sweep component to remove holds using the -ForceRemoveHold parameter.
Running Hold Sweep on an object store allows you to remove listed
record holds, up to a maximum of five, from a specified object store,
remove all holds from within a specified object store, or remove holds
from a specific object store located within a specific profile. When
you remove holds using the -ForceRemoveHold parameter,
the holds are removed if they are active, inactive, manually applied
or applied using Hold Sweep. Use one of the following methods to run
remove holds on an object store:
Option |
Description |
UNIX |
./RecordsManagerSweep.sh -HoldSweep -ObjectStore objectstorename|objectstoreID -ForceRemoveHold holdlist [-profile
"profile name"] For example:
./RecordsManagerSweep.sh -HoldSweep -ObjectStore "MyFPOS" -ForceRemoveHold "Hold1|Hold2|{E4F6F8F9-4E1A-4762-B062-344980B2B92}" -profile
"profile1"
|
Windows |
RecordsManagerSweep.bat -HoldSweep -ObjectStore objectstorename|objectstoreID -ForceRemoveHold holdlist [-profile
"profile name"] For example:
./RecordsManagerSweep.bat -HoldSweep -ObjectStore "MyFPOS" -ForceRemoveHold "Hold1|Hold2|{E4F6F8F9-4E1A-4762-B062-344980B2B92}" -profile
"profile1"
|
Option |
Description |
UNIX |
./RecordsManagerSweep.sh -HoldSweep -ObjectStore objectstorename -ForceRemoveHold
-All [-profile "profile name"] Attention: This option would only be used for a special purpose
|
Windows |
RecordsManagerSweep.bat -HoldSweep -ObjectStore objectstorename -ForceRemoveHold
-All [-profile "profile name"] Attention: This option would only be used for a special purpose
|
- Alternatively, you can run the Hold Sweep process from
a command prompt by navigating to the ..\FileNet\RecordsManagerSweep\lib folder
and entering the following: java -jar rmHoldSweep.jar.
- To stop Hold Sweep, add the -stop parameter:
Option |
Description |
UNIX |
./RecordsManagerSweep.sh -HoldSweep -stop |
Windows |
RecordsManagerSweep.bat -HoldSweep -stop |
A message displays when the Hold Sweep processes have
stopped.
- Verify if Hold Sweep ran successfully by viewing the error
log file created in the RecordsManagerSweep folder. If the error file is empty, the Hold Sweep process ran
successfully. Otherwise, the file contains errors that you can use
to troubleshoot the problem.