Index rebuild - record already exists

C

chakkucit

New Member
Hi ,

I am getting below message during index rebuild. Can i ignore this message or any issue. Please help.


[2012/02/14@15:34:26.140733193388632+0800] P-1187 T--1371646208 I : (1127) Fix RECID 461095, um_mstr already exists with Unit of Measure "¶à Alternate UM "no" Item Number "".
[2012/02/14@15:34:26.140733193388633+0800] P-1187 T--1371646208 I : (1127) Fix RECID 461095, um_mstr already exists with Item Number "" Unit of Measure "¶Ã" Alternate UM "no".
[2012/02/14@15:34:28.140733193388680+0800] P-1187 T--1371646208 I : (1127) Fix RECID 854, code_mstr already exists with Field Name "pt_um" Value "¶Ã".
[2012/02/13@22:49:22.140733193388691+0800] P-11349 T-432027392 I : (1127) Fix RECID 299, code_mstr already exists with Field Name "AD_STATE" Value "ÆäËü".
[2012/02/13@22:49:22.140733193388698+0800] P-11349 T-432027392 I : (1127) Fix RECID 8192, code_mstr already exists with Field Name "xx_salutation" Value "ÆäËü".
[2012/02/14@02:11:53.140733193388254+0800] P-20629 T--935852288 I : (1127) Fix RECID 346, code_mstr already exists with Field Name "AD_STATE" Value "ÆäËü".
[2012/02/14@02:11:53.140733193388257+0800] P-20629 T--935852288 I : (1127) Fix RECID 4415, code_mstr already exists with Field Name "xx_salutation" Value "ÆäËü".
 
Looks to me like you've somehow got duplicate values in indexes that are set as unique. I would suggest you need to look very carefully at the messages and tidy up the data that is duplicated as you have no idea what impact this may have.

Just my opinion - I've never actually dealt with this sort of error before.
 
Of course you can - but I would not advise you to. When you start an index rebuild the index gets deactivated automatically and it can't be activated until you fix the problem - in your case the duplicate records. Chances are that the application is missing the index and procedures that use it won't run anymore. Therefore, unless you don't need the index, you must fix the duplicate records.

You must identify the duplicate and delete it from the database. You will find RECID of the concerned records in the error message which allows you to find the record and display it. Next you need to find the original record based on the information in the error message and compare them. Then, when you have identified the duplicate, you can delete it. After you have fixed all the duplicate records issues you can start the index rebuild again.

It would be nice to know how the duplicate records got into the database in the first place. Do they have just appeared over time or did you load a binary dump file, or an ascii dump file with the bulk loader twice (both of this steps will deactivate the indexes on the concerned table)?

Heavy Regards, RealHeavyDude.
 
The alternative solution is to take the unique flag off the index, but that might break your data integrity... My personal preference is not to have the unique flag set on indexes, but to maintain this uniqueness in your own validation. But that's just me! :)
 
Actually... You should contact tech support about this but I think that the index rebuild is effectively removing the duplicates when it reports them.

Duplicates like this can arise in several ways. Mostly via bugs. Knowing the specific version of Progress might be helpful.
 
Actually... You should contact tech support about this but I think that the index rebuild is removing the duplicates when it reports them.

Duplicates like this can arise in several ways. Mostly via bugs. Sometimes maybe due to HW failures. Knowing the specific version of Progress might be helpful. Tech support will definitely want to know.
 
You must log in or register to reply here.
Back
Top