Duplicate on bmsql_history_pkey

[williamsd-ppb]

Converted to use Informix and seeing the following exception.

13:36:23,161 [Thread-2] ERROR jTPCCTData : Unexpected SQLException in PAYMENT
13:36:23,162 [Thread-2] ERROR jTPCCTData : Unique constraint (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate value for a record with unique key.(-100)
java.sql.SQLIntegrityConstraintViolationException: Unique constraint (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate value for a record with unique key.(-100)
at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:410)
at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401)
at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3021)
at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3272)
at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269)
at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194)
at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:813)
at com.informix.jdbc.IfxResultSet.executeUpdate(IfxResultSet.java:225)
at com.informix.jdbc.IfxStatement.executeUpdateImpl(IfxStatement.java:958)
at com.informix.jdbc.IfxPreparedStatement.executeUpdate(IfxPreparedStatement.java:322)
at jTPCCTData.executePayment(jTPCCTData.java:1278)
at jTPCCTData.execute(jTPCCTData.java:159)
at jTPCCTerminal.executeTransactions(jTPCCTerminal.java:219)
at jTPCCTerminal.run(jTPCCTerminal.java:146)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.sql.SQLException: ISAM error: duplicate value for a record with unique key.
at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416)
at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:397)
at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:371)
at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3276)
... 11 more

[wieck]

On 2/21/22 09:19, williamsd-ppb wrote: Converted to use Informix and seeing the following exception. 13:36:23,161 [Thread-2] ERROR jTPCCTData : Unexpected SQLException in PAYMENT 13:36:23,162 [Thread-2] ERROR jTPCCTData : Unique constraint (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate value for a record with unique key.(-100)

What construct are you using to generate the history pkey? It should be based on a sequence or other feature (like auto-increment) that generates unique, not null values without the help of the application. Note that this column is actually not part of the original TPC-C. It was added to support logical replication systems that rely on a primary key column to be present for all replicated tables. Regards, Jan

…

java.sql.SQLIntegrityConstraintViolationException: Unique constraint (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate value for a record with unique key.(-100) at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:410) at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401) at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3021) at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3272) at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269) at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194) at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:813) at com.informix.jdbc.IfxResultSet.executeUpdate(IfxResultSet.java:225) at com.informix.jdbc.IfxStatement.executeUpdateImpl(IfxStatement.java:958) at com.informix.jdbc.IfxPreparedStatement.executeUpdate(IfxPreparedStatement.java:322) at jTPCCTData.executePayment(jTPCCTData.java:1278) at jTPCCTData.execute(jTPCCTData.java:159) at jTPCCTerminal.executeTransactions(jTPCCTerminal.java:219) at jTPCCTerminal.run(jTPCCTerminal.java:146) at java.lang.Thread.run(Thread.java:750) Caused by: java.sql.SQLException: ISAM error: duplicate value for a record with unique key. at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416) at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:397) at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:371) at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3276) ... 11 more — Reply to this email directly, view it on GitHub <#18>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACYRMXRLSVNS2DKITAT7H3U4JCWDANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Jan Wieck

[williamsd-ppb]

HI, How would I tell what is used to construct the history pkey? We added a sql.informix and I notice in extraHistID.sql we do use the sequence. FYI I had to update the java so we can do password-less connections in Informix. If in the properties file we do not specify a user than the user/password is not added to the properties or DriverManager.getConnection is called with just the connection url. Do you have a direct email address where I can send you the updated code? Regards, David. From: Jan Wieck ***@***.***> Sent: 21 February 2022 18:13 To: pgsql-io/benchmarksql ***@***.***> Cc: David Williams ***@***.***>; Author ***@***.***> Subject: Re: [pgsql-io/benchmarksql] Duplicate on bmsql_history_pkey (Issue #18) EXTERNAL SENDER: This email originated from outside our email system. If you find this email suspicious please use the Report Phishing button in your Outlook to flag this to the Security Operations team.

On 2/21/22 09:19, williamsd-ppb wrote: Converted to use Informix and seeing the following exception. 13:36:23,161 [Thread-2] ERROR jTPCCTData : Unexpected SQLException in PAYMENT 13:36:23,162 [Thread-2] ERROR jTPCCTData : Unique constraint (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate value for a record with unique key.(-100)

What construct are you using to generate the history pkey? It should be based on a sequence or other feature (like auto-increment) that generates unique, not null values without the help of the application. Note that this column is actually not part of the original TPC-C. It was added to support logical replication systems that rely on a primary key column to be present for all replicated tables. Regards, Jan

…

java.sql.SQLIntegrityConstraintViolationException: Unique constraint (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate value for a record with unique key.(-100) at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:410) at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401) at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3021) at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3272) at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269) at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194) at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:813) at com.informix.jdbc.IfxResultSet.executeUpdate(IfxResultSet.java:225) at com.informix.jdbc.IfxStatement.executeUpdateImpl(IfxStatement.java:958) at com.informix.jdbc.IfxPreparedStatement.executeUpdate(IfxPreparedStatement.java:322) at jTPCCTData.executePayment(jTPCCTData.java:1278) at jTPCCTData.execute(jTPCCTData.java:159) at jTPCCTerminal.executeTransactions(jTPCCTerminal.java:219) at jTPCCTerminal.run(jTPCCTerminal.java:146) at java.lang.Thread.run(Thread.java:750) Caused by: java.sql.SQLException: ISAM error: duplicate value for a record with unique key. at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416) at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:397) at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:371) at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3276) ... 11 more — Reply to this email directly, view it on GitHub <#18>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACYRMXRLSVNS2DKITAT7H3U4JCWDANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***>>

-- Jan Wieck — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY7QGE74NLWQMEU5BR44HDU4J6EHANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[wieck]

On 2/22/22 09:38, williamsd-ppb wrote: HI, How would I tell what is used to construct the history pkey? We added a sql.informix and I notice in extraHistID.sql we do use the sequence. FYI I had to update the java so we can do password-less connections in Informix. If in the properties file we do not specify a user than the user/password is not added to the properties or DriverManager.getConnection is called with just the connection url. Do you have a direct email address where I can send you the updated code?

***@***.*** is my direct email address. What did you derive sql.informix from? Did you receive it from somewhere else or did you copy it from one of the other, existing ones? Regards, Jan

…

Regards, David. From: Jan Wieck ***@***.***> Sent: 21 February 2022 18:13 To: pgsql-io/benchmarksql ***@***.***> Cc: David Williams ***@***.***>; Author ***@***.***> Subject: Re: [pgsql-io/benchmarksql] Duplicate on bmsql_history_pkey (Issue #18) EXTERNAL SENDER: This email originated from outside our email system. If you find this email suspicious please use the Report Phishing button in your Outlook to flag this to the Security Operations team. On 2/21/22 09:19, williamsd-ppb wrote: > Converted to use Informix and seeing the following exception. > > 13:36:23,161 [Thread-2] ERROR jTPCCTData : Unexpected SQLException in > PAYMENT > 13:36:23,162 [Thread-2] ERROR jTPCCTData : Unique constraint > (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate > value for a record with unique key.(-100) What construct are you using to generate the history pkey? It should be based on a sequence or other feature (like auto-increment) that generates unique, not null values without the help of the application. Note that this column is actually not part of the original TPC-C. It was added to support logical replication systems that rely on a primary key column to be present for all replicated tables. Regards, Jan > java.sql.SQLIntegrityConstraintViolationException: Unique constraint > (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate > value for a record with unique key.(-100) > at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:410) > at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401) > at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3021) > at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3272) > at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269) > at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194) > at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:813) > at com.informix.jdbc.IfxResultSet.executeUpdate(IfxResultSet.java:225) > at com.informix.jdbc.IfxStatement.executeUpdateImpl(IfxStatement.java:958) > at > com.informix.jdbc.IfxPreparedStatement.executeUpdate(IfxPreparedStatement.java:322) > at jTPCCTData.executePayment(jTPCCTData.java:1278) > at jTPCCTData.execute(jTPCCTData.java:159) > at jTPCCTerminal.executeTransactions(jTPCCTerminal.java:219) > at jTPCCTerminal.run(jTPCCTerminal.java:146) > at java.lang.Thread.run(Thread.java:750) > Caused by: java.sql.SQLException: ISAM error: duplicate value for a > record with unique key. > at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416) > at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:397) > at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:371) > at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3276) > ... 11 more > > — > Reply to this email directly, view it on GitHub > <#18>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACYRMXRLSVNS2DKITAT7H3U4JCWDANCNFSM5O6XKJHA>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***<mailto:***@***.***>> > -- Jan Wieck — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY7QGE74NLWQMEU5BR44HDU4J6EHANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACYRMQEFFOMJAS5TXOX2CTU4ONXVANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

-- Jan Wieck

[williamsd-ppb]

Hi, Your email address is blanked ou in the reply! We derived the sql.informix from the postgres version. Regards, David. From: Jan Wieck ***@***.***> Sent: 22 February 2022 17:11 To: pgsql-io/benchmarksql ***@***.***> Cc: David Williams ***@***.***>; Author ***@***.***> Subject: Re: [pgsql-io/benchmarksql] Duplicate on bmsql_history_pkey (Issue #18) EXTERNAL SENDER: This email originated from outside our email system. If you find this email suspicious please use the Report Phishing button in your Outlook to flag this to the Security Operations team.

On 2/22/22 09:38, williamsd-ppb wrote: HI, How would I tell what is used to construct the history pkey? We added a sql.informix and I notice in extraHistID.sql we do use the sequence. FYI I had to update the java so we can do password-less connections in Informix. If in the properties file we do not specify a user than the user/password is not added to the properties or DriverManager.getConnection is called with just the connection url. Do you have a direct email address where I can send you the updated code?

***@***.*** is my direct email address. What did you derive sql.informix from? Did you receive it from somewhere else or did you copy it from one of the other, existing ones? Regards, Jan

…

Regards, David. From: Jan Wieck ***@***.***> Sent: 21 February 2022 18:13 To: pgsql-io/benchmarksql ***@***.***> Cc: David Williams ***@***.***>; Author ***@***.***> Subject: Re: [pgsql-io/benchmarksql] Duplicate on bmsql_history_pkey (Issue #18) EXTERNAL SENDER: This email originated from outside our email system. If you find this email suspicious please use the Report Phishing button in your Outlook to flag this to the Security Operations team. On 2/21/22 09:19, williamsd-ppb wrote: > Converted to use Informix and seeing the following exception. > > 13:36:23,161 [Thread-2] ERROR jTPCCTData : Unexpected SQLException in > PAYMENT > 13:36:23,162 [Thread-2] ERROR jTPCCTData : Unique constraint > (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate > value for a record with unique key.(-100) What construct are you using to generate the history pkey? It should be based on a sequence or other feature (like auto-increment) that generates unique, not null values without the help of the application. Note that this column is actually not part of the original TPC-C. It was added to support logical replication systems that rely on a primary key column to be present for all replicated tables. Regards, Jan > java.sql.SQLIntegrityConstraintViolationException: Unique constraint > (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate > value for a record with unique key.(-100) > at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:410) > at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401) > at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3021) > at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3272) > at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269) > at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194) > at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:813) > at com.informix.jdbc.IfxResultSet.executeUpdate(IfxResultSet.java:225) > at com.informix.jdbc.IfxStatement.executeUpdateImpl(IfxStatement.java:958) > at > com.informix.jdbc.IfxPreparedStatement.executeUpdate(IfxPreparedStatement.java:322) > at jTPCCTData.executePayment(jTPCCTData.java:1278) > at jTPCCTData.execute(jTPCCTData.java:159) > at jTPCCTerminal.executeTransactions(jTPCCTerminal.java:219) > at jTPCCTerminal.run(jTPCCTerminal.java:146) > at java.lang.Thread.run(Thread.java:750) > Caused by: java.sql.SQLException: ISAM error: duplicate value for a > record with unique key. > at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416) > at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:397) > at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:371) > at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3276) > ... 11 more > > — > Reply to this email directly, view it on GitHub > <#18>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACYRMXRLSVNS2DKITAT7H3U4JCWDANCNFSM5O6XKJHA>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***<mailto:***@***.***>> > -- Jan Wieck — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY7QGE74NLWQMEU5BR44HDU4J6EHANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACYRMQEFFOMJAS5TXOX2CTU4ONXVANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

-- Jan Wieck — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY7QGDKZGJVBNXPEKBBCJTU4O7RXANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[wieck]

On 2/24/22 14:06, williamsd-ppb wrote: Hi, Your email address is blanked ou in the reply!

Looks like some extreme paranoia on the side of your email admin. My email address is also in all the git commits of the benchmarksql repository. Jan

…

We derived the sql.informix from the postgres version. Regards, David. From: Jan Wieck ***@***.***> Sent: 22 February 2022 17:11 To: pgsql-io/benchmarksql ***@***.***> Cc: David Williams ***@***.***>; Author ***@***.***> Subject: Re: [pgsql-io/benchmarksql] Duplicate on bmsql_history_pkey (Issue #18) EXTERNAL SENDER: This email originated from outside our email system. If you find this email suspicious please use the Report Phishing button in your Outlook to flag this to the Security Operations team. On 2/22/22 09:38, williamsd-ppb wrote: > HI, > > How would I tell what is used to construct the history pkey? > > We added a sql.informix and I notice in extraHistID.sql we do use the > sequence. > > FYI > I had to update the java so we can do password-less connections in > Informix. > If in the properties file we do not specify a user than the > user/password is not added to the properties or > DriverManager.getConnection is called with just the connection url. > > Do you have a direct email address where I can send you the updated code? ***@***.*** is my direct email address. What did you derive sql.informix from? Did you receive it from somewhere else or did you copy it from one of the other, existing ones? Regards, Jan > > Regards, > David. > > From: Jan Wieck ***@***.***> > Sent: 21 February 2022 18:13 > To: pgsql-io/benchmarksql ***@***.***> > Cc: David Williams ***@***.***>; Author ***@***.***> > Subject: Re: [pgsql-io/benchmarksql] Duplicate on bmsql_history_pkey > (Issue #18) > > > > > EXTERNAL SENDER: This email originated from outside our email system. If > you find this email suspicious please use the Report Phishing button in > your Outlook to flag this to the Security Operations team. > > > > > > On 2/21/22 09:19, williamsd-ppb wrote: > > Converted to use Informix and seeing the following exception. > > > > 13:36:23,161 [Thread-2] ERROR jTPCCTData : Unexpected SQLException in > > PAYMENT > > 13:36:23,162 [Thread-2] ERROR jTPCCTData : Unique constraint > > (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate > > value for a record with unique key.(-100) > > What construct are you using to generate the history pkey? It should be > based on a sequence or other feature (like auto-increment) that > generates unique, not null values without the help of the application. > > Note that this column is actually not part of the original TPC-C. It was > added to support logical replication systems that rely on a primary key > column to be present for all replicated tables. > > > > Regards, Jan > > > > java.sql.SQLIntegrityConstraintViolationException: Unique constraint > > (informix.bmsql_history_pkey) violated.(-268) ISAM error: duplicate > > value for a record with unique key.(-100) > > at > com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:410) > > at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401) > > at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3021) > > at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3272) > > at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269) > > at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194) > > at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:813) > > at com.informix.jdbc.IfxResultSet.executeUpdate(IfxResultSet.java:225) > > at > com.informix.jdbc.IfxStatement.executeUpdateImpl(IfxStatement.java:958) > > at > > > com.informix.jdbc.IfxPreparedStatement.executeUpdate(IfxPreparedStatement.java:322) > > > at jTPCCTData.executePayment(jTPCCTData.java:1278) > > at jTPCCTData.execute(jTPCCTData.java:159) > > at jTPCCTerminal.executeTransactions(jTPCCTerminal.java:219) > > at jTPCCTerminal.run(jTPCCTerminal.java:146) > > at java.lang.Thread.run(Thread.java:750) > > Caused by: java.sql.SQLException: ISAM error: duplicate value for a > > record with unique key. > > at > com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416) > > at com.informix.util.IfxErrMsg.buildException(IfxErrMsg.java:397) > > at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:371) > > at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3276) > > ... 11 more > > > > — > > Reply to this email directly, view it on GitHub > > <#18>, or unsubscribe > > > <https://github.com/notifications/unsubscribe-auth/AACYRMXRLSVNS2DKITAT7H3U4JCWDANCNFSM5O6XKJHA>. > > > Triage notifications on the go with GitHub Mobile for iOS > > > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > > > or Android > > > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > > > > You are receiving this because you are subscribed to this thread.Message > > ID: ***@***.***<mailto:***@***.***>> > > > > > -- > Jan Wieck > > > — > Reply to this email directly, view it on > GitHub<#18 (comment)>, > or > unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY7QGE74NLWQMEU5BR44HDU4J6EHANCNFSM5O6XKJHA>. > > Triage notifications on the go with GitHub Mobile for > iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or > Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.******@***.***>> > > — > Reply to this email directly, view it on GitHub > <#18 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACYRMQEFFOMJAS5TXOX2CTU4ONXVANCNFSM5O6XKJHA>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you commented.Message ID: > ***@***.***> > -- Jan Wieck — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY7QGDKZGJVBNXPEKBBCJTU4O7RXANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACYRMTR4JBDKUGZEP5NSIDU4Z6SNANCNFSM5O6XKJHA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

-- Jan Wieck