Conference azur::mcc

    Geert,
    
    Glancing over this quickly, it seems that you may have a read-only
    replica of a directory that is out of synch with the master.  This has
    happened to me on occasion with other products.
    
    Try doing an update on all directories from the DNS$CONTROL program.
    This should be done from the Master directory server node.
    
    $ MCR DNS$CONTROL
    DNSCP> UPDATE DIRECTORY .
    DNSCP> UPDATE DIRECTORY .DNA_NODE
             .
             .
             .
    
    
    You should also be sure to check that CONVERGENCE is set HIGH so
    updates occur when anything gets changed.
    
    -Dan

 Dan,
    
    Thanks for the reply.
    I did an update of all directory's an child directory's on the master
    replica server node and repeated the tests with the read-only replica,
    but the problem still exists.
    To install the Kernel patch we deregistered every entity from mcc
    and removed all objects concerning mcc from the namespace. After
    installing the patch everything was registered again via a command
    procedure. Would it be a good idea to remove the read replica
    completely and reinstall it again and then copy all the directory's
    from the master ?
    
    Attached is a log from some commands that are failing.
    
    -Geert-
    
-------------------------------------------------------------------------------
    
MCC> show domain .b5.domains.bat_e mem *
Using default ALL IDENTIFIERS

Domain CAT$EUR_NS:.b5.domains.bat_e Member CAT$EUR_NS:.B5.STATIONS.E30D02
AT 26-JUN-1992 09:20:22 Identifiers

The requested operation cannot be completed
                      MCC Routine Error = %MCC-E-NOATTRIB, no such DNS attribute
MCC> show domain .b5.domains.bat_e mem .B5.STATIONS.E30D02
Using default ALL IDENTIFIERS

Domain CAT$EUR_NS:.b5.domains.bat_e Member CAT$EUR_NS:.B5.STATIONS.E30D02
AT 26-JUN-1992 09:21:34 Identifiers

Examination of attributes shows
                             MemberName = CAT$EUR_NS:.B5.STATIONS.E30D02
 
    
   

Geert,

	Have you installed the DNS server patch ? If not some binary 
	attributes will not be correctly copied to the read only replica.

	The DNS patch in this reply is a field test patch I recived
	from DNS engineering. After you have installed the patch you have
	to recreate your DNS READ only replica to make it work.

/Stefan

P.S	You also have to be careful to copy all DNS directorys to the READ only
	replica, if not wild card show commands don't work that grate.

$! see below for details of patch
$! To install, simply run this .com file.
$! 
$    verify_save 	= "noverify"
$    if f$verify() .eq. 1 then -
	verify_save = "verify"
$    default_save 	= f$environment("default")
$!
$    if f$trnlnm("exe$dir") .eqs. "" then -
        define exe$dir sys$system, sys$library
$!----------------------------------------------------------------------------
$    file		= "dns$lib.exe"
$!----------------------------------------------------------------------------
$    x 			= f$search("exe$dir:''file'")
$    if x .nes. "" then -
	goto filefound
$    write sys$output "File ''file' not found"
$    exit
$!
$filefound:
$    defdir		= f$parse("''x'",,,"device") -
			+ f$parse("''x'",,,"directory")
$    on control_y then - 
	goto cleanup
$!
$    set verify 
$    set default 'defdir'	! force updated file to same directory
$!
$    patch 'file'
!
!  Patch to DNS$LIB.EXE in V1.1 to fix dns$names_simplematch such that NULL
!  simplenames collate lower than all other types.
!  (ref module NAMES_LIB in DNS 1.1 listings)
!  This is to fix a problem which manifested itself under MCC wherein
!  attributes with binary (as opposed to normal) names on objects, were not 
!  copied when the directory in which the objects resided was replicated
!  (ie. using DNS$CONTROL COPY DIRECTORY command). Any binary named attributes
!  would not be returned for requests serviced by the clearinghouse containing
!  the directory replica.
!
	set eco 1
	define simplematch=420D
	define x=simplematch-0C
	repl/i x+0E
!					make room for JMP to patch area
		'MOVAB   W^0FDF8(SP),SP'
		'MOVAL   W^0FDFA(FP),R3'
		exit
!					restore instructions replaced by JMP
		'MOVAB   W^0FDF8(SP),SP'
		'MOVAL   W^0FDFA(FP),R3'
!					now for the inserted code
		'MOVL	B^04(AP),R1'	! name1 addr
		'MOVL	B^08(AP),R2'	! name2 addr
		'CMPB	(R1),#0'
		'BNEQ	L2'		! name1 type not NULL
		'CMPB	(R2),#0'
		'BNEQ	L1'		! name2 type not NULL
		'MOVL	#0,R0'		! both NULL - return EQL
		'RET'
	'L1:	 MNEGL	#1,R0'		! name1 NULL, name2 ^NULL - return LSS
		'RET'
	'L2:	 CMPB	(R2),#0'
		'BNEQ	L4'		! name2 type not NULL
		'CMPB	(R1),#0'
		'BNEQ	L3'		! name1 type not NULL
		'MOVL	#0,R0'		! both NULL - return EQL
		'RET'
	'L3:	 MOVL	#1,R0'		! name1 ^NULL, name2 NULL - return GTR
		'RET'
	'L4:	 NOP'			! continue in original code
		exit
	UPDATE
	EXIT
$    if .not. $status then -
	goto cleanup
$    x=f$environment("DEFAULT")+file
$    if f$file_attributes(x,"KNOWN") then -
         install replace 'x
$cleanup:
$    set default 'default_save'
$    set 'verify_save'
$    exit

    
    Stefan,
    
    I didn' know about this patch. Can we install this 'field test' patch 
    @customer sites or do we need approval from engineering ?
    
       -Geert-

      	Geert, I recived the patch in october when I reported this problem
	thru official channels. And yes I have installed this patch at customer
	sites, but if you want to be sure then ask DNS engineering.

	/Stefan

	P.S. Some where in this conferanse there is a topic about this.

    Stefan,
    
    I finally decided to install the patch on the machine of the customer
    and it works. Thank you very much for your help.
    
    Regards, Geert.