can't import hand histories with ipoker

Experiencing technical difficulties? Think you've found a problem with PokerTracker 3? Report it here.

Moderator: Moderators

can't import hand histories with ipoker

Postby Joeboy » Wed Oct 08, 2008 12:10 am

I keep getting the same error message...I sent 3 emails but poker tracker won't respond plz help....the message is as follows;
8: iPoker: Unable to import hand (#1776890633). Reason: Unable to execute query: COPY tourney_holdem_hand_summary FROM STDIN;; Reason: Fatal Error (ERROR: extra data after last expected column CONTEXT: COPY tourney_holdem_hand_summary, line 1: "1211 400 33 21 55 1776890633 2008/10/07 09:33:22 2008/10/07 12:51:26 2 2 2 2 1440.00 840.00 -0.00 -0..." )
2008/10/07 12:51:28: iPoker: Stopping auto-import.
8: iPoker: Unable to import hand (#1776890633). Reason: Unable to execute query: COPY tourney_holdem_hand_summary FROM STDIN;; Reason: Fatal Error (ERROR: extra data after last expected column CONTEXT: COPY tourney_holdem_hand_summary, line 1: "1211 400 33 21 55 1776890633 2008/10/07 09:33:22 2008/10/07 12:51:26 2 2 2 2 1440.00 840.00 -0.00 -0..." )
2008/10/07 12:51:28: iPoker: Stopping auto-import.
Joeboy
 
Posts: 2
Joined: Thu Aug 28, 2008 7:56 pm

Re: can't import hand histories with ipoker

Postby WhiteRider » Wed Oct 08, 2008 5:04 am

There are two main reasons for this error. The first is a result of data corruption from a computer crash that requires reindexing your database. You can reindex your database from the PostgreSQL command prompt. Click Start --> Programs --> PostgreSQL --> Command prompt. At the prompt that appears, type “reindexdb -a” and hit enter. Be aware that if you have large databases this may take a while, so be patient and wait for it to finish.
(If the re-index doesn't work because you are not logged in as user 'postgres' enter: "reindexdb -U postgres -a").

The second reason for this error is a result of faulty hardware. You can set PostgreSQL to ignore these errors by clicking Start --> Programs --> PostgreSQL --> Configuration Files --> Edit postgresql.conf. In the configuration file that appears, go to the bottom of the file and add the text “zero_damaged_pages = on” on a new line and then save and close the file. Click Start --> Programs --> PostgreSQL --> Reload Configuration and PostgreSQL will ignore the damaged data. If you continue to have problems with that hard drive, you should consider replacing it.

You should use the Support system to get help, rather than emailing.
WhiteRider
Moderator
 
Posts: 54025
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK


Return to Technical Support / Bug Reports [Read Only]

Who is online

Users browsing this forum: No registered users and 1 guest