The Data Protection Manager database grows and the console crashes after installing Update Rollup 3

Symptoms

After installing Update Rollup 3 for System Center 2012 Data Protection Manager you notice that the DPM database grows and eventually the DPM console will crash.

Cause

This issue is caused by a regression introduced in Update Rollup 3 for System Center 2012 Data Protection Manager.

Resolution

This issue has been corrected in System Center 2012 Data Protection Manager 2012 Service Pack 1 (SP1) or you can use the following workaround:

1. Backup the DPM Database.

2. Execute the following SQL stored procedure:

USE [DPMDB]
GO
/****** Object:  StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update]    Script Date: 11/03/2012 01:36:08 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update]
(
    @Caption                        nvarchar(40),
    @ComponentType                  nvarchar(16),
    @RecoverableObjectId            BIGINT
)
AS
    DECLARE @error INT,
            @rowCount INT
    SET @error = 0

    SET NOCOUNT ON

    -- UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption        
    UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption,
                ComponentType = @ComponentType        
    WHERE RecoverableObjectId = @RecoverableObjectId

    SELECT @error = dbo.udf_DPS_CheckRowCount(1)

    SET NOCOUNT OFF
RETURN @error

3. Finally, execute this following stored procedure.

USE [DPMDB]
GO
UPDATE tbl_PRM_DatasourceConfigInfo
SET ROCatalogCheckPoint = NULL
WHERE DatasourceId IN
(SELECT DISTINCT ReferentialDatasourceId FROM tbl_IM_ProtectedObject
WHERE ReferentialDatasourceId <> NULL)
GO

Properties

Article ID: 2809773 - Last Review: Jan 28, 2013 - Revision: 1

Microsoft System Center 2012 Data Protection Manager

Feedback