Could not allocate space for object 'dbo.BINARY_FILE' in database 'SEM5' because the 'FG_CONTENT' filegroup is full.
| Article:TECH106075 | | | Created: 2008-01-30 | | | Updated: 2013-04-01 | | | Article URL http://www.symantec.com/docs/TECH106075 |
Problem
This problem can have many symptoms depending on your Symantec Endpoint Protection Manager (SEPM) configuration.
- Symantec Endpoint Protection (SEP) client pacakges fail to import into the SEPM database.
- LiveUpdate sessions complete successfully on the SEPM, but the updates are not applied.
Error
The following error is written to the scm-server0/1.log:
2008-09-30 12:29:11.968 SEVERE: Unexpected server error. in: com.sygate.scm.server.consolemanager.requesthandler.BinaryFileHandler
com.sygate.scm.server.metadata.MetadataException: Could not allocate space for object 'dbo.BINARY_FILE' in database 'SEM5' because the 'FG_CONTENT' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Cause
This problem affects SEPM servers that use a Microsoft SQL database. The SEPM installation sets a default maximum size for the FG_CONTENT filegroup to 20,000 MB in size. This space is used by content (virus definitions, IPS signatures, etc) as well as client packages that can be exported by the SEPM. This amount of space can handle all existing client packages (current version and all historical packages) and our default enterprise content retention of 30 revisions. Storing more content revisions may require a SQL administrator to increase the maximum autogrowth size of the FG_CONTENT filegroup.
Solution
If your environment requires more than 30 revisions of content, work with the database administrator to increase the autogrowth limit on the FG_CONTENT filegroup. As of March 21, 2013, a single revision of content will use approximately 550 MB of space.
If your environment does not require more than 30 revisions of content, you can work around this problem by lower the number of content revisiont to keep to a more suitable number.
|
|
Related Articles
Legacy ID
2008093013225248
Article URL http://www.symantec.com/docs/TECH106075
Terms of use for this information are found in Legal Notices
Thank you.