check your database

All those commands that we don't really use very often, but that we should ! Documented or not, they worth it !
User avatar
frank
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3404
Joined: 06 Jul 2004 00:18
Location: New York
Contact:

check your database

Post by frank »

with checkdb !
Code Free Or Die
sappe

Post by 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 ?
User avatar
frank
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3404
Joined: 06 Jul 2004 00:18
Location: New York
Contact:

Post by frank »

it's "normal" ..
Code Free Or Die
sappe

Post by sappe »

thanks
chris.raper

checkdb errors

Post by chris.raper »

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
la_toupie

Post by la_toupie »

Since I do Alcatel4400, I've these incident and the incidents about entities are ,from Alcatel, ''normal'' as Franck says.

The only things to check, it's true :
- the existence of the number in CDT's entity

But I don't believe that it's that in this case...

Cu
chris.raper

entity CDT

Post by chris.raper »

check tech comm 0410. released 15-01-2003

Subject:
RISK OF MISFUNCTIONING IF THE MANAGEMENT OF OVERFLOW DIRECTORY UMBER OF ENTITIES/ATTENDANT GROUPS IS NOT PERFORMED
Amongst other information:
3. SOLUTION
Manage the various overflow directory numbers until the checkdb et telephone application incidents dissappear.
wizzy

Post by wizzy »

These errors are only a missing field in the entities. If you fill all the overflow, day mode and night mode fields, the errors will disappear.

As Frank said, it is 'normal' :D
spot the ?

Post by spot the ? »

I believe it can also cause random shutdowns, never seen it myself.
freedom

Post by 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
Post Reply

Return to “Usefull commands”