[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

6397.0. "%MCC-E-NOTIFEXCP" by GIDDAY::CHONG (Andrew Chong - Sydney CSC ) Mon Nov 06 1995 07:08

A customer modified the map and deregistered some entities from the doamins. 
While in the process of doing that the map crashes. 

Since then, He has been unable to start some of his notifications. 

He gets :

MCC> Notify Domain TAFE:.NORTHERN_SYDNEY
%MCC-S-NOTIFSTART, Notify request 2 started

%MCC-E-NOTIFEXCP, notify request 2 encountered an exception
An error has occurred while determining the contents of the domain.


A check of the domain (show domain member *) show that there are 
some domain members that is deregistered:

	Detected a deregistered Domain Member. TAFE:.ts.bvm101 


The map file does not show the deregistered member . Checked DNS namespace
and verified that the object TAFE:.ts.bvm101 has been removed.

So, I am not sure why notification still thinks that the deregisterd entity
is in the domain. Is there a repository (MIR file) where domain members 
are kept ? 

How do I fix this problem with notification ?


Regards,
Andrew
T.RTitleUserPersonal
Name
DateLines
6397.1even if entities are deregistered they may still be in the domainAZUR::DURIFMon Nov 06 1995 11:2816
Hi Andew,

> Is there a repository (MIR file) where domain members are kept ?

When things go well an entity is deregistered and also removed from all
domains.
Looks like it was not done in your case.

Try a "delete domain xxx member yyy" to remove domain membership.

You have to reach a point were "show domain member *" gives no error because
the error you get is also seen by the notif_fm and the notification fails.

Hope this helps.

Benoit
6397.2thanksGIDDAY::CHONGAndrew Chong - Sydney CSC Tue Nov 07 1995 06:047
Benoit,

Deleting the deregistered members fixed the problem. 


thanks,
Andrew
6397.3only works for some.....GIDDAY::CHONGAndrew Chong - Sydney CSC Thu Nov 09 1995 07:0236
Benoit,

While deleting the deregistered members work for some domains, it does nor work
for some other domains. 


MCC> show domain .tcpip member .ip.merx76
Using default ALL IDENTIFIERS

Domain TAFE:.tcpip Member TAFE:.ip.merx76
AT  9-NOV-1995 16:44:44 Identifiers

Detected a deregistered Domain Member. TAFE:.ip.merx76

MCC> delete Domain TAFE:.tcpip Member TAFE:.ip.merx76

Domain TAFE:.tcpip Member TAFE:.ip.merx76
AT  9-NOV-1995 16:44:57

No such entity: Domain TAFE:.tcpip Member TAFE:.ip.merx76
                         Unknown Entity = Domain TAFE:.tcpip Member
                                          TAFE:.ip.merx76
MCC> exit


Whith these domains the notifications still fails.....

Any other ideas ?

Given that the member does not exist in the map file (*.mcc_map_tcpip) and 
the obj .ip.merx76 does not exist in dns namespace, then it must detect the 
presence of the deregistered member from some other database. The question is
which database ?


Andrew
6397.4case sensitivity in domain member namesAZUR::DURIFFri Nov 10 1995 11:0430
Hi Andrew,

All the information is in DNS.

Each domain keeps a list of its members.

Sometimes ago we had a case sensitivity problem on domain members.

May be the member was created in uppercase and now is not found using lowercase.

I suggest :
1. try to delete it using uppercase.

2. Get the new kernel and domain images on node TAEC in directory
   MCC$PUBLIC:[MCC_V140_PATCHES.DOMAIN.FIX04]

3. install them and try to delete the members.
   "delete Domain TAFE:.tcpip Member TAFE:.ip.merx76"

4. If ok : nothing more.

5. If ko : the fix will prevent the case sensitivity problem to occur again
   but does not fix the problem.

6. Keep the fix but you need to delete the domain and then recreate it with
   the members.

Hope this helps,

Benoit