PowerHome Messageboard: Trouble migrating PH to new computer

Active Topics

Memberlist

Help

PowerHome General
PowerHome Messageboard : PowerHome General

Topic: Trouble migrating PH to new computer

Author

Message

<< Prev Topic | Next Topic >>

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: March 21 2007 at 12:04 \| IP Logged

Help! (as usual when I post here)

I installed the latest PH build (1.03.4.10) onto a new XP machine (new to powerhome, that is); copied over my existing pwrhome.db and pwrhome.ini files; and ran phupgd.exe successfully. However now when I try to start power home I get an error: "An error occurred while trying to retreive registration information."

My guess is that phupgd.exe is failing as the original db (now called pwrhome.10391.db) is 788,840KB and the after upgrade pwrhome.db is only 1,328KB (the same size as the originally installed empty db.

Any suggestions?

Is it just me, or does 780MB seem a bit large for the database?

Thanks, Tony

TonyNo
Moderator Group

Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889

Posted: March 21 2007 at 12:48 \| IP Logged

Yes, 780M is large.

My db is 8M right now and I trim it every day. Just before the latest upgrade, it was 20M.

Maybe a clue: There was a problem with the distributed phupgd file...

Quote:

If your phupg.exe file is dated 2007-02-27, then you need to go to the download page and get the newest phupg.exe file.

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: March 21 2007 at 16:29 \| IP Logged

Hmm, I just downloaded the install yesterday, but you are right, my phupgd.exe is dated 2007-02-27. I'll download the newest and try again...

On another note, my pre-upgraded db is also 780MB - when you say you trim yours every day, what do you mean?

Thanks

TonyNo
Moderator Group

Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889

Posted: March 21 2007 at 20:34 \| IP Logged

i have a macro which runs every day that does a Trim Event Log 3, to only keep the last three days.

cmhardwick
Senior Member

Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290

Posted: March 22 2007 at 07:44 \| IP Logged

Same here, but I think mine's set to 7 days. Works wonders

__________________
Cicero, Enjoying automation!

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: March 22 2007 at 14:59 \| IP Logged

Ok, so I seem to have another problem. I also have a daily macro that runs to trim the ph log to 1 day. However it does not seemt to do anything. My db is now over 800M - this is clearly going to become a problem.

My trim macro simply looks like:
ph_trimeventlog ( 1 )

Am I missing something here?

smarty
Super User

Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728

Posted: March 22 2007 at 16:00 \| IP Logged

I just use a dailey timed event to call a one line macro. The "command"(from the pull down list) is TRIM EVENT LOG, and 2 is in the "Send Keys" colunm.

__________________
Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: March 24 2007 at 16:29 \| IP Logged

I would have expected the end result to be the same. So I tried Smarty's method (TRIM EVENT LOG; 1) and I get an error:

Auto Message:
An error occured while trimming the eventlog table.
SQLSTATE = S1000
[Sybase][ODBC Driver][Adaptive Server Anywhere]General Error: Unable to find in index 'eventlog' for table 'eventlog'

Any suggestions? I'm starting to get quite worried about my database's health. I don't really think I have a viable backup (pretty sure my backup has the same issues) and I have many 100's of hours invested...

Help...

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: March 29 2007 at 17:31 \| IP Logged

Anyone? Dave?

My database is still growing, and I am unable to trim the even log (see above post).

This means that i cannot migrate my installation, I cannot upgrade to the new version, and eventually (obviously) my installation is going to crash.

Help...

TonyNo
Moderator Group

Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889

Posted: March 29 2007 at 19:30 \| IP Logged

Sounds like your DB is corrupt. Dave will need to chime in.

dhoward
Admin Group

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447

Posted: March 30 2007 at 20:47 \| IP Logged

Tony,

It sure sounds as if there is a problem with the database. If you've been running trimeventlog and it's still growing, something has gotten mucked up.

Here is what I would try. Open the PowerHome Multi-Editor and change to SQL mode (shift-F5). Then type in the following SQL statement and execute it:

delete from weblog

Verify if you get a message "Direct SQL performed OK". If all is well, type and run the following SQL:

delete from eventlog

Hopefully you'll get the SQL performed OK message. If all goes well, try and upgrade again.

If it doesnt work, then I'll need to prepare some special scripts for you to hopefully export your database as best we can.

Let me know,

Dave.

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: April 02 2007 at 20:53 \| IP Logged

Ok, looks like I'm in trouble.

From PH Multi-Editor in SQL mode I typed: "delete from weblog" and hit the Execute button. All that happened is powerhome hung. From the task manager it shows PowerHome - [Script Editor (SQL) - ] as not responding, and using no cpu cycles.

It's been going for about ten minutes - I'll let it go longer, just in case it's just slow handling my monster db... but I'm not too hopefull.

Next suggestion?

Thanks!

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: April 03 2007 at 12:31 \| IP Logged

Alright, a little progress. The above sql ("delete from weblog") did actually come back with "Direct SQL performed OK" after some number of hours.

But, when I try to run "delete from eventlog" it comes back after a few minutes with an error:
Invalid Direct SQL Code -189

SQLSTATE = S1000
[Sybase][ODBC Driver][Adaptive Server Anywhere]General error: Unable to find in index 'eventlog' for table 'eventlog'

Dave, what next? My db is now over a gig and my house is not running (my wife hates when I say things like that)

dhoward
Admin Group

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447

Posted: April 03 2007 at 15:20 \| IP Logged

Well, thats not good. What version are you currently running? I'll come up with some SQL scripts to manually export you.

Dave.

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: April 03 2007 at 15:48 \| IP Logged

Thanks for the quick response!

I'm running 1.03.4.7

dhoward
Admin Group

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447

Posted: April 03 2007 at 16:40 \| IP Logged

Tony,

I have a list of scripts to run to manually export your data. You will need to open the PowerHome multi-editor or switch to SQL mode (shift-F5). You'll then copy and paste each line below one at a time and execute it.

select * from analogio;
select * from ccbuttons;
select * from cctabs;
select * from ctlrs;
select * from ctlrparms;
select * from customcolor;
select * from digitalio;
select * from digitaltypes;
select * from discs;
select * from equip;
select * from formulas;
select * from global_variables;
select * from insteondevices;
select * from insteongroups;
select * from insteonlinks;
select * from insteontypes;
select * from ir;
select * from macrodetail;
select * from macroheader;
select * from playlistdetail;
select * from playlistheader;
select * from slots;
select * from timedevents;
select * from tracks;
select * from triggers;
select * from userdata1;
select * from video;
select * from voicedetail;
select * from voiceheader;
select * from x10devices;
select * from x10types;

You should get a SQL Query Report window opened with each line executed. With a report window as the current window, go to the menu File|Export. In the Save As window, set the save as type to "SQL" and make sure that the filename is the name of the table. So, with the very first line, the save as filename will be "analogio" without the quotes. After saving, close the SQL Query Report window and go to the next table.

See if you can get all of the tables exported. With the condition of your database, you may not be able to. If you can get the data exported, let me know and I'll help you with the next step.

Dave.

dhoward
Admin Group

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447

Posted: April 03 2007 at 16:43 \| IP Logged

1.03.4.7....hmmm, some of the tables in the list above MAY not exist. For instance, you probably won't have an INSTEONGROUPS table.

See what exports and let me know what problems you encounter.

Dave.

onhiatus
Senior Member

Joined: May 12 2004
Location: United States
Online Status: Offline
Posts: 279

Posted: April 04 2007 at 11:58 \| IP Logged

Phew! All done. It took me several hours to get my machine to boot - I need to get this exported quickly, my current machine is dying.

Anyway I've saved all of the above tables as SQL files named after the table. Note that you were right, the "insteongroups" table did not exist - all other tables did exist and were saved (many were empty, but I still saved them)

Now what?

Interestingly, all 30 tables in SQL format are only about 155KB. What is the other 990MB in my database...

Thanks again, you're a life saver! Tony

cmhardwick
Senior Member

Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290

Posted: April 04 2007 at 12:56 \| IP Logged

My guess is the event logs ... since it looked like the trimeventlog wasn't working. That's alot of activity :)

Good luck, glad it's working so far Tony!

__________________
Cicero, Enjoying automation!

dhoward
Admin Group

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447

Posted: April 04 2007 at 21:21 \| IP Logged

Tony,

Yep...the eventlog is what would be taking the other 990MB and consequently wasnt exported.

Ok...so far, so good. Copy those files off somewhere because this is the essence of your PowerHome setup.

Next step is to shutdown PowerHome. Rename your existing database from pwrhome.db to something else. In the database directory, there should be a file like ph10391.db. This will be a blank copy of your existing database format. Make a copy of this file (dont rename it) and name the copy pwrhome.db. Restart PowerHome. You won't have any registration information so you'll need to re-enter your original Reg name and then register with your unlock code. If you've lost this information, no problem, just use an appropriate reg name and I'll send you the appropriate unlock code for what you used.

With your new, fresh, pwrhome.db database up and running, launch the multi-editor. Make sure you're in SQL mode and then use the open file icon on the toolbar and read in your first saved SQL file. Execute the SQL. You should get a Direct SQL Performed OK message. If all is well, read in the next file and so on. When you're all done, you should have a rebuilt database and a much more reasonable size.

If all goes well, you should then be able to delete the 1GB monster and then begin your original upgrade process to 1.03.4.10.

Good luck and keep me posted.

Dave.

Page of 2 Next >>

Printable version

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum