Could not allocate space for object 'dbo.ISH_SESSIONSECURITYTOKEN'.'ISH_SESSIONSECURITYTOKEN_U1' in database 'ContentManager' because the 'PRIMARY' filegroup is full

Started running into the following error out of the blue. We have a Tridion Docs 13 SP2 install, and can't access anything.
[‎10/‎22/‎2019 1:03 PM]
System.Data.SqlClient.SqlException (0x80131904): Could not allocate space for object 'dbo.ISH_SESSIONSECURITYTOKEN'.'ISH_SESSIONSECURITYTOKEN_U1' in database 'ContentManager' 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.

Parents
  • Hi Akheil,

    Could you first check the disk space on the DB Server?  This is the most likely cause, unless you have “Autogrowth” disabled

     If there is ample disk space on the DB server,check the following

     In SQL Server Management Studio, under database properties choose “Files” in the left menu

    • In the GUI look under the column “FileGroup” and check which one(s) list “Primary” This is usually your .mdf file
    • If you have enough disk space check if “Autogrowth is not set”,
    • If this is the issue you can set Autogrowth to expand the current file, or create another file for storage.

    If your log file is in the "Primary" and you have recovery set to "Full" this may be full and need to run dbcc_shrinkfile

    I hope that helps, if you need further assistance please open a support ticket

    Best regards,

    Frank Gerardi

  • This is actually a different issue then what you are describing. You are describing an issue, if the database file fills up but we have more disk space available but are still receiving this error. The Autogrowth is to allow the database file to grow as the contents of the database grows, which is actually why we ran out of space, is because we do have it enabled.

    We have also already ran a dbcc_shrinkfile and it did not release any space because it’s technically full of real data, not used space. 

    We would like to know if we can safely truncate the table dbo.ISH_SESSIONSECURITYTOKEN safely or if it contains data that is needed by the system in some way. If we can truncate that table, then we can run a dbcc_shrinkfile to reclaim the 85GB’s that was being taken up by that table.

Reply
  • This is actually a different issue then what you are describing. You are describing an issue, if the database file fills up but we have more disk space available but are still receiving this error. The Autogrowth is to allow the database file to grow as the contents of the database grows, which is actually why we ran out of space, is because we do have it enabled.

    We have also already ran a dbcc_shrinkfile and it did not release any space because it’s technically full of real data, not used space. 

    We would like to know if we can safely truncate the table dbo.ISH_SESSIONSECURITYTOKEN safely or if it contains data that is needed by the system in some way. If we can truncate that table, then we can run a dbcc_shrinkfile to reclaim the 85GB’s that was being taken up by that table.

Children
  • Hi Akheil,

    I did ask engineering about this and yes you can truncate the table. If there are users connected, the worse that can happen is that they might need to login again.

    There is concern that the table got this much data.  The standard InfoShare nightly job should remove all records where that time is passed the specified grace period., which the default is 20.  Can you check that the “Standard InfoShare job” on the DB server is regularly scheduled and is running successfully?

    If you need more assistance on this, please open a ticket with support and reference this post.

    Best regards,

    Frank Gerardi