How to I transfer my old database to my new computer?

[WaterWorks]

I have just upgraded my old desktop to a new PC. Everything works except for old data is missing. I have tried taking my database and copying it to the new PC. But this does not work for me as the file is over 1.5 gig.  Does someone have a procedure for doing this.

Running Lookout 6.02.

[WaterWorks]

I have tried to archive the data and move it. However the process hangs when it is 75% complete.

This could be related to a memory problem as I have less than 1 gig of free memory space and the database is 1.5 gig.

If any one has suggestions it would be aprreciated.

[Ryan.S]

To archive the data by MAX to the remote database is a good way. I assume that you already know how to do it, since the process is 75% complete. It is possible that one or more data files in database is corrupted which causes the archiving to hang. You can try to archive the database step by step. For example. you have data from 2008 to 2009, you can just archive one month each time. In this way, if one month's archive fails, you will know which part of data has the problem.

Another way is to copy the files as you said. You can share the database folder, and copy to the remote. For example, on old computer, right click on database folder, select Properties. Go to Sharing tab, check "share this folder", click Apply. Then go to "Security" tab, click add, input everyone, OK. THen check "Read" and "List Folder" for "everyone". On the new pc, select Start->Run, input \\oldcomputername. Then you will see the shared folder. Just copy all files to a folder on new pc. In MAX, create the database for the database folder.

[WaterWorks]

Thanks Ryan,

I do believe some of the data is corrupt as you suggest. I will try to archive month by month later today.

I did manage to get the database transferred by detaching the database. This then allowed me to copy the file to a flash drive. I had been unable to copy it before, because I would get an error message, saying the file was in use.

So I have the database transferred now. 

However I am getting multiple traces in Hypertrend now. That is for each tag there are multiple lines showing on the Hypertrend screen. Some are giving the expected data and other lines of the same color show straight lines.

Is there a way of cleaning up these multiple traces?

If I archive month by month can I recover all the data to the new database?

Message Edited by WaterWorks on 02-13-2009 08:45 AM

[WaterWorks]

I am not happy.

I have given up trying to get the old data.  Any time that I do manage to recover it, once I start trending I get multiple traces of each item that I am trying to trend in Hypertrend. 

The data does appear to be ok when I look at it in Citadel 5.  I have uninstalled and reinstalled both lookout and Max Citadel 5  to no avail.

I have thrown out my old databases out and started with fresh databases.

However hypertrend is still doing multiple traces.

Answers please.

[Ryan.S]

Could you provide a screenshot of the hypertrend display?

Please also take a look at this KB

http://digital.ni.com/public.nsf/allkb/230017406BDDAFF686256DF3006FD57A?OpenDocument

Is the "horizontal lines" described in the KB like the one you saw? But if the problem exists when you use a fresh database, your issue is not the same.

I want to confirm with you that the Lookout on new pc is 6.0.2, not 6.0. We did have some bugs in Citadel which cause the incorrect display, but they are fixed in 6.0.2.

Please upload your process to ftp://ftp.ni.com/incoming. I will try to reproduce the problem with 6.0.2.

[WaterWorks]

Hi Ryan,

I am using Lookout 6.02.

On Friday I deleted all the databases and then created a new database. I then started Lookout and left run over the weekend.

I had the customer look at the trends this morning and they are still still adding the extra traces. However they seem to correct themselves and then awhile later the extra trace starts again.

I am sending you the process file for the server and the client. 

I am also sending you two screen shots of the Hypertrends.

Zipped  files are labeled server_district_taylor

I can send the database also if you want.

Message Edited by WaterWorks on 02-16-2009 11:16 AM

Message Edited by WaterWorks on 02-16-2009 11:17 AM

[Ryan.S]

I'm not able to reproduce the problem on my computer. Have you installed the lookout 6.0.2 updates? You can download it from http://joule.ni.com/nidu/cds/view/p/id/506/lang/en. Unzip the lo602_updates.zip and copy to the lookout 6.0.2 folder. It has an updated hyper.cbx. Copy hyper.cbx to both server and client folder and overwrite the current one. The lkworks.dll is for server system, don't copy to client software.

If the problem still exists with 6.0.2 updates, I'd like you to try the hyper.cbx from Lookout 6.2. I attach it here. Please backup the 6.0.2 hyper.cbx first, move it to another folder, and then copy this 6.2 hyper.cbx to lookout folder. We did have similar problem before, but it seems to be fixed. So I want to check if the 6.2 hyper.cbx has fixed this problem.

[WaterWorks]

I closed out lookout and renamed the files for the updates by adding .backup. I then copied the update files into the Lookout folder. I started Lookout again and checked my trends. They are worse than before, now there is up 5 traces for each tag. I shutdown and tried installing hyper.cbx for 6.2 but I get the same thing happening if not worse.

It was at this point that I noticed the time in Lookout (bottom left corner) is jumping all over the place. It will randomly jump forward two to three hours and then back again.  I do not know if it was doing this before the updates. I removed the update files and reinstalled the orginal files but now see the same thing happening.

I will seach the forum to see if any one else has had this problem.  I suspect this may be the cause of our multiple traces.

[Bob_L]

WaterWorks,

You may want to view threads relating to time shifting etc. There have been repeated reports of the Lookout time advancing 1+hr and then recovering to the correct value. This creates horizontal lines between a current time and a future incorrect value.

Bob .