Issue
There is a possible corruption of the SQL Database and the DCUxxxx.sav files when upgrading I/NET Seven from Rev 1.xx to I/NET Seven rev 2.13 and above
Product Line
TAC INET
Environment
I/NET site 1.xx
Cause
Corruption of the SQL Database and the DCUxxxx.sav files
Resolution
- If you do a fresh install of Inet Seven 2.13 and above and restore an Inet Seven rev 1.xx SQL DB. There is a possibility of having the SQL Database and the DCUxxxx.sav files getting corrupt if you do not properly save the NETCON file. The example below is an Inet Seven rev 1.06 SQL database that was restored to a fresh install of Inet Seven rev 2.14. This is what the NETCON file looks like; if you do a station restore at this point you will corrupt the system. Look at step 2 for the correct way to handle this.
- Taking the above example and changing it to look like the one below will prevent the corruption from occurring in the Inet Database and DCUxxxx.sav files. Please NOTE this issue will be corrected in Inet Seven rev 2.16 and above.
Note: Remember while you are in the NETCON editor; penetrate each station in the MCU summary page. Edit and Save each DPU entry so that the “Type” is correct DPU type (7910, or 7920). Also, save the revision of something close, such as 3.03 or 3.04 for the 7910 & 7920. Make sure that there are no “*”, “Blank spaces” or “0.00” displayed when you are done. Also make sure you “SAVE” NETCON all the way down to the door level.
