Updated to beta27, Crashed, now life in shambles.

[mad1]

I updated last night to beta27. While doing the database update that it requires on first boot, I got a blue screen and was forced to reboot. Naturally when I came back into windows, one of my other drives (not connected to postgres or pt3) had delayed write failure, and was unable to be read by windows. This may or may not have been the cause of the blue screen that crashed pt3. It could be the other way around. Getting back on topic:

I got back into pt3, and ran the maintenance again, only this time it completed with a huge page of errors, As seen here:

http://img93.imageshack.us/img93/4427/pt3error.jpg

I read posts for hours, and decided I would try going into the pgadmin program, and reindex my database. Completed that after a few hours. I then redid maintenance, and did the clustering/analyzing, and left off doing the cache. It completed successfully. I then tried to update the cache, and it instantly came back with the same page of errors.

So there appears to be a problem. I can't import hands to my database now. "Unable to begin feeder import process. Reason: PT is configured to import into an outdated database. This must be corrected before an import can succeed."

What are my options here? I'm running postgres 8.2. If I back up my database and completely uninstall postgres, and reinstall 8.3. Will I still have these problems that I'm having now? Do i need to export all text file hand histories and start from scratch?

If I try to run pt3 now, i always get the message on startup that my databases need to be updated. I then say ok, it instantly says ok done, Then it asks me to cluster and analyze (which I just did for 3 hours), then I get a message that my database does not contain a populated cache.

Please save my life.

[kraada]

Close PT3. Click Start --> Programs --> PostgreSQL --> psql to 'postgres'. At the prompt, type \l and hit enter, this will list your databases. Then type \connect 'Your Database Name' and hit enter (you'll need the quotes if there are any spaces in the name). The prompt will change to indicate that you're connected to the right database.

Type this in, then hit enter:

UPDATE settings SET setting_value = '300033' WHERE setting_name = 'dbversion';

Then restart PT3 and it should attempt to upgrade your database again. Depending on how far it got in the process, this should, hopefully, just fix things for you. If it doesn't, your database is unfortunately corrupted to the point where the best solution is to create a new database and reimport your hands.

[mad1]

Unfortunately, I got impatient and did start over from scratch. I uninstalled postgres, deleted the user, (Left pt3 as is in beta27), reinstalled postgres 8.3.7, created a new db, imported 2.5 million hands, and then did a full maintenance and cache, and it completed.

I am in the program now, trying to add my aliases, and I now get this error:

http://img80.imageshack.us/img80/7735/alias.jpg

I have tried to go both ways, from the account I play the most on, to adding the smaller one, and vice versa. It gets the error both times, though different numbers in the cache.id player.

I will wait for your response on this one before I take action.

I may go back and try to restore my old database to a new one, and try your suggestion from the prompt, just for argument sake.

[mad1]

Also, I wanted some clarification on creating a new database. Must I use sql_ascii for the encoding type, or will UTF8 work? A friend told me that UTF would be fine. Could that be causing any errors?

[mad1]

Ultra depressing.. I just saw the solution for this. It's a shame I wasted 7 hours just now doing maintenance, only to have to undo it.

[mad1]

Close PT3. Click Start --> Programs --> PostgreSQL --> psql to 'postgres'. At the prompt, type \l and hit enter, this will list your databases. Then type \connect 'Your Database Name' and hit enter (you'll need the quotes if there are any spaces in the name). The prompt will change to indicate that you're connected to the right database.

Type this in, then hit enter:

UPDATE settings SET dbversion = '300033';

Then restart PT3 and it should attempt to upgrade your database again. Depending on how far it got in the process, this should, hopefully, just fix things for you. If it doesn't, your database is unfortunately corrupted to the point where the best solution is to create a new database and reimport your hands.

ERROR: column "dbversion" of relation "settings" does not exist
LINE 1: UPDATE settings SET dbversion = '300033';

That is the error I received after copy pasting your command

[aslakator]

Ive got the same problem.
I made a new database, still it wont import and - update settings set dbversion = '300033'; - doesnt go right

[ChromaKey]

Before you upgraded to Beta27; did you do a full pgdump? to different media? If so, surely you can rollback to this and start the upgrade again with the errant HDD fixed?

[kraada]

If you created a new database in Beta 27 you shouldn't need to follow any of these directions. New databases in Beta 27 should just work.

I double checked the command line from earlier and it does look like I mistyped slightly; the correct command should be:
UPDATE settings SET setting_value = '300033' WHERE setting_name = 'dbversion';

I've updated the earlier post to reflect the proper command.

[aslakator]

WTF am i doing wrong??!!
ERROR: relation "settings" does not exist
when typing: UPDATE settings SET setting_value = '300033' WHERE setting_name = 'dbversion';

Should i change something from the row or just type it like it is?

I hope this update was worth this...