000017625 - RSA Archer: History log has filled up instance database, unable to log on

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Oct 28, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000017625
Applies ToRSA Product Set: Archer
Issue

Unable to log on to RSA Archer.  Archer.w3wp error log shows the following:



Message>Could not allocate space for object 'dbo.tblSessionTemp'.'PK_tblSessionTemp' in database 'Archer Instance' because 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 on for existing files in the filegroup.

ResolutionThe immediate solution to the error shown above is to free up space on the database server. 

Run the SQL script "Get table size.sql" to determine which database tables are consuming the most space. The query will return a list of tables in descending order of used space. 

If the query above indicates that the field history table (tblIVFieldHistory) is consuming an excessive amount of space, run the query "History table fields by row count.sql". This will tell you which fields are generating the most data in the table.  Based on this information, you can evaluate whether history log fields should be modified to remove tracking for certain fields.

If you determine that the field history table (tblIVFieldHistory) is the cause of the problem, consider modifying history log fields to turn off tracking for fields that are generating a large amount of history data.
 
Legacy Article IDa66870

Outcomes