Strange dublicated records in database

[R1BLH]

Often when searching for a QSO in the logbook there are duplicate records of the same QSO, with different QSL information.

In the database in this case is found two lines corresponding to the same QSO. An example of a query and result lines is given below.

SELECT * FROM TABLE_HRD_CONTACTS_V01 WHERE COL_CALL = 'RA1OHX' AND COL_BAND = '80m' AND COL_MY_GRIDSQUARE = 'KP50DA'

INSERT INTO `TABLE_HRD_CONTACTS_V01` (`COL_PRIMARY_KEY`, `COL_ADDRESS`, `COL_AGE`, `COL_A_INDEX`, `COL_ANT_AZ`, `COL_ANT_EL`, `COL_ANT_PATH`, `COL_ARRL_SECT`, `COL_BAND`, `COL_BAND_RX`, `COL_BIOGRAPHY`, `COL_CALL`, `COL_CHECK`, `COL_CLASS`, `COL_CNTY`, `COL_COMMENT`, `COL_CONT`, `COL_CONTACTED_OP`, `COL_CONTEST_ID`, `COL_COUNTRY`, `COL_CQZ`, `COL_DISTANCE`, `COL_DXCC`, `COL_EMAIL`, `COL_EQ_CALL`, `COL_EQSL_QSLRDATE`, `COL_EQSL_QSLSDATE`, `COL_EQSL_QSL_RCVD`, `COL_EQSL_QSL_SENT`, `COL_EQSL_STATUS`, `COL_FORCE_INIT`, `COL_FREQ`, `COL_FREQ_RX`, `COL_GRIDSQUARE`, `COL_HEADING`, `COL_IOTA`, `COL_ITUZ`, `COL_K_INDEX`, `COL_LAT`, `COL_LON`, `COL_LOTW_QSLRDATE`, `COL_LOTW_QSLSDATE`, `COL_LOTW_QSL_RCVD`, `COL_LOTW_QSL_SENT`, `COL_LOTW_STATUS`, `COL_MAX_BURSTS`, `COL_MODE`, `COL_MS_SHOWER`, `COL_MY_CITY`, `COL_MY_CNTY`, `COL_MY_COUNTRY`, `COL_MY_CQ_ZONE`, `COL_MY_GRIDSQUARE`, `COL_MY_IOTA`, `COL_MY_ITU_ZONE`, `COL_MY_LAT`, `COL_MY_LON`, `COL_MY_NAME`, `COL_MY_POSTAL_CODE`, `COL_MY_RIG`, `COL_MY_SIG`, `COL_MY_SIG_INFO`, `COL_MY_STATE`, `COL_MY_STREET`, `COL_NAME`, `COL_NOTES`, `COL_NR_BURSTS`, `COL_NR_PINGS`, `COL_OPERATOR`, `COL_OWNER_CALLSIGN`, `COL_PFX`, `COL_PRECEDENCE`, `COL_PROP_MODE`, `COL_PUBLIC_KEY`, `COL_QSLMSG`, `COL_QSLRDATE`, `COL_QSLSDATE`, `COL_QSL_RCVD`, `COL_QSL_RCVD_VIA`, `COL_QSL_SENT`, `COL_QSL_SENT_VIA`, `COL_QSL_VIA`, `COL_QSO_COMPLETE`, `COL_QSO_RANDOM`, `COL_QTH`, `COL_RIG`, `COL_RST_RCVD`, `COL_RST_SENT`, `COL_RX_PWR`, `COL_SAT_MODE`, `COL_SAT_NAME`, `COL_SFI`, `COL_SIG`, `COL_SIG_INFO`, `COL_SRX`, `COL_SRX_STRING`, `COL_STATE`, `COL_STATION_CALLSIGN`, `COL_STX`, `COL_STX_STRING`, `COL_SWL`, `COL_TEN_TEN`, `COL_TIME_OFF`, `COL_TIME_ON`, `COL_TX_PWR`, `COL_WEB`, `COL_USER_DEFINED_0`, `COL_USER_DEFINED_1`, `COL_USER_DEFINED_2`, `COL_USER_DEFINED_3`, `COL_USER_DEFINED_4`, `COL_USER_DEFINED_5`, `COL_USER_DEFINED_6`, `COL_USER_DEFINED_7`, `COL_USER_DEFINED_8`, `COL_USER_DEFINED_9`, `COL_CREDIT_GRANTED`, `COL_CREDIT_SUBMITTED`, `COL_ADDRESS_INTL`, `COL_AWARD_GRANTED`, `COL_AWARD_SUBMITTED`, `COL_CLUBLOG_QSO_UPLOAD_DATE`, `COL_CLUBLOG_QSO_UPLOAD_STATUS`, `COL_COMMENT_INTL`, `COL_COUNTRY_INTL`, `COL_SILENT_KEY`, `COL_SKCC`, `COL_DARC_DOK`, `COL_FISTS`, `COL_FISTS_CC`, `COL_HRDLOG_QSO_UPLOAD_DATE`, `COL_HRDLOG_QSO_UPLOAD_STATUS`, `COL_MY_ANTENNA`, `COL_MY_ANTENNA_INTL`, `COL_MY_CITY_INTL`, `COL_MY_COUNTRY_INTL`, `COL_MY_DXCC`, `COL_MY_FISTS`, `COL_MY_IOTA_ISLAND_ID`, `COL_MY_NAME_INTL`, `COL_MY_POSTCODE_INTL`, `COL_MY_RIG_INTL`, `COL_MY_SIG_INTL`, `COL_MY_SIG_INFO_INTL`, `COL_MY_SOTA_REF`, `COL_MY_STREET_INTL`, `COL_MY_USACA_COUNTIES`, `COL_MY_VUCC_GRIDS`, `COL_NAME_INTL`, `COL_NOTES_INTL`, `COL_QRZCOM_QSO_UPLOAD_DATE`, `COL_QRZCOM_QSO_UPLOAD_STATUS`, `COL_QSO_DATE`, `COL_QSO_DATE_OFF`, `COL_QTH_INTL`, `COL_REGION`, `COL_RIG_INTL`, `COL_SIG_INTL`, `COL_SIG_INFO_INTL`, `COL_SOTA_REF`, `COL_SUBMODE`, `COL_UKSMG`, `COL_USACA_COUNTIES`, `COL_VUCC_GRIDS`, `station_id`, `COL_WWFF_REF`, `COL_MY_WWFF_REF`, `COL_POTA_REF`, `COL_MY_POTA_REF`, `COL_QRZCOM_QSO_DOWNLOAD_DATE`, `COL_QRZCOM_QSO_DOWNLOAD_STATUS`) VALUES
(2218, '', NULL, NULL, NULL, NULL, NULL, '', '80m', '', '', 'RA1OHX', '', '', 'AR,', 'Distance: 499 km', 'EU', '', '', 'European Russia', 16, 498.8, '54', '', '', NULL, '2022-12-21 13:49:36', 'N', 'Y', '', NULL, 3574968, 0, 'KP91LM', NULL, '', NULL, NULL, NULL, NULL, '2022-12-21 00:00:00', '2022-12-21 13:48:49', 'Y', 'Y', '', NULL, 'FT8', '', 'Saint-Petersburg', '', 'EUROPEAN RUSSIA', 16, 'KP50DA', '', 29, NULL, NULL, '', '', '', '', '', '', '', 'Mikhail A. Ershov', '', NULL, NULL, 'R1BLH', '', '', '', '', '', '', '2023-01-10 08:36:46', '2023-01-10 08:36:46', 'Y', 'E', 'Y', 'E', '', '', NULL, 'Kargopol, Arkhangelskaya obl,164110', '', '-11', '-13', NULL, '', '', NULL, '', '', NULL, '', 'AR', 'R1BLH', NULL, '', NULL, NULL, '2022-12-18 19:40:14', '2022-12-18 19:39:15', NULL, '', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '', '', '', '', '', '2023-07-19 00:00:00', 'Y', '', '', '', '', '', NULL, NULL, NULL, '', '', '', '', NULL, 54, NULL, '', '', '', '', '', '', '', '', '', '', '', '', NULL, 'M', '2022-12-18', '2022-12-18', '', '', '', '', '', '', NULL, '', '', '', 25, '', '', '', NULL, NULL, NULL),
(3787, '', NULL, NULL, NULL, NULL, NULL, '', '80m', '', '', 'RA1OHX', '', '', '', 'Distance: 499 km', 'EU', '', '', 'European Russia', 16, 498.8, '54', '', '', NULL, '2023-02-22 22:58:41', NULL, 'Y', '', NULL, 3574968, NULL, 'KP91LM', NULL, '', 19, NULL, NULL, NULL, '2023-12-27 00:00:00', '2023-02-22 22:56:08', 'Y', 'Y', '', NULL, 'FT8', '', 'Saint-Petersburg', '', 'EUROPEAN RUSSIA', 16, 'KP50DA', '', 29, NULL, NULL, '', '', '', '', '', '', '', '', '', NULL, NULL, '', '', '', '', '', '', '', NULL, NULL, 'N', '', 'N', '', '', '', NULL, '', '', '-11', '-13', NULL, '', '', NULL, '', '', NULL, '', 'AR', 'R1BLH', NULL, '', NULL, NULL, '2022-12-18 19:40:14', '2022-12-18 19:39:15', NULL, '', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '', '', '', '', '', '2023-12-27 00:00:00', 'Y', '', '', '', '', '', NULL, NULL, NULL, '', '', '', '', NULL, 54, NULL, '', '', '', '', '', '', '', '', '', '', '', '', NULL, '', '2022-12-18', '2022-12-18', '', '', '', '', '', '', '', '', '', '', 25, '', '', '', '', NULL, NULL);

In this case, when searching for duplicates in this station location, this callsign is not found in the list of duplicates.

How to diagnose and correct this situation?

[magicbug]

How are you inserting FT8 QSOs?

[R1BLH]

I'm using the GridTracker.
I tried Cloudlog Aurora but it does not work in my case (I have no idea why).

[magicbug]

It would suggest GridTracker is either sending the QSO twice or your saving the QSO twice inside WSJT-X

[R1BLH]

It's very strange. I do not manually save QSOs to the JTDX log. If there was a Gridtracker sending QSOs to the log twice, the COL_PRIMARY_KEY values would be consistent, and they differ by almost 1500. It is possible that there was an import error when searching for duplicates.
If you now search for duplicate QSOs, these records will not show up in the results. Found only when processing QSLs, when searching by callsign.