Database permanently corrupted? How do I start a new one?

[katefan55]

I started a support ticket this morning but since it is christmas I expect support to take a while to get back to me. I wanted to see if anyone could help me here.

Yesterday as I began to import hands I got this message--" Full Tilt: Unable to import hand (#9673347223). Reason: Unable to execute query: COPY holdem_hand_histories FROM STDIN;; Reason: Fatal Error (ERROR: could not open relation 1663/16403/16659: No such file or directory CONTEXT: COPY holdem_hand_histories, line 1: "93935 "

The interesting thing is that the hands are actually being imported I can see them in the general tab when I click refresh. However no HUD stats have updated since these error messages started yesterday (meaning I can't get stats on unknown players and session Hero stats do not appear). Graphs are also not updating (there are a different amount of total hands listed in the general tab compared to the graph)

I have thoroughly read through this thread:

viewtopic.php?f=16&t=7893&st=0&sk=t&sd=a

and the sticky thread for Vista Users here: viewtopic.php?f=16&t=15574

and have tried all of the solutions. Here is a list in order--

1. Uninstall and reinstall Postgresql8.3--This fixed an issue I was having opening PT3. Sometimes the program would just not appear it seems to now be resolved.

2. Added "zero_damaged_pages = on" to the last line of the editpostgresql.conf file and saved. Ran reload configuration. It had no effect. Is it proper that the reload config file only blips on for like a quarter of a second? When I use to have trouble with PT3 opening id click on start service a lot and it would take several seconds to load.

3. Attempted to reindex database. Process began but stopped with a message saying " reindexing of database "PT3 DB" failed: ERROR: could not open relation 1663/16403/16659: No such file or directory

4. Did Houskeeping. Midway through got this message:

"There were errors during the housekeeping process:
Unable to execute query: VACUUM FULL;; Reason: Fatal Error (ERROR: could not open relation 1663/16403/16659: No such file or directory CONTEXT: COPY holdem_hand_histories, line 1:"


" could not open relation 1663/16403/16659" seems to be popping up in all of the documented solutions. Why isn't PT3 ignoring the errors when I inserted the zero damaged pages comment?

If the database is corrupted can a start a new one and just import all the HH from the PT3 DB database? How do I go about doing that? Is there a link to instructions somewhere?

Thank you,

Bart Hanson

[WhiteRider]

There are two main reasons for this kind of 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.

The guy who normally supports this forum knows more about postgres and this kind of problem than me but I'm not sure when he'll be online - hopefully sometime today, but I can't be sure..

[kraada]

You can create a new database in PT3 by clicking Database --> Database management --> New, but you may need to reinstall PostgreSQL first; you can find a tutorial on how to do that here and it might help as well.

[katefan55]

There are two main reasons for this kind of 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.

The guy who normally supports this forum knows more about postgres and this kind of problem than me but I'm not sure when he'll be online - hopefully sometime today, but I can't be sure..

No offense, White Rider, but you guys give this generic response to everyone that presents this type of problem. I have tried both of your solutions--see my whole post--including also uninstalling and reinstalling SQLpost and housekeeping. I again ask why PT3 will not ignore the errors if I have inserted that zero_damaged_pages comment in the postgresql.conf file?

I also find it a little hard to believe that everyone who gets these types of error messages have had a power failure or have faulty hardware. Someone else got some sort of invalid header comment message that he posted here on the 24th in this tech support forum. That makes dozens of customers over the last few months, counting people in the forums alone. When is the policy of PT support going to change from providing this generic reindexing/zero_damage solution to actually addressing what is causing these errors?

Also your last resort solution is to replace my hardrive? I just purchased an inspiron 1525 last month, and PT3 last week.

Bart

[kraada]

Please create a support request via this link and we'll have a support technician log into your machine and resolve the error firsthand.

The reason that setting is requested is that there is damaged data in the database. That's what the error you've quoted means. You can see this area of the PostgreSQL documentation to see that setting zero_damaged_pages to true lets PostgreSQL get past the damaged area. The most common reason that I've seen for this error is a computer crash. I'm not sure what caused it in your case, but it's clear from the error what is going on, which is why WhiteRider suggested that solution. It works for most people who have the problem you describe, but since it doesn't work for you, if you create the ticket as suggested above, we'll figure out what's going on for you and get it fixed.

[katefan55]

Please create a support request via this link and we'll have a support technician log into your machine and resolve the error firsthand.

The reason that setting is requested is that there is damaged data in the database. That's what the error you've quoted means. You can see this area of the PostgreSQL documentation to see that setting zero_damaged_pages to true lets PostgreSQL get past the damaged area. The most common reason that I've seen for this error is a computer crash. I'm not sure what caused it in your case, but it's clear from the error what is going on, which is why WhiteRider suggested that solution. It works for most people who have the problem you describe, but since it doesn't work for you, if you create the ticket as suggested above, we'll figure out what's going on for you and get it fixed.

Kraada,

I created a ticket yesterday. The number is 44561.

[kraada]

Thanks, we'll get back to you in the ticket and we'll keep at it until your issue is resolved.