Alcatel Unleashed

Hi all,

We had 3 nodes of OXE, in one of the node we had a Huntgroup and in other 2 nodes I have a network number prefix routing to that huntgroup. The problem is that, for some emergency purposes we shutdown and removed the node where huntgroup was located, and now we are unable to delete or modify the network number prefix from other 2 nodes. We want to use the same prefix number for something else.

The error I am getting while deleting or modifying is :



┌─Error:───────────────────────────────┐
│ │
│ Press CANCEL to remove this window │
│ │
│ processing Failure │
│ OBJECT -1: Number: invalid Operation │
│ │
└──────────────────────────────────────┘

When network HG deleted on reference node and exist in another nodes (broadcast problem) - we remove this TG with audit.

In your case - if HG reference node not exist - I think you need to remove this number from database with "cuser" command. I cannot say exactly from which tables (HG, translator, prefix plan).

Hi MAY BE ith multitool REPAIR
you can change the reference node of the huntgroup for any node to the local node after you can remove it from Prefixplan

I guess multitool repair is for keys or supervised sets, can I use it for prefixes too?

from my practice - you can do something with network HG only from reference node. On local node - you can just add/delete local users from HG.

if reference node - not exist - I think - only cuser help you.

sorry for the confusion i think the good command is µ>pbxstat menu and choose option 2
i remenber i was facing similar issue , i was able to delete the prefix only after changing the refernce node of hg in th concerned node where to delete the prefix
it was already given by vad
(1)pst_cpu6> pbxstat menu

Tue Oct 28 09:19:05 CET 2014


GPBX (Hunting group) modification :
-------------------------------------
Modify the directory number of the GPBX : 1
Modify the reference node of the GPBX : 2
Modify the type of a GPBX : 3
Insert a network set into a group : 4
Display hunting group datas : 5
Display the table of network directory number: 6
Remove a network set from a hunting group : 7
Modify the distribution mode : 8
Display a queue of a hunting group : 9
Updating the queue of a GPBX : 10
Updating the index of chained term : 11
Search of chained term : 12
Personal call pick-up : 13
Quit this tool : 0

Enter your choice : 2
Enter the hunting group number to modify : (1)pst_cpu6>

I have never tried
but found
>multitool CLEANGPBX
option 13
ofcorse mao should be off before running cleangbpx

Dear Haroun,

I used pbxstat menu command and modified the reference node but it didnt take effect on the prefix, its still same, also CLEANGPBX is not showing me this huntgroup.

Dear Vad,

Can you please tell me how to use cuser? because I am getting following error ;

(2)eccc06> cuser
Database dictionnaries corrupted
or you are not in a database directory
Connection failed (Error = -10000)

[quote="Xero"]Dear Haroun,

I used pbxstat menu command and modified the reference node but it didnt take effect on the prefix, its still same, also CLEANGPBX is not showing me this huntgroup.
under the Groups have you the corrupted HG crated
mao should be off before using that command , may be reboot is necesary
can you out put
>cdmao
>checkdb

Yes I know, I did turn mao off. Also I donot find this HG in the groups.

output of checkdb as you asked :

(1)nhoa10>
(1)nhoa10> checkdb
Data base checking in progress ...
/........ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. <
200 rack=2 coupler=26
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
2 coupler=24
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
2 coupler=17
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
2 coupler=15
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
1 coupler=5
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
2 coupler=1
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
5 coupler=5
ERROR 4351 : DATA INCONSISTENCY, Table HARDCONF, cause=Synch. prior. < 200 rack=
5 coupler=11
........ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=2 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=3 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=103 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=5 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=10 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=11 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=12 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=13 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=15 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=105 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=101 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=100 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=102 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=6 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=150 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=176 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=175 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=20 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=4 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=140 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=7 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=25 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=182 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=183 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=185 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=29 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=30 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=8 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=180 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=250 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=245 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=244 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=9 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=16 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=18 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=22 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=19 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=90 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=62 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=255 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=64 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=228 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=129 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=51 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=91 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=60 invalid cdt
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=17 invalid cdt
...................../