[O&M Master] Automatic CRC Error of Data Tables on MSC's .:victory:

Handling Process

We collected below data to troubleshoot this issue .

LST ME:; 
LST PATCH:;

DSP PATCH:;

DSP CPATCH:;

DSP OMU:;

LST WKSP:;

LST SYNC:;

EXP ALMDATA: FNAME="alminfo_all", CLR***=ALL, EFMT=CSV, CF=COMPRESSED;

EXP ALMDATA: FNAME="alminfo_unclear", CLR***=UNCLEARED, EFMT=CSV, CF=COMPRESSED;

EXP MES: EXPTYPE=TEXT, TBNAME="tbl_sm_log";

1) Log in to the LMT. Choose Maintenance > File transfer service to start the FTP tool.

2) Select OMU run log in Remote Directory and download  cm, mm, mt folders to the local PC.

3) Select Export file in Remote Directory and choose fm->alarminstance->manualexprot->alarm,download alarminfo_all_CSV.tar.gz and alarminfo_unclear_CSV.tar.gz to the local PC.

4) Select Backup in Remote Directory and download exp_datatool-> exp_datatool_ALL_TBL_SM_LOG.tar.gz to the local PC.

Root Cause

According the cm log, it show the table 966 TBL_LICI_USERINFO inconsistency.

It means the LIG side begin setting targets to OMU at that time, if the time is same with STR CRC, it maybe cause the CRC error.

it is a fake alarm because STR CRC is conflicted with set target from LIG.

At that time, the tbl 966’s record is written to database, but not format to .dat file yet. So the CRC error occur.

Later the system will auto format to dat file, and then run STR CRC again, it will no any CRC error.

LM_ERROR:     Thu Jun 23 2016 03:06:38.348307  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(2), MODULENO(1302), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.348550  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(3), MODULENO(1302), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.348746  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(2), MODULENO(1303), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.348966  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(3), MODULENO(1303), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.349162  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(2), MODULENO(1304), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.349348  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(3), MODULENO(1304), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.349534  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(10), MODULENO(1305), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

LM_ERROR:     Thu Jun 23 2016 03:06:38.349719  2939866016     (LWP 11845)  [DB]MEID(5), FRAMENO(0), SOLTNO(11), MODULENO(1305), TABLEID(966), TABLENAME(TBL_LICI_USERINFO)'s CRC is inconsistency.    in cm_business_handle.cpp(2213)

Solution

 STR CRC: CRCTYPE=ALL; in CGP and MSX window