check your database
-
sappe
when i check my data base with this (checkdb) command it says....
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=1
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=2
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=3
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=5
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
can u tell me about this ?
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=1
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=2
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=3
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=5
ERROR 2656 : DATA INCONSISTENCY ENTITY info3=4000
can u tell me about this ?
-
chris.raper
checkdb errors
seeing errors in your checkdb is not 'normal'.
the errors you are seeing are relating to a misconfidured entity. it looks like the translator does not know about the number 4000 and that it is in the entitys routing table, alternatively it may be an invalid answer point....
check the CDT destinations in your entity and make sure they all exist in the translator... also make sure you have an 'overflow routing number" in the entity CDT's.
the command 'checkdb' should not display any errors when ran, if it does, it means there are misconfigured parameters in the database, or database corruption.
enjoy and good luck
the errors you are seeing are relating to a misconfidured entity. it looks like the translator does not know about the number 4000 and that it is in the entitys routing table, alternatively it may be an invalid answer point....
check the CDT destinations in your entity and make sure they all exist in the translator... also make sure you have an 'overflow routing number" in the entity CDT's.
the command 'checkdb' should not display any errors when ran, if it does, it means there are misconfigured parameters in the database, or database corruption.
enjoy and good luck
-
la_toupie
-
chris.raper
entity CDT
check tech comm 0410. released 15-01-2003
Subject:
Subject:
Amongst other information:RISK OF MISFUNCTIONING IF THE MANAGEMENT OF OVERFLOW DIRECTORY UMBER OF ENTITIES/ATTENDANT GROUPS IS NOT PERFORMED
3. SOLUTION
Manage the various overflow directory numbers until the checkdb et telephone application incidents dissappear.
-
wizzy
-
freedom
It is not uncommon that there are entity messages in checkdb command. As mentioned above, it is possible that you have some strange behaviour when these errors occure.
In one case a customer complained about losing calls.
Callers complained to the customer that there was no answer for some time and suddenly the call was terminated.
After some research (also using checkdb) the problem was in the CDT of the entities. They were not filled in completely.
There were some empty lines in the entities.
If there was no answer for some time the call went to the overflow extension (which wasn't there).
After that the call was routed to entity 0.
This one wasn't filled in at all, so the call was terminated.
This is just one example of what the errormessages using checkdb can indicate.
Freedom
In one case a customer complained about losing calls.
Callers complained to the customer that there was no answer for some time and suddenly the call was terminated.
After some research (also using checkdb) the problem was in the CDT of the entities. They were not filled in completely.
There were some empty lines in the entities.
If there was no answer for some time the call went to the overflow extension (which wasn't there).
After that the call was routed to entity 0.
This one wasn't filled in at all, so the call was terminated.
This is just one example of what the errormessages using checkdb can indicate.
Freedom

