MSSQL 2017 on Linux: Full Text Search: Full-text catalog lacks sufficient disk space to complete this operation

Microsoft.SQLServer.2017.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_lacks_sufficient_disk_space_to_complete_this_operation_1_5_Rule (Rule)

There is not enough disk space to hold the full-text catalog.

Knowledge Base article:

Summary

There is not enough disk space to hold the full-text catalog.

Causes

The size of a full-text catalog is usually less than 50 percent of the size of the raw data, that is, of all full-text indexable data in the catalogs. However, the master-merge process requires additional space.

Resolutions

You must determine the total data size of the full-text indexed columns in all indexes that belong to the catalog. To further accommodate the master-merge process, we suggest that you allow space for 100 percent of the raw data size for the full-text catalog. Use the operating-system cleanup utilities to reclaim disk space.

Overrideable Parameters

Name

Description

Default Value

Enabled

Enables or disables the workflow.

Yes

Interval (seconds)

The recurring interval of time in seconds in which to run the workflow.

300

Priority

Defines Alert Priority.

1

Severity

Defines Alert Severity.

2

Synchronization Time

Synchronization Time

 

Timeout (seconds)

Specifies the time the workflow is allowed to run before being closed and marked as failed.

200

Timeout for database connection (seconds)

The workflow will fail and register an event, if it cannot access the database during the specified period.

15

Element properties:

TargetMicrosoft.SQLServer.2017.Linux.DBEngine
CategoryEventCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
MSSQL 2017 on Linux: Full Text Search: Full-text catalog lacks sufficient disk space to complete this operation
{0}
CommentMom2017ID='{6E7F9690-D62A-4BDD-A310-D5F17E404C59}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

ID Module Type TypeId RunAs 
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_ DataSource Microsoft.SQLServer.2017.Linux.DataSource.EventCollectionFiltered Default
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SQLServer.2017.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_lacks_sufficient_disk_space_to_complete_this_operation_1_5_Rule" Target="SQL2017LD!Microsoft.SQLServer.2017.Linux.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2017ID='{6E7F9690-D62A-4BDD-A310-D5F17E404C59}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Microsoft.SQLServer.2017.Linux.DataSource.EventCollectionFiltered">
<MachineName>$Target/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/MachineName$</MachineName>
<InstanceName>$Target/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/InstanceName$</InstanceName>
<ConnectionString>$Target/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/ConnectionString$</ConnectionString>
<SqlTimeoutSeconds>15</SqlTimeoutSeconds>
<TimeoutSeconds>200</TimeoutSeconds>
<IntervalSeconds>300</IntervalSeconds>
<SyncTime/>
<EventDisplayNumber>7622</EventDisplayNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2017.Linux.EventRule.DBEngine.Full_Text_Search___Full_text_catalog_lacks_sufficient_disk_space_to_complete_this_operation_1_5_Rule.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>Event ID: $Data/Property[@Name='EventID']$. $Data/Property[@Name='Message']$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>