[SOLVED] ERROR 4351 : DATA INCONSISTENCY

wizzy · Post by **wizzy** » 23 Nov 2006 12:00

Data base checking in progress ...
/............ERROR 4351 : DATA INCONSISTENCY, Table POSTE, station=0003 func_moc=0 neqph
..ERROR 4351 : DATA INCONSISTENCY, Table TABGPBX, pbx_nbr=0 nulog=40

any ideas ????

Post by **frank** » 23 Nov 2006 12:52

try

cdmao

fichges -force_recover_dico

wizzy · Post by **wizzy** » 23 Nov 2006 13:04

What does it ????

I have this problem on a productive system

Is it dangerous ?????

spring · Post by **spring** » 24 Nov 2006 04:07

Referring to TC0410, the incident number 4351 is due to the overflow number od Entity and attendant group is empty or incorrect

Post by **vad** » 24 Nov 2006 04:56

Error during database check and incident number - a not the same.

spring · Post by **spring** » 25 Nov 2006 00:35

Here is the content of TC410
1. PROBLEM
Risk of misfunctioning if the management of overflow directory number of entities/attendant groups is
not performed.
Concerned releases
All.
2. CONSEQUENCE
Misfunctioning such as backtraces or unexplained CPU reboot.
Memory corruption on private/public incoming calls if the final destination is one of these directory
numbers.
These misfunctioning do not occur immediately.
The checkdb command is used to check the status of entity management: an incident is sent for each
entity or attendant groups if the overflow directory number is wrong or not correctly managed.
Examples of incidents
4351=Data inconsistency : appli INITREM table ENTITY cause invalid cdt info 0 -1 â€“1
ô€ƒŽ Manage the overflow directory number.
ERROR 4351 : DATA INCONSISTENCY CDT cdt not initalized info1=1 info2=0 info3=-1
ô€ƒŽ Wrong management of overflow directory number (attendant group call distribution) : the
directory number is wrong.
ERROR 4351 : DATA INCONSISTENCY CDT cdt not initalized info1=0 info2=1 info3=-1
ô€ƒŽ Wrong management of overflow directory number (attendant call distribution) : the directory
number is wrong.
01/10/02 08:26:28 000001M|00/11/0/000|=3:1307=MCDU tab distri entite 1, col Day, lig 4
incorrect ou absent
3. SOLUTION
Manage the various overflow directory numbers until the checkdb et telephone application incidents disappear.

cavagnaro · Post by **cavagnaro** » 25 Nov 2006 10:53

Spring, the error you mention is when you execute incvisu under the command line, when running checkdb command the error ID can be the same but not the meaning of the error.

wizzy · Post by **wizzy** » 04 Dec 2006 02:38

Here is a new one

ERROR 4116 : 0 0 32 3 108 97 114 105 115 97 0 0

wizzy · Post by **wizzy** » 07 Dec 2006 11:18

Anyone knows about this error on checkdb ???

Post by **tot3nkopf** » 07 Dec 2006 15:49

You simply have a database incoherency. You can manualy check the SQL tables to see which one is station 0003 (in one of the tables you find there you will get the correspondence between 0003 and interior number). maybe you can fix this by deleteng and recreating the interior to which station 0003 corresponds).
By the way to enter the PBX's database the command is:
cdmao
/usr/fab/cuser . m
and you're in.
Enjoy (you need some SQL commands though).
To view certain fields from DB for example use something like:
"select numan from poste" to extract the numan field from "poste".

Hope that helps.