Welcome
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
Datasource deletion process for DB2
This section provides step-by-step instructions for database administrators to compile, execute, monitor, and troubleshoot the DB2 datasource deletion stored procedure using standard DB2 CLI commands.
Step 1: Pre-Execution Environment Setup
Step 1 includes the process for the pre-execution environment setup.

BigFix Documentation Homepage
BigFix 11 Inventory Documentation
Welcome to the BigFix Inventory documentation, where you can find information about how to install and configure BigFix Inventory. The application provides you with information about your inventory and license metrics. You can manage your software assets, gather information about your hardware, and ensure license compliance for your enterprise using BigFix Inventory.
BigFix Platform
BigFix Scanner
Overview
Become familiar with key concepts that are necessary to understand how BigFix Inventory works and learn about features and functions that are introduced in every version of the application.
Installing
Learn about the requirements and available installation scenarios to ensure that the deployment of BigFix Inventory goes smoothly in your environment.
Configuring
After you install BigFix Inventory, configure the application. Create accounts for the users who need access to the application and set up scans to collect software and hardware inventory data from your environment.
Upgrading
A new version of BigFix Inventory is released periodically, typically at the end of each calendar quarter. Upgrade to the new version regularly to take full advantage of new features and application fixes.
Catalog Overview
This section provides information about catalog updates available with every release.
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
- Software Scan Status
- Computer statuses
  Computer statuses provide information about the condition of the computers that are monitored by BigFix Inventory. To properly discover the installed software and measure its license metric utilization, ensure that computers in your environment work correctly.
- Managing VM managers
  VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
- Administering the server
  Perform administering tasks on your server to configure advanced settings, or restart its services.
- Administering the database
  Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
- Datasource deletion process for DB2
  This section provides step-by-step instructions for database administrators to compile, execute, monitor, and troubleshoot the DB2 datasource deletion stored procedure using standard DB2 CLI commands.
  - Step 1: Pre-Execution Environment Setup
    Step 1 includes the process for the pre-execution environment setup.
  - Step 2. Executing DBO.DELETE_DATASOURCE_DATA via DB2 CLI
    Step 2 includes the deletion process.
  - Step 3: Live Monitoring via DB2 CLI
    Step 2 includes live monitoring using the DB2 CLI.
  - Step 4: Post-Execution Verification and Cleanup
    Step 4 includes the post-execution verification and cleanup of the database.
  - Step 5: Risk Mitigation & Rollback Strategy
    Perform a full restoration using the database backup generated during Step 1, point 3. Use the procedural guidelines for recovery: Inventory/admin/t_db2_restore.html.
  - Step 6: Common CLI Errors & Resolution Checklist (Troubleshooting)
    Check the list of common CLI errors and their resolutions.
- Removing inactive computers
  When you decommission a computer in your infrastructure, it continues to report to BigFix Inventory. The data is still collected from this computer, and displayed on the metric reports. To ensure that all infrastructure changes are reflected in BigFix Inventory, you should remove each decommissioned computer from BigFix. If you cannot remove this computer from BigFix for a valid reason, you can use an alternative solution, and decommission the computer in BigFix Inventory.
- Managing data sources
  Computers in an organization can be divided into organizational units, and can be monitored by multiple BigFix infrastructures. Each infrastructure is referred to as a data source. Data from multiple data sources can be imported to one instance of BigFix Inventory.
Software inventory and license utilization
You can classify the discovered software so that reports in BigFix Inventory reflect your entitlements and properly show utilization of license metrics by particular products.
Managing security threats
Learn how to use BigFix Inventory to manage security threats in your environment. You can view whether any of the installed components is prone to any Common Vulnerability and Exposure (CVE).
Tutorials
Tutorials help you understand how to use BigFix Inventory. They consist of modules that focus on broad goals. Modules consist of tasks that show how to configure specific settings step-by-step.
Security
Configure different security features to adequately protect business assets and resources in the data model when using BigFix Inventory.
Troubleshooting and support
Learn about solutions to common problems that might arise when you use BigFix Inventory BigFix Inventory and how to find logs and trace files that help you troubleshoot those problems.
Tuning performance
Learn how to plan the infrastructure of BigFix Inventory and to configure the application server to achieve optimal performance. The following guidelines are applicable in big data environments as well as in smaller environments that are running on low-performance hardware.
Integrating with REST API
External systems integration is one of the key features of BigFix Inventory. Business logic is enabled for integration and interfaces are provided for common integration points.
Glossary
Guide in PDF format
DataFlow ServiceNow Integration
Service Graph Connector Integration

Step 1: Pre-Execution Environment Setup

Step 1 includes the process for the pre-execution environment setup.

Identify the Datasource ID:
Ensure you know the exact ID of the datasource you wish to delete from the BigFix Inventory UI. There must be more than one datasource configured before deleting one.
Stop the BFI Service:
You must manually stop the BigFix Inventory service before running this procedure to prevent database locks. For more information, refer to Stopping the server.
Database Backup:
Take a full, restorable backup of your BigFix Inventory database.
Note: This step cannot be undone.
For more information, refer to Backing up the DB2 database.
User Permissions:
You must execute these steps as the DB2 instance owner (typically db2inst1).
Revalidate the Datasource Deletion Procedure
Following database migration or system upgrade routines, verify that DBO.DELETE_DATASOURCE_DATA is in a valid state before initiating removal actions:
Check Procedure Status: Query the system catalog to evaluate routine status:
```
db2 "SELECT ROUTINESCHEMA,
            ROUTINENAME,
            SPECIFICNAME,
            VALID,
            CREATE_TIME
     FROM SYSCAT.ROUTINES
     WHERE ROUTINESCHEMA='DBO'
       AND ROUTINENAME='DELETE_DATASOURCE_DATA'"
```
Verify Validity: The VALID field should return a value of Y.
Recompile If Needed: If the query returns N, manually recompile the target object using the CLI command below:
```
db2 "CALL SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS('PROCEDURE','DBO','DELETE_DATAS
OURCE_DATA')"
```
Switch User & Set Environment:
Log in as the DB2 instance owner (db2inst1) and terminate any stale CLI connections:
- Log in as the DB2 instance owner, which by default is db2inst1.
- Run the following command to check the details of the existing database:
```
su - db2inst1
db2 list db directory
db2 terminate
db2 connect to TEMADB
db2 "SELECT CURRENT SERVER, CURRENT USER, CURRENT TIMESTAMP FROM SYSIBM.SYSDUMMY1"
```