VICIDIAL 2.0.3 corrupt leads!!!

[caspar]

We used VICIDIAL 2.0.2 at a call center and have recently upgraded to VICIDIAL 2.0.3 using the UPDATE instructions. I also run the /extras/upgrade_2.0.3.sql script that comes with VICIDIAL 2.0.3 to upgrade the database.

Everything seems to work fine until one of the managers did a "Reset Lead-Called-Status for this list" in VICIDIAL ADMIN. Now the list is corrupt and 11806 leads are now a big mess and the manager is not to happy. The other lists that have not been reseted are still fine.

The first_name field contains some sort of weird number that I do not know where it comes from.
The province field contains a number.
The postal_code contains a part of some string that is definitely not a postal_code.
The email address contains the alternative phone number.
Most of the other fields are blank or set to 0.

Did you guys changed the vicidial_list table structure and perhaps forgot to update the /extras/upgrade_2.0.3.sql script? Or is this a bug in VICIDIAL 2.0.3?

[mflorell]

Nothing changed in that table between 2.0.2 and 2.0.3. I am running 2.0.3 on about a dozen production systems, some of them upgrades, and I have never seen anything like issue you describe.

Does anyone have access to the database at this location? Are there any other scripts or applications that have access to the database?

[caspar]

No one access the database except VICIDIAL itself and there is also no other database applications running.

After further investigation and by looking at the source code myself, it does not make sense to me that resetting a list would cause something like this.

I also noticed it is not only the one list (although 95% of the leads are from the same list), but some leads of other lists as well. This seems very random accept that the modify_date column of all the corrupted leads are the same and shows to the exact time that the manager changed one of the campaigns from ADAPT_AVERAGE to MANUAL_DIAL mode. He said that he did nothing else. No lead importing, no resetting, nothing.

Another interesting discovery shows that the list's list_changedate = 2007-05-08 10:12:19 (time we had reseted the list), but the lead's modify_date = 2007/05/09 11:22:41 AM (time dial mode was changed).

I also though it could be the importer or that the importing file was wrong, but most of these leads are old leads that have been on the system for months.

[mflorell]

I don't know what could be causing this since I have never seen it myself. Could you post some output from some of their strange field values?

[caspar]

Here is just a few entries:

lead_id,entry_date,modify_date,status,user,vendor_lead_code,source_id, list_id,gmt_offset_now,called_since_last_reset,phone_code,phone_number, title,first_name,middle_initial,last_name,address1,address2,address3,city, state,province,postal_code,country_code,gender,date_of_birth,alt_phone, email,security_phrase,comments,called_count
10997,2007/02/08 09:16,2007/05/09 11:22,B,solomon,0,,2776702,0,Y,27,839495768,,1089998431,,MTHOMBENI NJ,,7332 PROTEA GLEN,EXT 11,NULL,SO,,,181,,0000-00-00,,114736243,,,1
12223,2007/02/13 14:06,2007/05/09 11:17,WNo,vincent,0,,2776703,0,N,27,498910054,,2220266080,,SEPKIT BM,,,,,,4,UNIVERSAL,,,0000-00-00,,498910052,,,1
12219,2007/02/13 14:06,2007/05/09 11:17,WNo,solomon,0,,2776703,0,Y,27,182911011,,1150000000,,SIZANE CA,,,,,,12,UNIVERSAL,,,0000-00-00,,182953832,,,2
12221,2007/02/13 14:06,2007/05/09 11:17,DC,vincent,0,,2776703,0,N,27,722361897,,2030264085,,NGXISHE LV,,,,,,6,UNIVERSAL,,,0000-00-00,,466530248,,,1
35543,2007/04/26 11:53,2007/05/09 11:17,A,jeanette,0,,2575,0,Y,27,832804862,MRS,CHARMAIN,,CAROTO,,,,,,,,,,0000-00-00,,119504060,,,1
10999,2007/02/08 09:16,2007/05/09 11:22,B,solomon,0,,2776702,0,Y,27,828153647,,3120184084,,DIGORO PRM,,P.O. BOX 1101,PROTEA GLEN,NULL,SO,,,181,,0000-00-00,,119821008,,,1
11000,2007/02/08 09:16,2007/05/09 11:22,DC,vincent,0,,2776702,0,Y,27,723310337,,4055924080,,NOBELA N,,8364 PROTEA GLEN,EXT 11,PROTEA GLEN,CH,,,181,,0000-00-00,,117224200,,,1
11001,2007/02/08 09:16,2007/05/09 11:22,SALE,vincent,0,,2776702,0,Y,27,721093452,,4160000000,,NGUBANE SP,,30198 MEADOWLANDS,EXT 11,MEADOWLANDS,SO,,,185,,0000-00-00,,114977135,,,2
11003,2007/02/08 09:16,2007/05/09 11:22,N,vincent,0,,2776702,0,Y,27,119882589,,10030000000,,BACA SNP,,157 PUZZLE BUSH ST.,,PROTEA GLEN,TS,,,181,,0000-00-00,,119874995,,,1

I know it is difficult to read this in the forum, but when you save this to a .csv file and open it with a spreadsheet, it is much easier.

[mflorell]

I really don't have any idea what your problem would have been caused by. This doesn't look like something that an upgrade could have caused, especially since the upgrade does not alter data in that table.