Impossible to delete a user

[stseya]

Hello,
I've a problem with a user in my OXE.
it's currently deleted of my base with cuser but the numan is associate with a nulog.(command tradna ____)
My question : which table in the OXE associate the numan and the nulog??




=> sorry for my english, I'm french...

[sadim]

I supose you delete the number on poste, phoneb, tabtrad and keyboard tables.
The nulog/numan are in memory, so you must to a reset or if you want, give me the remote access number and i will remove it from memory

[stseya]

Hi , thanks for you response.

The reboot system have been effectued but the nulog associated with the numan are always in the base.
I've been deleted the user in the table "POSTE".
I will search in the another table that you notified.

Thanks.

[Eliott_DUP]

I supose you delete the number on poste, phoneb, tabtrad and keyboard tables.

POSTE numan='number';
PHONEB Mcdu = 'number';
TABTRAD number='number';
KEYBOARD poste_id = 'nulog';
You should also check:
TABRAL poste_id = nulog;
RALBIT nulog=nulog;
REPERT poste_id = 'nulog';
PIN mcdu='number';
INTERPH poste_id = nulog;
TABALARM alarm_mcdu='number';
TAB_AGENT nulog = nulog ;
WBLISTAG agent_nb = 'number' ;
CORDLESS poste_id;
...and so on...

Carefully if editing the database by hand!

PS: You should to a checkdb and a chek and repair using "multitool CHECK REPAIR" (in /usr3/mao) after your changes.

To to a reboot is necessary if you're not using listrad to modify the memory. (And it's more easy)

Sometimes it gives an idea to use the "mgr -line".

Choose your object and the memorize the ID e.g. -> 890052:S0 Bus

Then check the file /usr2/fab/obj2tbl.ref for object 890052:
Object_Identifier:Object_Name:#define:Table_Name:Access_Rights
890052:S0_Bus:OBJ_S0_BUS:T_ACCES:READ_WRITE
890052:S0_Bus:OBJ_S0_BUS:T_POSTE:READ_WRITE
890052:S0_Bus:OBJ_S0_BUS:T_S0BUS:READ_WRITE

Following this, you have to check the tables
ACCES
POSTE
and
S0BUS
if you change a S0 set.

(Revese with tbl2obj.ref)

[vad]

When you make something with cuser, really you can works with system (4740,4760) only after shutdown. Cuser works only with database on CPU HDD (not with RAM database).

[tot3nkopf]

Hi,

To know exactly what tables to search in and delete from you can create a user in your OXE with the same characteristics as the problematic one and then activate a trace:
srvtrace
traced &
then delete user and see what trace shows you and do the same with cuser for the problem user.

Hope that helps.

[stseya]

Hi, thanks for your responses.

The problem is with a DECT.
After delete in the table "POSTE", when i do a tradna command in the numan, the suscriber is always associated with a nulog.

[Eliott_DUP]

As already written just clean the other tables PHONEB,TABTRAD,... including CORDLESS too and reboot the system.

The association is in TABTRAD and in the memory.
mgr - Translator - Numbering plan
Number = Directory Number
Information = Nulog