1

Topic: error updating indexes

I have just had the attached error whilst updating index 0000004M on a standalone copy of Recorder 6.29 - this had previously run without error on our networked copy

Craig

---error message--------------------
date/time : 2019-11-07, 13:48:10, 929ms
computer name : SERTABLET
user name : Staffordshire
operating system : Windows NT New Tablet PC x64 build 9200
system language : English
system up time : 2 hours 22 minutes
program up time : 28 minutes 50 seconds
processors : 4x Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz
physical memory : 3352/8097 MB (free/total)
free disk space : (C:) 64.23 GB
display mode : 2160x1440, 32 bit
process id : $1c70
allocated memory : 51.75 MB
command line : RecorderApp.exe /1705842
executable : RecorderApp.exe
exec. date/time : 2019-04-05 13:48
version : 6.29.0.290
compiled with : Delphi 7
madExcept version : 3.0n
callstack crc : $5b5c45c7, $3bfc1c4c, $3bfc1c4c
contact name : Craig
contact email : c.slawson@staffs-wildlife.org.uk
exception number : 1
exception class : EOleException
exception message : Violation of PRIMARY KEY constraint 'PK_INDEX_TAXON_GROUP'. Cannot insert duplicate
key in object 'dbo.INDEX_TAXON_GROUP'. The duplicate key value is (BMSSYS0000052786, BMSSYS0000052786)

Craig Slawson
Staffordshire Ecological Record

2

Re: error updating indexes

I am on holiday at the moment and can't investigate properly. My first thought is that the index is not being truncated, but I can't think why. Did the Xml report give the right answer? Did you do the rebuild from within the update ,? If so try a rebuilding the  index again . When processing multiple updates  you only need to rebuild the index after the last one.

Mike Weideli
Littlefield Consultancy - IT Consultants

3

Re: error updating indexes

Mike,

I didn't rebuild the Indexe3s at all, because I was intending to do 4N-4Q, before rebuilding - no rush, enjoy your holiday

I have just tried to re-run the update (which I could have done yesterday), but today the computer reckons 4M has been applied and is now asking for 4N - is there a way to re-apply a dictionary update?


Craig

Craig Slawson
Staffordshire Ecological Record

4

Re: error updating indexes

0000004M , 4N and 4O do nothing of consequence. No need to rerun 4M if it thinks it has been run. Run 4N,4O and 4P and 4Q then try the index rebuild.

Mike Weideli
Littlefield Consultancy - IT Consultants

5

Re: error updating indexes

Mike,

It did the rest of the dictionary updates and the rebuild without further errors

Craig

Craig Slawson
Staffordshire Ecological Record