|
The Problem The upgrade of the company database stopped with an error in the VAT10301 'VAT Line item Work file" table. Utilities reported error "Other error (135)" saying "The conversion Process encountered an error and the Temporary table did not get removed". This table appeared to be empty so the choice of "Update Again" was taken and the Company database appeared to complete the upgrade successfully, however unknown to anyone there was a problem with the GL tables. On launching eEnterprise and checking Cards - Financial - Account there was an error on reading the first record from the GL. "A get / change next operation on table 'GL_Account_MSTR' failed accessing SQL data", "More Info" revealed 3 invalid Column names 'ADJINFL', INFLAREV'. INFLAEQU'. When I checked the GL_Account_MSTR with "Select * from GL00100" I found three columns missing. Indeed the columns 'ADJINFL', INFLAREV'. INFLAEQU' were nowhere to be seen. The Fix To fix the problem I restored the data and ran Dynutils from eEnterprise 6.0 again and proceeded with the upgrade until the error in the VAT10301 'VAT Line item Work file" table was presented. This time I choose the "Ignore Error" option in the "Table Error Detail" screen. Dynutils then proceeded to complete the update of the Company database where I was presented with a big green TICK . So what about the VAT10301 table which did not get the update. Well as there appeared to be no data in the VAT10301 table, I removed the table at database level and recreated it with the relevant code from table, procs and Index.cmp. From the lack of feedback from the Team working at NMM there seems to have been no problems with this work around to the problem. Epilogue So how did I work this out? Read through what happened, what I did, who I spoke to and what scripts I used to come to this fix and its eventual resolution. Richard 24th July 2001 Back |