Home
  •  

The database is already involved in log shipping.

Microsoft.SQLServer.2000.The_database_is_already_involved_in_log_shipping (Rule)

Knowledge Base article:

Causes

If this error occurred on the primary server, this database is already configured as the source database in a log shipping pair. The information about source databases in log shipping is stored in msdb.dbo.log_shipping_databases on the primary server.

If this error occurred on the secondary server, this database is already configured as the destination database in a log shipping pair. The information about destination databases in log shipping is stored in msdb.dbo.log_shipping_plan_databases on the secondary server.

Resolutions

If the error occurred on the primary server, execute sp_delete_log_shipping_database for the specified source database on the primary server.

If the error occurred on the primary server, execute sp_delete_log_shipping_plan_database for the specified destination database on the secondary server.

Element properties:

TargetMicrosoft.SQLServer.2000.DBEngine
CategoryEventCollection
EnabledTrue
Event Source$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$
Alert GenerateTrue
Alert SeverityInformation
Alert PriorityNormal
RemotableTrue
Alert Message
The database is already involved in log shipping.
{0}
Event LogApplication
CommentMom2005ID='{B9B72AF5-E09A-4779-A94D-4F49A86DDACA}'

Member Modules:

ID Module Type TypeId RunAs 
EventDS DataSource Microsoft.Windows.EventProvider Default
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SQLServer.2000.The_database_is_already_involved_in_log_shipping" Target="SQL2000Core!Microsoft.SQLServer.2000.DBEngine" Enabled="true" Comment="Mom2005ID='{B9B72AF5-E09A-4779-A94D-4F49A86DDACA}'" Remotable="true">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery>EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>MatchesMOM2005RegularExpression</Operator>

              <Pattern>^(17052|17055)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery>EventDescription</XPathQuery>

              </ValueExpression>

              <Operator>MatchesMOM2005BooleanRegularExpression</Operator>

              <Pattern>(^.*14424 and (not ^.*\n.*14424)) or (^.*14424.*\n.*14424)</Pattern>

            </RegExExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>0</Severity>

      <AlertOwner>$Data/PublisherName$</AlertOwner>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2000.The_database_is_already_involved_in_log_shipping.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>