This issue is related to solr, When solr create indexes, Solr make connection with alfresco to get all transactions to create index, By default it ask for all the transactions and alfresco reply with all transaction ids. If some node is deleted, its details go to archive folder. but if there are some reference remain for deleted node then scheduler will unable to clean it and throw this exception. To solve this issue just delete that transaction id. But when you try to delete transaction id from alf_transaction table, it always throw foreign key constraints. To resolve this just take database backup and drop below foreign key constraints and recreate them with cascade effect.
(`alfresco400dev`.`alf_node`, CONSTRAINT `fk_alf_node_txn` FOREIGN KEY (`transaction_id`) REFERENCES `alf_transaction` (`id`))
ALTER TABLE alf_node DROP CONSTRAINT fk_alf_node_txn;
ALTER TABLE alf_node
ADD CONSTRAINT fk_alf_node_txn FOREIGN KEY (transaction_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
(`alfresco400dev`.`alf_child_assoc`, CONSTRAINT `fk_alf_cass_cnode` FOREIGN KEY (`child_node_id`) REFERENCES `alf_node` (`id`))
ALTER TABLE alf_child_assoc DROP CONSTRAINT fk_alf_cass_cnode;
ALTER TABLE alf_child_assoc
ADD CONSTRAINT fk_alf_cass_cnode FOREIGN KEY (child_node_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
(`alfresco400dev`.`alf_node_aspects`, CONSTRAINT `fk_alf_nasp_n` FOREIGN KEY (`node_id`) REFERENCES `alf_node` (`id`))
ALTER TABLE alf_node_aspects DROP CONSTRAINT fk_alf_nasp_n;
ALTER TABLE alf_node_aspects
ADD CONSTRAINT fk_alf_nasp_n FOREIGN KEY (node_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
(`alfresco400dev`.`alf_node_properties`, CONSTRAINT `fk_alf_nprop_n` FOREIGN KEY (`node_id`) REFERENCES `alf_node` (`id`))
ALTER TABLE alf_node_properties DROP CONSTRAINT fk_alf_nprop_n;
ALTER TABLE alf_node_properties
ADD CONSTRAINT fk_alf_nprop_n FOREIGN KEY (node_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
delete from alf_transaction where id = 42057
then configure alfresco for not to provide deleted node for indexing by putting below property -
index.tracking.minRecordPurgeAgeDays=0
Now on solr machine call this url -
http://solrhostname:8080/solr/admin/cores?action=FIX
Now delete solr indexes and recreate them.
Now your problem will disappear (it worked for me).
(`alfresco400dev`.`alf_node`, CONSTRAINT `fk_alf_node_txn` FOREIGN KEY (`transaction_id`) REFERENCES `alf_transaction` (`id`))
ALTER TABLE alf_node DROP CONSTRAINT fk_alf_node_txn;
ALTER TABLE alf_node
ADD CONSTRAINT fk_alf_node_txn FOREIGN KEY (transaction_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
(`alfresco400dev`.`alf_child_assoc`, CONSTRAINT `fk_alf_cass_cnode` FOREIGN KEY (`child_node_id`) REFERENCES `alf_node` (`id`))
ALTER TABLE alf_child_assoc DROP CONSTRAINT fk_alf_cass_cnode;
ALTER TABLE alf_child_assoc
ADD CONSTRAINT fk_alf_cass_cnode FOREIGN KEY (child_node_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
(`alfresco400dev`.`alf_node_aspects`, CONSTRAINT `fk_alf_nasp_n` FOREIGN KEY (`node_id`) REFERENCES `alf_node` (`id`))
ALTER TABLE alf_node_aspects DROP CONSTRAINT fk_alf_nasp_n;
ALTER TABLE alf_node_aspects
ADD CONSTRAINT fk_alf_nasp_n FOREIGN KEY (node_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
(`alfresco400dev`.`alf_node_properties`, CONSTRAINT `fk_alf_nprop_n` FOREIGN KEY (`node_id`) REFERENCES `alf_node` (`id`))
ALTER TABLE alf_node_properties DROP CONSTRAINT fk_alf_nprop_n;
ALTER TABLE alf_node_properties
ADD CONSTRAINT fk_alf_nprop_n FOREIGN KEY (node_id)
REFERENCES alf_node (id)
ON DELETE CASCADE
delete from alf_transaction where id = 42057
then configure alfresco for not to provide deleted node for indexing by putting below property -
index.tracking.minRecordPurgeAgeDays=0
Now on solr machine call this url -
http://solrhostname:8080/solr/admin/cores?action=FIX
Now delete solr indexes and recreate them.
Now your problem will disappear (it worked for me).
