How to check the autogrowth setting for an ePolicy Orchestrator database

Technical Articles ID: KB93031
Last Modified: 2023-08-07 06:58:16 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.x

Summary

This article provides guidance on how to identify why an ePO database can be out of space. The article primarily covers how to identify if the space issue is related to either of the following reasons:

The SQL Autogrowth setting
The partition hosting the database files is out of space

If your company has a Database Administrator (DBA), we recommend that you contact your DBA for assistance.

Problem

You receive an error message indicating that the ePO database is full. There are several reasons that a database might be full. Common reasons are as follows:

One or more files used by the ePO database are restricted in size.
The partition hosting the database is out of space.

In both scenarios, the error messages can appear to be identical. This article helps you determine the actual problem.

Here's an excerpt from an error message you might see in the Orion.log file if your database is full:

The 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth to on for existing files in the filegroup.

Solution

To check the auto-growth setting for the ePO database and enable it if it's disabled:

Enable Auto-Growth:

Open a connection to the SQL Server hosting the ePO database using SQL Server Management Studio. For details, see KB67591 - How to run a SQL script provided by Technical Support against the ePolicy Orchestrator database.
Locate the ePO database in Object Explorer. By default, the ePO database is named ePO_<server name>, where <server name> is the name of your ePO server.

NOTE: ePO 5.10 has two databases; the second database is named ePO_<server name>_Events.
Right-click the ePO database, and select Properties.

NOTE: If you're experiencing problems with threat events, and if you're using ePO 5.10 or later, check the events database.
Select files from the Select a page list on the left.
Examine the Autogrowth / Maxsize column, and take the following actions based on how it's configured:

If all rows have the autogrowth set to unlimited, auto growth isn't the problem. Look at the Path column, which tells you what partition the ePO database is hosted on. Confirm that the partition has ample free space. If the partition is out of space, and if freeing up space or adding extra space isn't an option, see the section "Autogrowth is Limited" below for possible alternative solutions.
If any rows have the size set to limited, look at the Path column. The path column tells you where the file is located. Then, look at the File Name column, which specifies the name of the file. Then, check the path/file and see if it has reached the auto-growth limit. Also, make sure that the partition has ample free space. If the file has reached its auto-growth limit, and you have ample free space, you can continue to Step 6. Otherwise, if unlimited autogrowth isn't an option, see the section "Autogrowth is Limited" below.
If any rows have auto-growth None, continue to Step 6 for instructions on enabling auto-growth.

Click the ellipsis in the Autogrowth / Maxsize column.
Select Enable Autogrowth.
In the File Growth selection, select In Percent, and set the value to 10.
In the Maximum File Size selection, select Unlimited.
Click OK, and OK again.

NOTE: The setting changes above take effect immediately. No service restart is needed.

Autogrowth is Limited
This discussion provides suggested alternatives for the following situations:

The database Autogrowth is limited, and you can't increase it.
You've reached the capacity of the partition hosting the database, and freeing up or increasing capacity on the partition isn't an option.

When you want to purge data from the primary database file:

NOTE: This option doesn't apply if the log file is full.
To purge data from the database, follow the instructions in one of the following articles:

When the transaction log is full:
Reduce its size by switching the log level to simple:

Open a connection to the SQL Server hosting the ePO database using SQL Server Management Studio. For details, see KB67591 - How to run a SQL script provided by Technical Support against the ePolicy Orchestrator database.
Right-click the ePO database that you're having problems with, and select Properties.
From the "Select a page" section on the left, select Options.
In the Recovery Model drop-down list, select Simple.
Click OK.

NOTE: The setting changes above take effect immediately. No service restart is needed.

Affected Products

ePolicy Orchestrator 5.10.x

Languages:

This article is available in the following languages:

Knowledge Center

How to check the autogrowth setting for an ePolicy Orchestrator database

Environment

Summary

Problem

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

How to check the autogrowth setting for an ePolicy Orchestrator database

Environment

Summary

Problem

Solution

Affected Products

Languages:

Choose your region

Title

Title