Error: 25p02

[justdoit]

I have a perfectly fine working Database which is purged, fully vacuumed, reindexed and made a Backup.
When I restore that backup and import new hands from hh dealer after a certain amount, about 200.000, I receive the following error:

ERROR: 25P02: current transaction is aborted, commands ignored until end of transaction block

My Database is very large, can it be the case that it has reached HM1 maximum capacity? How big can a HM1 Database be?
I always also restore the \config folder... can the reason for the error lie in the config folder?

I use 1.12.02
It could correlate to the update to 1.12
should I try an earlier version of HM?

:(:(:(

[Patvs]

The database size has no maximum.

Your issue is probably a database corruption. (might be caused by the database update when you updated to 1.12)
Which SQL version are you using?

After you restored the .backup, do you still vacuum/reindex the database regularly (for example monthly after importing 100.000 hands?)

Restoring the old /config folder is unrelated to this.

[justdoit]

I use 8.4 and dont know how to tell you a more specific version.

Before this problem came up i was able to import MUCH larger amounts than 100k hands before this happened. now I really have to vacuum reindex after 100k hands but this is so small that I would have to do it too often... thats why i assumed i might have reached the HM1 maximum or the db is corrupt.

I just optimized the DB and let hm put the optimal postgres values.
now i cant import anymore at all and receive a timeout error.

[Patvs]

Try reimporting the hands into a new database.

Don't purge any of the hands.

[justdoit]

i can import those hands into a new database

i btw had the same issue with a backup that was couple of months old an running fine for two more months

the problem persistes on two different systems that is why i assumed it might be a problem with the config folder because i carry that around since not long after the release.

is there a maximum of unpurged hands?

[Sarek]

unpurged? you mean "how big can DB be"? Limited by disk size only

[justdoit]

ok
so in theory I dont gain any advantage of a purge vacuum reindex when I use a SSD, only save disk space?


After you restored the .backup, do you still vacuum/reindex the database regularly (for example monthly after importing 100.000 hands?)
why should i do it? (yes i did it regularly)

[Patvs]

Yes, with a SSD you only save diskspace.
And there are two types of purges (delete)

-options--> settings--> purge hands (will delete handhistory, hand from graph, $Won from sessions, etc. everything, so hand won't be used anymore for stats)
-options--> settings--> observed HH configuration--> purge hands--> will delete the handhistory and therefore the ability to replay the hand, but the hand will still be used for the graph, $Won from sessions and for the HUD.


With observed HH configuration--> purge hands you only win back a TINY bit of diskspace, so it's not worth it.

Ideally, you now update PostgreSQL and reimport all your hands again into a new database. Then create another backup.
Try PostgreSQL 9.1 (64 bit if you use a 64 bit operation system) from PostgreSQL: The world's most advanced open source database (http://www.postgresql.org)

[BigHand]

Sick
After upgrading to 1.12.03 I'm getting same errors while importing large number of hh files in newly created DB

Also at the same time Postgresql error log is filled with this errors


2011-09-24 15:35:35 MSD ERROR: duplicate key value violates unique constraint "uniqueserial"
2011-09-24 15:35:35 MSD STATEMENT: EXECUTE PKHEXECUTE(5177272903262,9,to_timestamp('09/20/2011 17:21:24','MM/DD/YYYY HH24:MI:SS'),153,2,3,2,2,2,0,3,12,9,45,3,7,120,6,1 20,120,120,0,0,0,0,2,3,False,4,0,0,0,12,12,12,-1,0,-1,0); select currval('pokerhands_pokerhand_id_seq')
2011-09-24 15:35:35 MSD ERROR: duplicate key value violates unique constraint "uniqueserial"

[olliepower]

Hi,

We are looking into this.

Ollie.

[fozzy71]

Sick
After upgrading to 1.12.03 I'm getting same errors while importing large number of hh files in newly created DB

Also at the same time Postgresql error log is filled with this errors


2011-09-24 15:35:35 MSD ERROR: duplicate key value violates unique constraint "uniqueserial"
2011-09-24 15:35:35 MSD STATEMENT: EXECUTE PKHEXECUTE(5177272903262,9,to_timestamp('09/20/2011 17:21:24','MM/DD/YYYY HH24:MI:SS'),153,2,3,2,2,2,0,3,12,9,45,3,7,120,6,1 20,120,120,0,0,0,0,2,3,False,4,0,0,0,12,12,12,-1,0,-1,0); select currval('pokerhands_pokerhand_id_seq')
2011-09-24 15:35:35 MSD ERROR: duplicate key value violates unique constraint "uniqueserial"


Thats a normal error if you try to import a duplicate hand. You can ignore it if you have no other problems.