- Flexera Community
- :
- Data Platform
- :
- Data Platform Forum
- :
- Error during Normalize - Could not allocate space for object 'dbo.SORT temporary run storage: 140821...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error during Normalize - Could not allocate space for object 'dbo.SORT temporary run storage: 140821531066368' in database 'tempdb' because the 'PRIMARY' filegroup is full.
We are receiving the below error during our Normalize process. Our DBA has increased the tempdb space for us so that the Normalize process can finish. However we would like to know what we can do to avoid this going forward. The error states "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."
Which one of these steps can we take advantage of to avoid the issue in the future?
We are using an FNMS compliance MSSQL database as our data source.
ERROR An error occurred while importing task[17271]
System.AggregateException: One or more errors occurred. ---> System.Data.SqlClient.SqlException: Could not allocate space for object 'dbo.SORT temporary run storage: 140821531066368' in database 'tempdb' 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.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @karlwogoman ,
I personally prefer to set auto growth on for existing files in the filegroup.
Could you confirm with your DBA which DB server the changes were made to? FNMA SQL database server or the BDNA database server? If the issue occurred on your FNMS SQL server, could you please share the FNMS extractor config file with me? We have an optimized version for the FNMS extractor config file which could prevent such error from happening , but we might need to check if there is any customized section in your current config file first.
Regards,
Gang
