DX Unified Infrastructure Management

 View Only
  • 1.  custom query and check point - query is coming up blank and checkpoint as not active chcked - Sql servr probe

    Posted Oct 14, 2020 03:21 AM

    I tested it on the probe on many servers, I am getting the output as expected.
    But when I use it for bulk deployment via CFX it comes up blank.
    What am i missing cant understand....



    <checkpoints> overwrite
    <Back_up_Status> overwrite
    active = yes
    description =
    qos = no
    qos_list = yes
    interval = 15 sec
    sql_timeout =
    scheduling = rules
    use_exclude = no
    use_include = no
    exclude_defs = yes
    include_defs = yes
    samples = 1
    send_alarm = yes
    query_checksum = h4DSX9OoVT2e5RSMquehGfPBzFAFMQcnbXmFS6SiD4M=
    type = 12
    column = minutes
    key = $minutes
    msg_variables = $db_name.c;$minutes.i;$days_sincebackup.i;$state_desc.c;$time.i;$profile.x;$check.x;$instance.x
    query_file = backup_status
    interval_modus = no
    query_uid =
    <thresholds>
    <minutes>
    <default>
    <0>
    tagid = 0
    value = 10
    unit =
    sev = major
    msg = database_backup_status_critical
    condition = >=
    clear_msg = database_backup_status_clear
    scheduling = rules
    key_col_name =
    key_col_value = default
    </0>
    </default>
    </minutes>
    </thresholds>
    </Back_up_Status>
    <db2> overwrite
    active = yes
    description =
    qos = no
    qos_list = yes
    interval =
    sql_timeout =
    scheduling = rules
    use_exclude = no
    use_include = no
    exclude_defs = yes
    include_defs = yes
    samples = 1
    send_alarm = yes
    query_checksum = 9V/QZpow4fz8QTBSmI1Xs7i5eg9Gh8CPbk/OvEOy9/Y=
    type = 12
    column = state
    key = $state
    msg_variables = $db_name.c;$state.i;$profile.x;$check.x;$instance.x
    query_file = db_status
    interval_modus = no
    query_uid =
    <thresholds>
    <state>
    <0>
    tagid = 0
    value = 0
    unit =
    sev = warning
    msg = database_backup_status_critical
    condition = =
    clear_msg = dbstatus2
    scheduling = rules
    key_col_name = state
    key_col_value = 0
    </0>
    </state>
    </thresholds>
    </db2>
    </checkpoints>


    ------------------------------
    HCL Technologies
    ------------------------------


  • 2.  RE: custom query and check point - query is coming up blank and checkpoint as not active chcked - Sql servr probe

    Broadcom Employee
    Posted Oct 14, 2020 09:03 AM

    So I am not sure you can do a bulk config of a custom checkpoint.
    The reason being is the probe stores and MD5 Hash of the custom checkpoint after it is tested in the GUI.
    Once this is done then every time the checkpoint is run this is checked against the local file to make sure it has not been tampered with as a security measure.
    When you create this on one system but then copy it to another this will cause the MD5 hash to change and so when deployed to a new system the checkpoint will not be executed.

    You should be able to see this happening in the loglevel 5 logs.

    Maybe some others have found a way to get this to work and can comment further.



    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: custom query and check point - query is coming up blank and checkpoint as not active chcked - Sql servr probe

    Posted Oct 14, 2020 12:51 PM
    i played here and there 
    I now see the checkpoint and query is also populating , but in the template it is not coming up as active even after i have put it like ACTIVE =YES in cfx



    ------------------------------
    HCL Technologies
    ------------------------------



  • 4.  RE: custom query and check point - query is coming up blank and checkpoint as not active chcked - Sql servr probe

    Broadcom Employee
    Posted Oct 14, 2020 12:53 PM

    this is expected because of the MD5 Hash check.

    If you check the loglevel 5 logs you will see that is says the MD5 Hash does not match and will not process.



    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 5.  RE: custom query and check point - query is coming up blank and checkpoint as not active chcked - Sql servr probe

    Posted Oct 14, 2020 01:01 PM
    something similar we already worked on in previous org. for oracle probe and it is working successfully for bulk deployments .

    This is what i can see in the logs
    Oct 14 18:44:45:366 [14524] sqlserver: Checking no migration will be performed in this run
    Oct 14 18:44:45:397 sqlserver: (NimCryptographerCfgKeyReadEncryptedValue) failed to decrypt value. RC=3
    Oct 14 18:44:45:397 sqlserver: (NimCryptographerCfgKeyReadEncryptedValue) failed to decrypt value. RC=3
    Oct 14 18:44:45:397 sqlserver: Profile: test/db_status, query checksum is not correct, query might have been manipulated - checkpoint deactivated
    Oct 14 18:44:45:397 sqlserver: fwSave_alarm - called with invalid parameter
    Oct 14 18:44:45:397 sqlserver: fwCreateCheckpoint active no
    Oct 14 18:44:45:397 sqlserver: Profile: test/db_backup_status, query checksum is not correct, query might have been manipulated - checkpoint deactivated
    Oct 14 18:44:45:413 sqlserver: fwSave_alarm - called with invalid parameter
    Oct 14 18:44:45:413 sqlserver: fwCreateCheckpoint active no

    ------------------------------
    HCL Technologies
    ------------------------------



  • 6.  RE: custom query and check point - query is coming up blank and checkpoint as not active chcked - Sql servr probe

    Posted Oct 15, 2020 10:26 AM
    I had a similar experience with the oracle probe while updating custom queries. I was able to get it working by retrieving a new checksum from the probe and then updating the CFX file with that. It was never clear to me why the first checksum didn't work, but I always guessed it had something to do with file formatting being slightly different in the one the probe created when I pasted in the query and the one that got pushed out via the package with the CFX file. (Could have been line endings or something else.) Not sure if you've tried this approach already, but it was a simple fix even though inconvenient because I always had to update the package twice to get it working.

    -Keith