Last Modified: Nov 22, 2021
Known Affected Versions:
11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
11.5.0, 11.4.0 HF6
Opened: Oct 14, 2013 Severity: 3-Major Related Article:
Related Article: K33516353
DCC error: Cannot add or update a child row: a foreign key constraint fails. The following messages appear in /var/log/ts/dcc.log: dcc|INFO|Oct 01 14:00:00.288|11314| [DB::add_client_side_drop_data_entry, ] The table CLIENT_SIDE_DROPPED_STAT is empty. dcc|ERR|Oct 01 14:00:00.321|11314| [DB::insert_ev_client_side_dropped_data_reporting, ] mysql_stmt_execute, failed. dcc|ERR|Oct 01 14:00:00.321|11314| [DB::insert_ev_client_side_dropped_data_reporting, ] Cannot add or update a child row: a foreign key constraint fails =(`DCC`.`CLIENT_SIDE_DROPPED_STAT`, CONSTRAINT `CLIENT_SIDE_DROPPED_STAT_ibfk_1` FOREIGN KEY (`account_id`) REFERENCES `ACCOUNTS` (`account_id`) ON DELETE ). dcc|INFO|Oct 01 14:00:00.321|11314| [DB::insert_ev_client_side_dropped_data_reporting, ] invalid affected rows by MySQL.
The error message is mostly benign. It occurs on storing counters for web scraping attacks to the database, and could include records for multiple policies in a single update. If the failing record were inserted in a batch, all records in the batch will be silently lost. However, under most conditions, individual records will be saved, so this is unlikely to have an impact.
After upgrading, ASM keeps logging error messages, but there is no impact on the traffic.
Run the following command: bigstart restart asm.
The system no longer sends multiple error messages in asm.log when client-side statistics are updated for a non-existent account.