Post reply

Error 32023 while editing the Log Shipping Configuration

  • December 23, 2008 at 4:43 am

    #216861

    Hi,

    I am trying to change the configuration for log shipping on the primary server I get the following error.

    An entry for primary server (PrimaryServerName)primary database (PrimaryDatabaseName) does not exist on this secondary. (Microsoft SQL Server, Error: 32023)

    Please suggest how to change the configuration after the log shipping has already been setup.

  • December 30, 2008 at 11:33 am

    #919173

    What configuration you want to change?

  • January 2, 2009 at 1:13 am

    #920116

    I want to change two settings for the Log Shipping Configuration --

    1. Delete Files Older Than setting for the LS_Backup Job

    2. Delete Copied FIles Older Than setting for the LS_Copied Job

    Do I need to Remove the LS configuration totally and reconfigure?

    TIA

  • January 2, 2009 at 11:22 am

    #920453

    You don't have to reconfigure entire logshipping for this.

    You can change the settings in 2 different ways.

    1st Method.

    1st step Execute this command on your primary server for changing retention value of backup files on primary server

    exec master.dbo.sp_change_log_shipping_secondary_database @database =

    2nd step.

    Execute this command on your secondary server for changing retention value of copied backup files on secondary server

    exec master.dbo.sp_change_log_shipping_secondary_primary

    @primary_server = ,

    @primary_database = ,

    @file_retention_period =

    2nd Method.

    Right click database for which value needs to be changed then select tasks and ship Transaction logs.

    Logshipping configuration window pops up.

    For deleting files on primary server, click the backup setting and modify the value under delete files older than heading.

    For deleting files on secondary server, click secondary server ellipsis button for which value needs to be changed here modify the value under copy files.

  • January 3, 2009 at 9:05 am

    #920693

    http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=117064

  • January 3, 2009 at 9:07 am

    #920694

    Thanks but I already got it fixed using UI.

    http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=117064

  • May 31, 2011 at 3:03 am

    #1331846

    I am getting same error when I am changing from restoring mode to readonly mode.

    Thanks

  • May 31, 2011 at 3:47 am

    #1331855

    It has now showing in Readonly/Standby mode automatically.

    Thanks

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply