Database requirements
The database stores all the data retrieved from the clients. Before installing the BigFix server, ensure that the database requirements are met.
A pre-upgrade check Fixlet is available to perform a set of checks to verify if the BigFix server can be successfully
upgraded to V11. A log file is created in the BigFix server directory
containing details about the executed steps. If these checks fail, a
preupgrade-Version 11 <datetime>.err
log file is created
in the BigFix server
directory. If these checks end successfully, a preupgrade-Version
11.out
log file is created in the BigFix server directory. X
is the modification level. This task is not relevant only when all the checks are
completed successfully.
The BigFix server on Windows systems supports the following configurations:
- Local or remote Microsoft SQL Server 2014, 2016, 2017, 2019 or 2022 or remote DB Google Cloud
SQL for Microsoft SQL Server 2022 database.Note: When installing BigFix in a production environment, Microsoft SQL Server Enterprise and Standard are recommended. The Express edition might be used for very small deployments. Refer to Microsoft documentation to choose the best database for your deployment.Important: When installing or upgrading BigFix, the user account performing the installation or upgrade must have
sysadmin
server role in SQL Server. When working with a remote instance of SQL Server, the AD domain service account must have dbo rights, that isdb_owner
on the BFEnterprise and BESReporting databases. Start withsysadmin
server role to perform the installation or upgrade, then back off the privileges todb_owner
after the product is up and running.Important: When working with SQL Server, ensure that you satisfy the following prerequisites for the Microsoft SQL database collation:- The database collation must be case insensitive.
- The database collation at the server, database and column level must be set to the same value.
- At the SQL server instance level
SELECT ServerProperty('Collation')
- At the database level
SELECT DatabasePropertyEx('BFEnterprise','Collation')
- At the column level in the BFEnterprise and BESReporting databases
SELECT C.name, O.name, C.collation_name
Important: The database compatibility level for BFEnterprise and BESReporting must be at least 120.Note: The database passwords must not contain the characters '{' or '}' , otherwise the installation might fail.
- Local or remote Microsoft SQL Server 2014, 2016, 2017, 2019 or 2022 or remote DB Google Cloud
SQL for Microsoft SQL Server 2022 database.
- Microsoft SQL Server 2019 or 2022 on Windows can be configured to leverage Microsoft Extended Protection for Authentication. On Microsoft SQL Server 2022 the Strict Encryption is not supported.
-
The BigFix server on Red Hat Enterprise Linux systems supports the following configurations with MS SQL as deployed database:
- Starting from Patch 1, Microsoft SQL Server 2019 or 2022 (Enterprise and Standard are recommended) can be installed on BigFix Server Linux Red Hat 9.
- Only the SQL Authentication is supported. DSA environments are not supported on the BigFix Linux Server with Microsoft SQL database.
- Microsoft SQL Server 2019 or 2022 on Linux can be configured to leverage Microsoft Encrypted Connection.
- Starting from Patch 2, BigFix Server supports Google Cloud SQL for Microsoft SQL Server 2022 database.
- Only the SQL Authentication is supported.
- DSA configurations are not supported with Google Cloud SQL for Microsoft SQL Server 2022 database.
The BigFix server on Red Hat Enterprise Linux systems supports the following configurations with DB2 as deployed database:
- If the DB2 server is installed locally: DB2 V11.5 GA / 11.5.4 / 11.5.5 / 11.5.6 / 11.5.7 / 11.5.8 / 11.5.9 Standard Edition 64-bit.
- If the DB2 server is installed remotely: IBM Data Server Client V11.5.
db2licm -l
command. On the computer where the DB2 server is installed, you receive a detailed report, if only the client is installed you receive an empty report. To check which DB2 version is installed, run thedb2level
command.Note: After installing a deployment, the DB2 instance name used to connect to the database can no longer be modified. The default name isdb2inst1
.Note:- The DB2 instance name with which BigFix connects
to both BigFix Server and Web Reports databases must have the following privileges:
- The SYSADM privilege during the phase of installation.
- The DBADM privilege during the phase of upgrade.
- The DATAACCESS privilege at run time.
- Ensure that you meet the following required database configurations
needed to install/upgrade BigFix:
- LOGFILSIZ must have a minimum value of 10240.
- LOGPRIMARY must have a minimum value of 10.
- LOGSECOND must have a minimum value of 100.
- AUTO_REORG must be set to ON.
- Ensure that you you have stopped all BigFix services and you have closed
all connections to the BFENT database. To verify if you have
successfully done these operations, run the following
command:
It should return the following output:db2 list applications for db BFENT
SQL1611W No data was returned by Database System Monitor.
-
The DB2 instance names used to install the BES Root Server cannot contain the following special characters: blanks, tabs
\t
, returns\n
and; & | " ' < >
- The database passwords cannot contain the following characters: blanks,
tabs
\t
, returns\n
and; & | " ' < > %
- To successfully install the BigFix server on Linux systems, ensure that you unset the DB2 registry variable DB2_COMPATIBILITY_VECTOR. This variable should be set to null.
For more information about the supported database versions, see BigFix Support Matrix.