Upgrade prerequisite checks
The following prerequisite checks are automatically run by the upgrade procedure on the BigFix Server.
If any of these checks fails, the upgrade does not start and the procedure exits with an error
message. You can rerun the upgrade after you ensure that the condition that failed is satisfied.
The upgrade procedure checks that:
- The size of the Upload Manager Buffer Directory and the number of files that it contains do
not exceed the 90% of the values that are specified in the following settings:
If the check fails: Fix the issue by running the following Fixlets available in the BES Support site, and then rerun the upgrade:_BESRelay_UploadManager_BufferDirectoryMaxSize _BESRelay_UploadManager_BufferDirectoryMaxCount
2695: WARNING: Upload Manager Directory exceeds file max number - BES Server 2696: WARNING: Upload Manager Directory Full - BES Server
- The site names listed in the following columns of the database contain only ASCII
characters:
LOCAL_OBJECT_DEFS.Name LOCAL_OBJECT_DEFS.Sitename
If the check fails: Rename the site names and fix the content referencing them.
- The size of the data related to custom content and the actions that are contained in the
ACTION_DEFS.Fields
andLOCAL_OBJECT_DEFS.Fields
fields does not exceed the maximum size allowed in the new database schema.If the check fails: Shorten the exceeding data length.
- The data contained in each of the following fields does not exceed the maximum index
length:
DASHBOARDDATA.NAME UNMANAGEDASSET_FIELDS_TYPES.FIELDNAME WEBUI_DATA.NAME
If the check fails: Shorten the data contained in the fields as required.
Run these steps, if you are in a DSA environment and any of the prerequisite checks fails on the
primary server, which is the first server that is upgraded:
- Run the needed corrective actions on the primary server.
- Wait for a full replica on the secondary servers to ensure that the same corrective actions are applied to their databases as well.
- After the full replica completes, rerun the upgrade on the primary server and then on the secondary servers.