Database Errors in Eventviewer

[RobertX]

Hello,

first of all, please apologize for my bad english, I will give my best to explain the issue at hand.

I just discoverd that my postgresql db is producing errors in the event view like this:

2011-05-26 19:02:43 CEST ERROR: duplicate key value violates unique constraint "thhs-unique_hand_no"
2011-05-26 19:02:43 CEST DETAIL: Key (id_site, hand_no)=(300, 30717166481) already exists.
2011-05-26 19:02:43 CEST CONTEXT: COPY tourney_holdem_hand_summary, line 1: "31565 300 0 31 2234 30717166481 2011/05/26 16:31:00 2011/05/26 19:02:43 9 2 2 2 1500.00 1480.00 1460..."
2011-05-26 19:02:43 CEST STATEMENT: COPY tourney_holdem_hand_summary FROM STDIN;

and

2011-09-01 21:03:42 CEST ERROR: duplicate key value violates unique constraint "settings_primary_key"
2011-09-01 21:03:42 CEST DETAIL: Key (setting_name)=(cache_update:holdem) already exists.
2011-09-01 21:03:42 CEST STATEMENT: INSERT INTO settings VALUES('cache_update:holdem', '8799');

taking right from a few minutes ago.

As you can see it started already back in May this year up to then there were no errors at all, just the starting messages. I am not much of a computer geek, so haven't really been looking into the event viewer, please apologize I am asking this late.

After reading up on PT database and such, I tried housekeeping. It had not effect, the error keeps occuring on each session. Today I created a new database and reimported the hands. Same errors happening during the manual import as well. However PT does not report any errors at all, which I don't understand.

Trying to create a new database I found those errors produce during the creation process, last one top, first one bottom.

2011-09-01 21:15:47 CEST ERROR: table "tourney_omaha_cache" does not exist
2011-09-01 21:15:47 CEST STATEMENT: DROP TABLE tourney_omaha_cache;
2011-09-01 21:15:46 CEST ERROR: table "omaha_cache" does not exist
2011-09-01 21:15:46 CEST STATEMENT: DROP TABLE omaha_cache;
2011-09-01 21:15:46 CEST ERROR: table "tourney_holdem_cache" does not exist
2011-09-01 21:15:46 CEST STATEMENT: DROP TABLE tourney_holdem_cache;
2011-09-01 21:15:46 CEST ERROR: table "holdem_cache" does not exist
2011-09-01 21:15:46 CEST STATEMENT: DROP TABLE holdem_cache;
2011-09-01 21:15:46 CEST ERROR: relation "holdem_cache" does not exist at character 32
2011-09-01 21:15:46 CEST STATEMENT: SELECT min(position_type) FROM holdem_cache WHERE 1=2;

What can I do to get the database repaired? I have all hand histories saved, so it would be no problem to start from scratch, but I am afraid of de-installing somewhat, not sure whether those errors are still there because something is corrupted?

I haven't noticed explicetly that PT is running bad or has wrong numbers, but that is only my view, is there a way I could find the hand for example from the error and look it up in PT?

I am sorry if this sounds confusing, but I hope you guys get an idea what I mean.

Regards,

Robert

[RobertX]

Some more information:

Tried now to import single files into the new database, show the same error following by this one:
2011-09-01 22:07:09 CEST WARNING: there is no transaction in progress
and later on
2011-09-01 22:08:28 CEST WARNING: there is already a transaction in progress

On another file with 39 hands PT reported all 39 hands import, the errors were the following:

2011-09-01 22:16:28 CEST ERROR: duplicate key value violates unique constraint "settings_primary_key"
2011-09-01 22:16:28 CEST DETAIL: Key (setting_name)=(cache_update:tourney_holdem) already exists.
2011-09-01 22:16:28 CEST STATEMENT: INSERT INTO settings VALUES('cache_update:tourney_holdem', '72');

2011-09-01 22:16:27 CEST ERROR: duplicate key value violates unique constraint "settings_primary_key"
2011-09-01 22:16:27 CEST DETAIL: Key (setting_name)=(cache_update:holdem) already exists.
2011-09-01 22:16:27 CEST STATEMENT: INSERT INTO settings VALUES('cache_update:holdem', '39');

Also found out that those errors here happen for cash game files. The errors earlier on are errors from tournament hand histories, if that helps.

Regards,

Robert

[WhiteRider]

The errors you're seeing don't necessarily indicate a problem - you can see that sort of thing if the hands you're trying to import are already in the database.

However:
What version of PostgreSQL do you have? See Database > Database Management.
If it's 8.3.x but not 8.3.9 or 10 then you should update - Directions here.

I would suggest that you run Database > Housekeeping with the ReIndex and Rebuild Cache options in addition to the defaults whether you need to update PostgreSQL or not.

[RobertX]

The errors you're seeing don't necessarily indicate a problem - you can see that sort of thing if the hands you're trying to import are already in the database.

However:
What version of PostgreSQL do you have? See Database > Database Management.
If it's 8.3.x but not 8.3.9 or 10 then you should update - Directions here.

I would suggest that you run Database > Housekeeping with the ReIndex and Rebuild Cache options in addition to the defaults whether you need to update PostgreSQL or not.

Apparently I forgot to write that these errors happen during autoimport and they were reproduced when I created a new database and import a single file to it, so there is hardly any hand duplicate. The creation of a new database produces errors already:

Trying to create a new database I found those errors produce during the creation process, last one top, first one bottom.

2011-09-01 21:15:47 CEST ERROR: table "tourney_omaha_cache" does not exist
2011-09-01 21:15:47 CEST STATEMENT: DROP TABLE tourney_omaha_cache;
2011-09-01 21:15:46 CEST ERROR: table "omaha_cache" does not exist
2011-09-01 21:15:46 CEST STATEMENT: DROP TABLE omaha_cache;
2011-09-01 21:15:46 CEST ERROR: table "tourney_holdem_cache" does not exist
2011-09-01 21:15:46 CEST STATEMENT: DROP TABLE tourney_holdem_cache;
2011-09-01 21:15:46 CEST ERROR: table "holdem_cache" does not exist
2011-09-01 21:15:46 CEST STATEMENT: DROP TABLE holdem_cache;
2011-09-01 21:15:46 CEST ERROR: relation "holdem_cache" does not exist at character 32
2011-09-01 21:15:46 CEST STATEMENT: SELECT min(position_type) FROM holdem_cache WHERE 1=2

I am using PostgreSQL 9.0 from the very first install. There were no errors from December last year up to may when first ones popped up.

Those errors weren't produced when I created the first database on the fresh install back in December.

[RobertX]

I have run the housekeeping on the original database like suggested those errors were produced:

2011-09-02 20:18:14 CEST ERROR: duplicate key value violates unique constraint "settings_primary_key"
2011-09-02 20:18:14 CEST DETAIL: Key (setting_name)=(cache_update:holdem) already exists.
2011-09-02 20:18:14 CEST STATEMENT: INSERT INTO settings VALUES('cache_update:holdem', '11535');

2011-09-02 20:21:26 CEST ERROR: duplicate key value violates unique constraint "settings_primary_key"
2011-09-02 20:21:26 CEST DETAIL: Key (setting_name)=(cache_update:tourney_holdem) already exists.
2011-09-02 20:21:26 CEST STATEMENT: INSERT INTO settings VALUES('cache_update:tourney_holdem', '40207');

Does this help any further?

[WhiteRider]

If you're getting those errors in a new database that's definitely strange.
(The error "table "tourney_omaha_cache" does not exist" is expected in a new database because there isn't a cache yet.)

Please enable logging and restart PT3 and reproduce the problem. Attach the PokerTracker.log file to a Support ticket along with the last few files from the PostgreSQL/9.0/data/pg_log folder (you can compress them to upload just one file) and one of our support techs will work with you to get things sorted out. If we can't see the issue from the logs we can schedule a remote session where someone can connect to your computer to help you directly, but we'll do that via the ticket if the logs don't help.
Please include a link to this thread in your ticket too - thanks.

Tutorial: Submitting a Bug Report

[RobertX]

If you're getting those errors in a new database that's definitely strange.
(The error "table "tourney_omaha_cache" does not exist" is expected in a new database because there isn't a cache yet.)

Please enable logging and restart PT3 and reproduce the problem. Attach the PokerTracker.log file to a Support ticket along with the last few files from the PostgreSQL/9.0/data/pg_log folder (you can compress them to upload just one file) and one of our support techs will work with you to get things sorted out. If we can't see the issue from the logs we can schedule a remote session where someone can connect to your computer to help you directly, but we'll do that via the ticket if the logs don't help.
Please include a link to this thread in your ticket too - thanks.

Tutorial: Submitting a Bug Report

I have installed PT3 and Postgres 9.04 on another machine which I just had for today. The error log shows the same errors on creating the very first default database on this fresh install as well:

2011-09-02 22:52:23 CEST FATAL: database "PT3 DB" does not exist
2011-09-02 22:53:41 CEST ERROR: relation "holdem_cache" does not exist at character 32
2011-09-02 22:53:41 CEST STATEMENT: SELECT min(position_type) FROM holdem_cache WHERE 1=2;
2011-09-02 22:53:41 CEST ERROR: table "holdem_cache" does not exist
2011-09-02 22:53:41 CEST STATEMENT: DROP TABLE holdem_cache;
2011-09-02 22:53:41 CEST ERROR: table "tourney_holdem_cache" does not exist
2011-09-02 22:53:41 CEST STATEMENT: DROP TABLE tourney_holdem_cache;
2011-09-02 22:53:41 CEST ERROR: table "omaha_cache" does not exist
2011-09-02 22:53:41 CEST STATEMENT: DROP TABLE omaha_cache;
2011-09-02 22:53:42 CEST ERROR: table "tourney_omaha_cache" does not exist
2011-09-02 22:53:42 CEST STATEMENT: DROP TABLE tourney_omaha_cache;

It looks like somehow the script that creates the database has some errors, because it says for example "at character 32". Also it seems that those errors were on my machine from the very start as well, just not redirected to the windows event viewer.

I will deinstall my machine and reinstall PT3 and Postgresql 9.0.4 and then do as suggest via ticket.

Thanks, Robert

[RobertX]

On a sidenote:

The ticketing system shows Versions 3.11. My Version is 3.10 would it be supposed to update to 3.11?

Latest download is 3.10 from the website as well.

[Peligroso]

On a sidenote:

The ticketing system shows Versions 3.11. My Version is 3.10 would it be supposed to update to 3.11?

Latest download is 3.10 from the website as well.

There are two versions available on the Download Page - 3.10 and our latest Beta release which is 3.11.4.