MARS: "Unable to estimate slack or disorder for $<vol><subvol>.<file> -- error 1"`
The error indicates that MARS could not perform an estimate because of error 1 when sampling records to determine slack or disorder. As error 1 indicates that the EOF was reached without finding any records. There is likely not enough data in the file to make an estimate.
Be sure that the fileset is set to trigger a reload (ie, checkbox checked) based on free blocks allocated. This can be accomplished by checking the "reload triggers tab" in the "fileset configuration".
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.
Related Articles
MARS: How is the percentage of File Disorder and Slack Space calculated.
A block is considered to be disordered if its logical order (by key value) in relation to adjacent blocks within the file does not match the physical order of those blocks. To estimate disorder, MARS selects approximately 100 blocks from random ...
MARS: System.Classes.TList.Error
If this issue only happens on older version of mars < 2.60. We recommend upgrading to MARS 2.60 to resolve the issue. From the Softdoc: * ITID 260-443 Addresses an issue where excluded CPUs defined to a reload schedule window were still being used ...
DISCOVER - DCVFH File Is Full
DCVFH contains the file history data for files managed by Discover. If saving the history for existing files is desired, execute the following command to clean up DCVFH records: Logon as the Discover installation owner DCI CLEAN HISTORY EXIT This ...
MARS: Error importing MARS reload filesets when upgrading from MARS 2.40
The workaround is to modify the fileset and add "<*OUS|Fixed>0<#>" to the end of the configuration. Example below: <[ReloadFileSets> <*FSN|String>test01<#><*GDS|String>Audited Files in more than two patterns will be evaluated every week.\n\nSQL ...
XYGATE: UNPAK Error After Obeying Product BIN file (How to manually install host product BIN file)
This may occur with any host XYPRO product BIN file. Workaround is to manually UNPAK the BIN file to a distribution subvolume, then manually run INSTALL: Example: Customer has downloaded BIN file for XMA called XMAINST. They tried to obey it, but it ...