We are running DPA 2025.3 against AWS RDS PostgreSQL database at version 14.17. We see these persistent errors coming from the PREPARE dpaprepare() statement sent by the monitor utility. How do we resolve (or interpret) these errors? Is there anything we need to configure?
2025-10-21 23:03:27 UTC:10.115.16.33(49723):solarwindsdpa_monitor@prd _fad_db:[22271]:ERROR: relation "location_summary" does not exist at character 206
2025-10-21 23:03:27 UTC:10.115.16.33(49723):solarwindsdpa_monitor@prd _fad_db:[22271]:STATEMENT: PREPARE dpaprepare(unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown) as SELECT DISTINCT LS.DRO_PUBLIC_ID, LS.PSL_LATITUDE,LS.PSL_LONGITUDE, null FROM LOCATION_SUMMARY LS JOIN PPID_NETWORK_ASSOCIATION NWK ON LS.DRO_PUBLIC_ID = NWK.DRO_PUBLIC_ID AND NWK.PRODUCT_PROVIDER_NETWORK_ID in ($1,$2,$3,$4) AND NWK.PSL_DISPLAY_IND='R' WHERE LS.PSL_LATITUDE>$5 AND LS.PSL_LATITUDE<$6 AND LS.PSL_LONGITUDE>$7 AND LS.PSL_LONGITUDE<$8 AND LS.DRO_TYP_CD IN ($9,$10,$11,$12,$13)
2025-10-21 23:03:27 UTC:10.115.16.33(52799):solarwindsdpa_monitor@prd _fad_db:[4409]:ERROR: relation "location_summary" does not exist at character 244
2025-10-21 23:03:27 UTC:10.115.16.33(52799):solarwindsdpa_monitor@prd _fad_db:[4409]:STATEMENT: PREPARE dpaprepare(unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown,unknown) as SELECT DISTINCT LS.DRO_PUBLIC_ID, LS.PSL_LATITUDE,LS.PSL_LONGITUDE, CASE when PB.DRO_VALUE_AVP is NULL then 'N' else 'Y' end DPA_PRMR_APLY_CD FROM LOCATION_SUMMARY LS JOIN PPID_NETWORK_ASSOCIATION NWK ON LS.DRO_PUBLIC_ID = NWK.DRO_PUBLIC_ID AND NWK.PRODUCT_PROVIDER_NETWORK_ID in ($1,$2,$3,$4) AND NWK.PSL_DISPLAY_IND='R' LEFT OUTER JOIN LOCATION_EXTRA PB ON LS.DRO_PUBLIC_ID = PB.DRO_PUBLIC_ID AND PB.DRO_ATTRIBUTE_AVP ='BNFT' and PB.DRO_VALUE_AVP ='PB' WHERE LS.PSL_LATITUDE>$5 AND LS.PSL_LATITUDE<$6 AND LS.PSL_LONGITUDE>$7 AND LS.PSL_LONGITUDE<$8 AND LS.DRO_TYP_CD IN ($9,$10,$11,$12,$13)
