Home › Forums › KX Solutions › dxATAlert table grown too big › Re: dxATAlert table grown too big
-
Hi cj,
- For this you will need to check the AT HDB directory on disk to find out if it exists; if it does then you should run some checks to determine if source of the type
- You would need to check the process log of the AT to see which HDB’s it’s tried to reload. In some misconfigurations it’s possible that an HDB outside of the AT workflow is being picked up and the AT is trying to connect to that permissioned HDB to reload (which it doesn’t have access to)
Hope the above helps your initial investigation