RP/MSQ 5.0 (VMS) - Request for support: Naming Agent Communication Error (Doc ID 777863.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle MessageQ / MessageQ / 5.0
Information in this document applies to any platform

Goal

DESCRIPTION:
Customer is using a primary and backup naming agent on two groups (nimi=11000 & nimi2=11100) on the same Alpha
V7.3-2 (attached dmq$init.4000_11000)
%NAM **************** Naming Agent Section ********************
NA_GROUP 11000
NA_GROUP 11100
%EOS
It appears from a third group (11001) that the Naming Agent is switching from primary to backup endlessly; for
instance (attached dmq$evl_4000_11001.log):
COM_SERVER      15-MAR-2007 18:58:15.75 E Naming agent comm error, switch to naming agent in group 11100
COM_SERVER      15-MAR-2007 18:58:18.92 E Naming agent comm error, switch to naming agent in group 11000
COM_SERVER      15-MAR-2007 18:58:19.30 E Naming agent comm error, switch to naming agent in group 11100
 ...
Setting traces on NA_SERVER (& COM_SERVER) shows up that (attached dmq$evl_4000_11000.log):
NA_SERVER        1-JUN-2007 09:18:11.26 I open_namespace_file: opened namespace file
/DMQ$DISK/DMQ$V50/dmqns/kehitys/kehitys.dnf
NA_SERVER        1-JUN-2007 09:18:11.28 I close_namespace_file: /DMQ$DISK/DMQ$V50/dmqns/kehitys/kehitys.DNF
NA_SERVER        1-JUN-2007 09:18:11.28 I close status = 0
NA_SERVER        1-JUN-2007 09:18:11.28 I Namespace entry does not exist
 and equivalent for other group (attached dmq$evl_4000_11100.log):
NA_SERVER        1-JUN-2007 09:34:37.41 I open_namespace_file: opened namespace file
/DMQ$DISK/DMQ$V50/NIMI2/DMQNS/KEHITYS/KEHITYS.dnf
NA_SERVER        1-JUN-2007 09:34:37.44 I close_namespace_file: /DMQ$DISK/DMQ$V50/NIMI2/DMQNS/KEHITYS/KEHITYS.DNF
NA_SERVER        1-JUN-2007 09:34:37.44 I close status = 0
NA_SERVER        1-JUN-2007 09:34:37.44 I Namespace entry does not exist

Attached NADIR_protection.txt (result of $ dir dmq$disk:['f$trnlnm("dmq$root")'.dmqns...]/sec) clearly shows
that for NIMI group,
file exists: DISK$SYSDISK:[DMQ$V50.DMQNS.KEHITYS]KEHITYS.DNF;1 with a standard protection.
Trying to reproduce on FRVMS02 upon email received (on 06/04/2007 02:21:50 AM), DEFAULT_NAMESPACE_PATH definition from
the DMQ$INIT.TXT file has been commented,
and only use of Dmq$user:Dmq$boot.com: $ dmq_lnm DMQNS_DEVICE        dmq$disk:['root'.DMQNS]
Several tests on DMQNS_DEFAULTPATH ("/BUS500/", "/BUS500/NAMESPACE", /BUS500/NAMESPACE ...) have
not allowed to create the DNF file, 
still hitting on error below (using Manager Utility - NA LA) hence blocking reproduction.
"file specification syntax error
%NONAME-?-NOMSG, Message number FFFFFFF6"

Questions:
 1. How is normally created the DNF file and if corrupted/deleted how to re-create it?
 2. It seems that problem is laying around DNF name which is case sensitive, but looks like converted in lowercase if
used in Dmq$Init_File?

CONFIGURATION:
MSQ 5.0 (VMS)

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms