Unable to synchronize with DA

book

Article ID: 35835

calendar_today

Updated On:

Products

CA Infrastructure Management CA Infrastructure Management CA Performance Management - Usage and Administration CA Performance Management - Data Polling

Issue/Introduction

Problem: 

I have an instance of Performance Center that I have upgraded to 2.6.0.68, and am attempting to synchronize with a newly installed Data Aggregator 2.6.0.104. 

Before I started the upgrade, I got the following error when attempting to backup the database on Performance Center: 

Table './netqosportal/data_source_log' is marked as crashed and should be repaired 

I didn't have any data to backup, since this is a test system, so I went forward with the upgrade to 2.3.4, then 2.6.0.68. Now, when I add the new Data Aggregator as a Data Source, I get Synchronization Failure message, and when I look in the PC logs, I see the same error message about the /netqosportal/data_source_log. 

 

Environment: 

CA Infrastructure Performance Release:2.6

LINUX

 

Resolution/Workaround: 

  1. Stop all the CAPC processes:

    service caperfcenter_console stop 
    service caperfcenter_devicemanager stop 
    service caperfcenter_eventmanager stop 
    service caperfcenter_sso stop

     

  2. Collect CA Remote Engineer data: 
    Note: Make sure the MySQL error file is contained in the Remote Engineer file when it is uploaded. It will be named with the hostname of the CAPC server and have the extension ".err". If it is in a non-standard location on the customers system, please have them upload it separately.

     

  3. Start the mysql client by typing mysql at the command line:

    [[email protected]_machine ~]# mysql 
    Welcome to the MySQL monitor. Commands end with ; or \g. 
    Your MySQL connection id is 2615 
    Server version: 5.6.10-enterprise-commercial-advanced MySQL Enterprise Server - Advanced Edition (Commercial) 

    Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved. 

    Oracle is a registered trademark of Oracle Corporation and/or its 
    affiliates. Other names may be trademarks of their respective 
    owners. 

    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. 

    mysql>

     

  4. Based on the database that contains the error, you must switch to that database. The database is in the error (em or netqosportal)

    mysql> use em; 
    Database changed 
    mysql>

     

  5. You should run a check against the table in question, this should indicate that it has issues. Your errors may be different depending on what sort of corruption occurred.

    mysql> CHECK TABLE event_properties; 
    +---------------------+-------+----------+------------------------------------------------------------------------------------+ 
    | Table | Op | Msg_type | Msg_text | 
    +---------------------+-------+----------+------------------------------------------------------------------------------------+ 
    | em.event_properties | check | Error | Incorrect key file for table './em/event_properties#P#p20140721'; try to repair it | 
    | em.event_properties | check | Error | Incorrect key file for table 'event_properties'; try to repair it | 
    | em.event_properties | check | error | Corrupt | 
    +---------------------+-------+----------+------------------------------------------------------------------------------------+ 
    3 rows in set (0.00 sec)

     

  6. Now, you need to repair the table. We repair the entire table, even if it is partitioned. This may take several minutes or longer, depending on the size of the table.

    mysql> REPAIR TABLE event_properties; 
    +---------------------+--------+----------+--------------------------------------+ 
    | Table | Op | Msg_type | Msg_text | 
    +---------------------+--------+----------+--------------------------------------+ 
    | em.event_properties | repair | warning | Number of rows changed from 0 to 965 | 
    | em.event_properties | repair | status | OK | 
    +---------------------+--------+----------+--------------------------------------+ 
    2 rows in set (0.00 sec)

    You should see statements indicating what was fixed, and a statement indicating "OK", that the table was successfully repaired. Repeat the procedure on any other tables giving similar errors. If a table cannot be repaired, it will be necessary to open a defect with engineering, containing the results of "CHECK TABLE" and "REPAIR TABLE" commands.

     

  7. Once all tables are repaired, You may restart all the CAPC processes:

    service caperfcenter_sso start 
    service caperfcenter_eventmanager start 
    service caperfcenter_devicemanager start 
    service caperfcenter_console start

Environment

Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator
Component: