KX Community

Find answers, ask questions, and connect with our KX Community around the world.
KX Community Guidelines

Home › Forums › KX Solutions › dxATAlert table grown too big › Re: dxATAlert table grown too big

  • cj

    Member
    July 5, 2022 at 12:00 am

    Thanks a lot David for the quick response.

    I think my HDB is corrupt, when I try to access dxATAlert on action tracker HDB, it gives a “type” error? Can this be related with the Kx version where syms were updated to String instead of symbols? Or does it mean that because nothing has ever been EODed successfully so far, so there is nothing in the HDB at all?

    Also, tried to close one item from AT dashboard and manually triggered dxATEOD1[.z.d], this resulted in removing that item from the dashboard but following error occurred on the action tracker process.

     

    ERROR. ### (3317156): Failed to connect to :hostname:port for HDB reload ### “access”

    Any idea why would this be occurring?

     

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member

Please allow a few minutes for this process to complete.

Report

You have already reported this .