Confluence 6 针对 key "cp_" 或 "cps_" 的 "Duplicate Entry" 问题解决

若是你遇到了下面的错误信息,例如:sql

com.atlassian.confluence.importexport.ImportExportException: Unable to complete import because the data does not match the constraints in the Confluence schema. Cause: MySQLIntegrityConstraintViolationException: Duplicate entry '1475804-Edit' for key 'cps_unique_type'

上面表示在 XML 的备份文件中恢复的数据库没有正确的权限,一般是由于使用了第三方的插件的缘由。这个问题在 Confluence 3.5.2 的后续版本中已经修复了,请参考 CONF-22123 中的说明。若是你的版本已是新的版本了,你的导出文件可能须要手动进行修改来删除掉重复权限实例,或者整个记录都须要被删除。下面的 SQL 能够被用来找到这个记录。数据库

SELECT * FROM CONTENT_PERM WHERE USERNAME IS NULL AND GROUPNAME IS NULL ;
 
FROM CONTENT_PERM cp
WHERE cp.USERNAME IS NOT NULL AND cp.GROUPNAME IS NOT NULL ;
 
SELECT cps1.ID, cps1.CONTENT_ID, cps1.CONT_PERM_TYPE FROM CONTENT_PERM_SET cps1, CONTENT_PERM_SET cps2
WHERE cps1.ID <> cps2.ID AND
 
( SELECT scps.ID FROM CONTENT_PERM_SET scps WHERE scps.CONTENT_ID = cps.CONTENT_ID AND scps.CONT_PERM_TYPE = cp.CP_TYPE) AS suggested_cps_id
FROM CONTENT_PERM cp, CONTENT_PERM_SET cps
WHERE cp.CPS_ID = cps.ID AND
 
FROM CONTENT_PERM cp1, CONTENT_PERM_SET cps1, CONTENT_PERM cp2, CONTENT_PERM_SET cps2
WHERE
cp1.ID <> cp2.ID AND
 
FROM CONTENT_PERM cp1, CONTENT_PERM_SET cps1, CONTENT_PERM cp2, CONTENT_PERM_SET cps2
WHERE
cp1.ID <> cp2.ID AND
 
SELECT * FROM CONTENT_PERM_SET
WHERE ID NOT IN ( SELECT DISTINCT CPS_ID FROM CONTENT_PERM);

删除全部找到的记录,而后尝试从新导出。eclipse

 

https://www.cwiki.us/display/CONFLUENCEWIKI/Troubleshooting+XML+backups+that+fail+on+restorespa

相关文章
相关标签/搜索