错误:重复的键值违反了唯一约束“ xak1fact_dim_relationship”

如何解决错误:重复的键值违反了唯一约束“ xak1fact_dim_relationship”

| 在删除某些行并根据来自Java的条件更新表时,出现以下错误。我的数据库是PostgreSQL 8.4。下面是错误: 错误:重复的键值违反唯一 约束\“ xak1fact_dim_relationship \” 导致此问题的代码如下:
/**
 * Commits job.  This does the following:
 * <OL>
 *  <LI> cancel previous datamart states </LI>
 *  <LI> drop diabled derived objects </LI>
 *  <LI> flip mirror relationships for objects with next states </LI>
 *  <LI> advance rolloff_state from start1 to complete1,from start2 to complete </LI>
 *  <LI> set 1/0 internal states to 0/-1 </LI>
 *  <LI> remove header objects with no letter rows </LI>
 *  <LI> mark mirror rel as OS if children are missing (e.g.,semantic w/o agg build) </LI>
 *  <LI> mark mirror rel as OS if int-map not in sync with dim base (e.g.,int-map SQL w/o semantic) </LI>
 * </OL>
 */
protected void CommitJobUnprotected()
    throws SQLException
{
    if (_repl.epiCenterCon== null)
        throw makeReplacementError(0);
    boolean oldAutoCommitStatus = _repl.epiCenterCon.getAutoCommit();

    try
    {

        _repl.epiCenterCon.setAutoCommit(false);

        Statement stmt = null;
        boolean committed = false;
        synchronized (SqlRepl.metaChangeLock)
        {
            try
            {
                stmt = _repl.epiCenterCon.createStatement();

                // update internal states for fact_dim_relationship
                metaExec(stmt,\"DELETE from fact_dim_relationship WHERE internal_state = -1 AND \"  +
                                \" EXISTS (SELECT 1 FROM fact_dim_relationship WHERE internal_state = 1)\",\" SELECT 1 from fact_dim_relationship WHERE internal_state = -1 AND \"  +
                                \" EXISTS (SELECT 1 FROM fact_dim_relationship WHERE internal_state = 1)\"); /*1*/
                metaExec( stmt,\"UPDATE fact_dim_relationship SET internal_state = internal_state - 1 \" +
                             \" WHERE EXISTS (SELECT 1 FROM fact_dim_relationship inner1 \" +
                             \"              WHERE inner1.internal_state = 1 \" +
                             \" AND inner1.fact_tbl_key = fact_dim_relationship.fact_tbl_key \" +
                             \" AND inner1.dim_base_key = fact_dim_relationship.dim_base_key ) \",\" SELECT 1 FROM fact_dim_relationship \" +
                             \" WHERE EXISTS (SELECT 1 FROM fact_dim_relationship inner1 \" +
                             \"              WHERE inner1.internal_state = 1 \" +
                             \" AND inner1.fact_tbl_key = fact_dim_relationship.fact_tbl_key \" +
                             \" AND inner1.dim_base_key = fact_dim_relationship.dim_base_key ) \"); /*5*/

                System.out.println(\"Update done on fact_dim_relationship\");
                _repl.doDrop(SqlReplLogger.DB_META,stmt,\"fact_agg\",\"SELECT fact_agg_key FROM fact_agg f WHERE \" +
                                                                      \" NOT EXISTS (SELECT 1 FROM fact_agg_letter l WHERE \" +
                                                                      \"                 f.fact_agg_key = l.fact_agg_key) \"); /*6*/

                _repl.doDrop(SqlReplLogger.DB_META,\"dim_base_agg\",\"SELECT dim_base_agg_key FROM dim_base_agg d WHERE \" +
                                                                          \" NOT EXISTS (SELECT 1 FROM dim_base_agg_letter l WHERE \" +
                                                                          \"                 d.dim_base_agg_key = l.dim_base_agg_key) \"); /*6*/

                CheckOutOfSync(stmt,null); /*7*/
                CheckOutOfSync(stmt,null); /*7*/

                metaExec( stmt,\" update mirror_relationship set relation_to_current = \'Out Of Sync\' \" +
                                \" where dim_col_intmap_key is not null \" +
                                \" and relation_to_current = \'One Back\' \" +
                                \" and not exists ( \" +
                                \"       select 1 \" +
                                \"       from mirror_relationship m2,dim_col_view c,dim_col_intmap i \" +
                                \"       where m2.dim_base_key = c.dim_base_key \" +
                                \"       and c.dim_col_key = i.dim_col_key  \" +
                                \"       and i.dim_col_intmap_key = mirror_relationship.dim_col_intmap_key \" +
                                \"       and m2.relation_to_current = \'One Back\') \",\" SELECT 1 FROM mirror_relationship \" +
                                \" where dim_col_intmap_key is not null \" +
                                \" and relation_to_current = \'One Back\' \" +
                                \" and not exists ( \" +
                                \"       select 1 \" +
                                \"       from mirror_relationship m2,dim_col_intmap i \" +
                                \"       where m2.dim_base_key = c.dim_base_key \" +
                                \"       and c.dim_col_key = i.dim_col_key  \" +
                                \"       and i.dim_col_intmap_key = mirror_relationship.dim_col_intmap_key \" +
                                \"       and m2.relation_to_current = \'One Back\') \"); /*8*/

                // clean out the tables used by mombuilder,aggbuilder,and semantics
                metaExec( stmt,\"delete from relation_intermediary\",\"select 1 from relation_intermediary\" );

                _repl.epiCenterCon.commit();
                committed = true;
            }
            finally
            {

                safeMetaRollbackIfNeeded( committed );
                _repl.safeClose( null,stmt );
            }
        } // end synchronized block
    }
    finally
    {
        _repl.epiCenterCon.setAutoCommit(oldAutoCommitStatus);
    }
}
第一条delete语句运行良好,但是在运行更新时会引发上述异常。我们支持SQLServer,Oracle和DB2,并且相同的代码可以在其他DB上正常运行。顺便说一下,我们在READ_COMMITTED事务级别上运行这些语句,并且如果在两次安全操作之间有任何失败的情况下,我们都将自动提交设置为关闭。如果我使用autocommit true运行上述代码,则代码工作正常!但是我们不应该这样做。我怀疑PostgreSQL的多版本并发控制功能,我是否错误地设置了隔离级别?请尽我所能。我可以提供您想要的任何信息。     

解决方法

        如果仅这组特定查询,请使用
SET CONSTRAINT
BEGIN;
SET CONSTRAINT = xak1fact_dim_relationship DEFERRED;
-- Do your SQL
COMMIT;
如果这是非常常见的情况,则可以更改数据库模式,也可以更改数据库模式以支持“ 3”。     

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
参考1 参考2 解决方案 # 点击安装源 协议选择 http:// 路径填写 mirrors.aliyun.com/centos/8.3.2011/BaseOS/x86_64/os URL类型 软件库URL 其他路径 # 版本 7 mirrors.aliyun.com/centos/7/os/x86
报错1 [root@slave1 data_mocker]# kafka-console-consumer.sh --bootstrap-server slave1:9092 --topic topic_db [2023-12-19 18:31:12,770] WARN [Consumer clie
错误1 # 重写数据 hive (edu)&gt; insert overwrite table dwd_trade_cart_add_inc &gt; select data.id, &gt; data.user_id, &gt; data.course_id, &gt; date_format(
错误1 hive (edu)&gt; insert into huanhuan values(1,&#39;haoge&#39;); Query ID = root_20240110071417_fe1517ad-3607-41f4-bdcf-d00b98ac443e Total jobs = 1
报错1:执行到如下就不执行了,没有显示Successfully registered new MBean. [root@slave1 bin]# /usr/local/software/flume-1.9.0/bin/flume-ng agent -n a1 -c /usr/local/softwa
虚拟及没有启动任何服务器查看jps会显示jps,如果没有显示任何东西 [root@slave2 ~]# jps 9647 Jps 解决方案 # 进入/tmp查看 [root@slave1 dfs]# cd /tmp [root@slave1 tmp]# ll 总用量 48 drwxr-xr-x. 2
报错1 hive&gt; show databases; OK Failed with exception java.io.IOException:java.lang.RuntimeException: Error in configuring object Time taken: 0.474 se
报错1 [root@localhost ~]# vim -bash: vim: 未找到命令 安装vim yum -y install vim* # 查看是否安装成功 [root@hadoop01 hadoop]# rpm -qa |grep vim vim-X11-7.4.629-8.el7_9.x
修改hadoop配置 vi /usr/local/software/hadoop-2.9.2/etc/hadoop/yarn-site.xml # 添加如下 &lt;configuration&gt; &lt;property&gt; &lt;name&gt;yarn.nodemanager.res