When checking Control-M/Server Mirroring Status via ctm_menu the following message appears: Mirroring is damaged

Version 1

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Control-M/Server for UNIX and Microsoft Windows


    Control-M/Server for UNIX and Microsoft Windows


    Control-M/Server for UNIX and Microsoft Windows 7.0.00, 8.0.00, 9.0.00 All operating systems and databases


    When using Control-M server with mirroring you may experience the error message "Mirroring is damaged" while checking mirror status.
    Within the Control-M server logs in ctm_server/proclog, you'll receive error messages from the database.

    Example from an Oracle database:

    0124 10:48:21.903 U_CTMCREATE46535: checkerr(StructLogin=0x1486fa0) - Error, ORA-28547: connection to server failed, probable Oracle Net admin error
    0124 10:48:21.903 U_CTMCREATE46535: DB_GetDBproc() - Failed in OCISessionBegin
    0124 10:48:22.313 U_CTMCREATE46535: checkerr(StructLogin=0x14bcd00) - Error, ORA-01013: user requested cancel of current operation
    0124 10:48:22.313 U_CTMCREATE46535: DB_ExecSelect() - Failed in OCIStmtExecute
    0124 10:48:22.313 U_CTMCREATE46535: GM_SYSPRM_read: failed in DB_GEN_CMS_SYSPRM_select_ini
    0124 10:48:22.313 U_CTMCREATE46535: CTM6337 -> GM_PROC_prolog_common : Failed to open CMS_SYSPRM table

    Process for checking Mirror Status from ctm_menu

    ctm_menu > Database Mirroring > Check Mirroring Status

    Database Mirroring Menu (Primary Environment)
    Select one of the following options:

    Primary Server Options:
    1 - Check Mirroring Status
    2 - Initialize Mirroring
    3 - Disable Mirroring
    4 - Use Mirror Database
    5 - Restore Control-M Server database from Mirror

    Failover Server Options:
    6 - Initialize Failover
    7 - Start Failover
    8 - Stop Failover
    9 - Disable Failover

    q - Quit

    Enter option number ---> []:1
    Mirroring is damaged


    This problem is likely caused by poor network performance between the Primary Control-M/Server and the Mirror Control-M/Server, but could be caused by many other factors that may not be readily apparent.


    To reduce the chances that the Mirror becomes damaged, set an environment variable on the Primary and Mirrored CONTROL-M/Server to increase the number of retries the CONTROL-M/Server will attempt before marking the Mirror as damaged.

    Contact your local System or CONTROL-M Administrator for assistance in performing this function if you are unsure how or if you are uncomfortable with the steps required to complete this task.
    For Unix Platforms:

         1). Login as the CONTROL-M/Server user.
         2). Modify the $HOME/.cshrc file by adding the following line:
              setenv CTM_MIRROR_RETRY <0-99>.
              Increase the CTM_MIRROR_RETRY value from 10 (seconds default) to 25.  
         3). Save the file
         4). Logout 
         5). Login again as the CONTROL-M/Server User
         6). Stop the CONTROL-M/Server (e.g. shut_ctm)
         7). Start the CONTROL-M/Server (e.g. start_ctm) for the change to take effect.

    Wait for a while and see if the problem reoccurs.
    If it does, increase the value by 25.
    Repeat this process until you reach the maximum.

    For Microsoft Windows Platforms:
    The following solution requires that you modify the registry of your Microsoft Windows computer directly.  Ensure that you have a current backup of your Registry  prior to any modifications.  For information or assistance on how to backup your Registry or how to modify your Registry, contact your local Windows Administrator or Help Desk.

    = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
    WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system.
    Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved.
    Use Registry Editor at your own risk.
    For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.  Note that you should back up the registry before you edit it.  If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD)
    = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

         1). Open the registry editor (regedit or regedt32)
         2). Navigate to HKLM\Software\BMC Software\CONTROL-M/Server\SYSPRM
         3). Right click on SYSPRM
         4). Choose New
         5). Choose String Value
         6). Replace the value: New Value #1 with CTM_MIRROR_RETRY 
         7). Press enter to save
         8). Double click the CTM_MIRROR_RETRY value you just added
         9). In the Value Data field, enter a number for 0 to 99 press enter to save. The default is 10 retries. 
         10). Cycle the CONTROL-M/Server to make the change take effect.
         11). Increase the CTM_MIRROR_RETRY value from 10 to 25.  Wait for a while and see if the problem reoccurs.  If it does, increase the value by 25.  Repeat this process until you reach the maximum.

    Please note: If you do not have access or permissions to modify the Registry, you can set CTM_MIRROR_RETRY as an environment variable on the Microsoft Windows box (as CONTROL-M/Server will look for this if it does not find it in the Registry). 

    You can set environment variables on a Microsoft Windows box from Start -> Settings -> Control Panel -> System -> Advanced (tab) -> Environment Variables. It can be either User environment variable (for the CONTROL-M/Server User), or a System Environment variable. Simply select "New" and add the Variable Name and Variable Value. 

    If you continue to receive Damaged Mirror messages, contact your Network Administrator to determine if there are problems with the Network link between the primary and mirrored CONTROL-M/Server.

    Additional things to check:

    1) Check the network latency between the primary and mirrored Control-M server databases.
    2) Check for any network related issues between the primary and mirrored Control-M server databases.

    3) Check your database logs. If using Oracle, have the DBA team review the listener log files.
    4) Control-M/Server is supplied with a utility called "toolbox" that can be used to perform various tests between the application and the database.


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles