Loading...

Knowledge Center


How to troubleshoot a full ePolicy Orchestrator TempDB
Technical Articles ID:   KB90101
Last Modified:  5/2/2018

Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Summary

TempDB is a system database used by a SQL Server to carry out several operations. It is normal for it to grow, because it is used by SQL, to the maximum size needed for normal operation. For example, if a specific query in SQL requires 1 GB of tempdb space, the files that make up tempdb grow to 1 GB. When the query completes, SQL releases the space in tempdb, but the files remain at 1 GB; tempdb does not automatically shrink by default.

It is normal for the tempdb size to increase over time; the maximum size depends on the work that ePO is doing. But, SQL and ePO functionality could degrade, or fail entirely, if tempdb runs out of space because:
  • The disk where the SQL database resides is full.
  • The SQL database maximum size has reached the configured limit.
TempDB is re-created when the SQL Server service starts. You can reduce the size of the database if needed by restarting ePO services on the ePO server, and any additional Agent Handlers:
  1. Stop the ePO services:
    1. Press Windows+R, type services.msc, and click OK.
    2. Right-click the following services and select Stop:

      McAfee ePolicy Orchestrator x.x.x Application Server
      McAfee ePolicy Orchestrator x.x.x Server
      McAfee ePolicy Orchestrator x.x.x Event Parser

       
  2. Start the ePO services:
    1. Press Windows+R, type services.msc, and click OK.
    2. Right-click the following services and click Start:

      McAfee ePolicy Orchestrator x.x.x Application Server
      McAfee ePolicy Orchestrator x.x.x Server
      McAfee ePolicy Orchestrator x.x.x Event Parser
A new, small tempdb is created.

Troubleshooting steps
When troubleshooting problems with the tempdb, you must first determine if the tempdb is full or is mostly free space:
  1. Open SQL Management Studio.
  2. Connect to the SQL instance hosting the ePO database.
  3. Expand Databases and select System Databases.
  4. Right-click tempdb and select Properties.
  5. On the General page, in the Database section, locate the Size and Space Available values.

    If there is a large amount of space available in tempdb, it implies that SQL is working correctly. At some point, an operation caused tempdb to grow to the size it currently is, but the operation completed and released the space in tempdb that it was using.

    In this scenario, allow tempdb to grow to the size it requires, as SQL is functioning correctly.

    If there is little or no free space, a problem is indicated. In SQL Management Studio, run the following query:
     
    SELECT is_read_committed_snapshot_on FROM sys.databases WHERE Name = '<epo database name>'

    where <epo database name> is the name of the ePO database.

    This query normally returns a value of 1 or 0, depending on the version of ePO:
    • ePO 5.3.1 and 5.3.2 normally return 1.
    • All other ePO versions normally return 0.
If you are running ePO 5.3.1 or 5.3.2, and experience tempdb growth, upgrade to ePO 5.3.3 or 5.9.x. 

If you are on any other version of ePO and the query returns 1, contact Technical Support because additional steps are required to address an issue with the database.

To contact Technical Support, log on to the ServicePortal and go to the Create a Service Request page at https://support.mcafee.com/ServicePortal/faces/serviceRequests/createSR:
  • If you are a registered user, type your User Id and Password, and then click Log In.
  • If you are not a registered user, click Register and complete the required fields. Your password and logon instructions will be emailed to you.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Spanish Spain
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.