Beta 3.07.2 Install Issue

PostgreSQL is the database server used to store information. Do you have a question or are you having problem with PostgreSQL? If so, post them here.

Moderator: Moderators

Beta 3.07.2 Install Issue

Postby midas001 » Fri Jul 23, 2010 12:09 am

Hi all,

I just installed the new beta release. During the database update I received a dependacy erorr message becasue of a data view I had created. After trying to reinstall I no longer get the window that indicates the database is going to be updated. The bottom line is that no data displays in PT3 other than the player list on the left.

There are records in the database, I checked for data in a couple of the tables. i deleted the views and installed an older version over this new one with no sucess. I then reinstalled the new version... same result. FYI, the cash results are showing up with no issues.

Can I manually update the database?

Please help.

Thanks,

Bill S
midas001
 
Posts: 51
Joined: Sat Jan 17, 2009 2:46 am

Re: Beta 3.07.2 Install Issue

Postby WhiteRider » Fri Jul 23, 2010 4:42 am

Please make a Backup of your database before you change anything.

You could try setting the database version back to its previous value - what version of PT3 did you upgrade FROM?
The setting is "dbversion" in the "settings" table, but we need to know what to change the version number back to so that the correct updates are applied. PT3 should be closed when you apply the change so that when you start it again the database will be updated.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Beta 3.07.2 Install Issue

Postby midas001 » Fri Jul 23, 2010 7:40 pm

The ptversion in the settings table is now 300046. I updated from beta 3.07.1.

I have completed all the backups.

Thanks!
midas001
 
Posts: 51
Joined: Sat Jan 17, 2009 2:46 am

Re: Beta 3.07.2 Install Issue

Postby WhiteRider » Sat Jul 24, 2010 7:11 am

OK, try this:

Close PT3.
Run PGAdmin from Start > Programs > PostgreSQL > PGAdmin III.
Double click PostgreSQL Database Server (the default password is dbpass if it asks for one) and expand Databases > PT3 DB (or whatever your database is called) > Schemas > Public > Tables.
Right click the "settings" table and choose View Data > View All Rows.
In the window that pops up change the "dbversion" to 300043.
Repeat for all your databases, if you have more than one.

When you start PT3 again it should re-do the update.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Beta 3.07.2 Install Issue

Postby midas001 » Sat Jul 24, 2010 7:46 am

Bummer... While I was waiting for your reply I started at 30045 and worked my way down 300038 (the number in an older database) and still the tournament data does not populate. After changing the number to 300043 I got this message:

Error updating database: PT3_NEW
Error:
Unable to execute query: INSERT INTO lookup_positions VALUES (7, 2, 'MP+1', false, false, true, false);; Reason: Fatal Error (ERROR: duplicate key value violates unique constraint "lookup_positions_primary_key" )


PT3 is then in an ednless loop of trying to update the database and giving me the error message. I got a different error message with one of the other numbers, I think it was 300039.

Thanks!
midas001
 
Posts: 51
Joined: Sat Jan 17, 2009 2:46 am

Re: Beta 3.07.2 Install Issue

Postby WhiteRider » Sat Jul 24, 2010 8:28 am

It sounds like some of the updates were done but not others, so setting the value back won't necessarily work. That error means that setting has already been changed, though, so that shouldn't matter.

Since we don't know what has updated and what hasn't the safest thing to do will be to create a new database and re-import your hands. If you don't still have all of the original hand history files (in the PokerTracker 3\Processed folder by default), or if you have manually entered tournament results, then you should be able to export from your existing database first.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Beta 3.07.2 Install Issue

Postby midas001 » Sat Jul 24, 2010 9:22 am

Kind of figured thats we were heading!

Thanks!!
midas001
 
Posts: 51
Joined: Sat Jan 17, 2009 2:46 am

Re: Beta 3.07.2 Install Issue

Postby midas001 » Mon Jul 26, 2010 9:52 am

Well... all seemed to go well. I exported all my hands from the current database then created the database and made it the default/active database. It took several hours to import the 90,000+ tourney and 40,000+ cash hands. When I look in the tournament tab I only see 17 hands!! When I open PostgreSQL and look at the new database there are no tables in the public shcema! Help again!

This makes no sense becasue there were no error messages and the imports imported successfully.

Thanks,

Bill S
midas001
 
Posts: 51
Joined: Sat Jan 17, 2009 2:46 am

Re: Beta 3.07.2 Install Issue

Postby WhiteRider » Mon Jul 26, 2010 10:07 am

Have you selected your own screenname? In a new database "My Name Is" won't be configured automatically.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Beta 3.07.2 Install Issue

Postby midas001 » Thu Jul 29, 2010 9:29 pm

Thanks for the reminder!

The old table "lookup_tourney_table_type" had 16 records in it along with descriptions and that table is now gone. The data in "tourney_holdem_summary" has ID's in the "id_table_type" column that join with the old "lookup_tourney_table_type" "id_type" column. Should the 16 rows of data from the OLD "lookup_tourney_table_type" be in "tourney_holdem_table"? The data view I created relies on these 16 records to properly group my results.

Old "lookup_tourney_table_type" table
id_type; description
0;"N/A"
100;"SnG"
200;"SnG (1 Table)"
300;"SnG (2 Table)"
400;"SnG (3 Table)"
500;"SnG (4 Table)"
600;"SnG (5 Table)"
700;"SnG (6 Table)"
800;"SnG (7 Table)"
900;"SnG (20 Table)"
1000;"SnG (2 Max)"
1100;"SnG (6 Max)"
1200;"SnG (Qualifier)"
1300;"SnG (Speed/Turbo)"
1400;"MTT"
1500;"MTT (Heads Up)"

Thanks,

Bill S
midas001
 
Posts: 51
Joined: Sat Jan 17, 2009 2:46 am

Next

Return to PostgreSQL [Read Only]

Who is online

Users browsing this forum: No registered users and 13 guests

cron
highfalutin