Conference orarep::nomahs::dec_data_distributor

252.0. "DDAL$TR_MON picking wrong version of Rdb?" by svrav1.au.oracle.com::AMENDOZA () Thu Dec 12 1996 01:10

Hi,

Our customer has installed DDAL V6.0-11 in his system where he got both 
Rdb V4.2 (standard) and Rdb V6.1 (multiversion) monitors running.   His 
DDAL$TR_DB is in Rdb V6.1 format and his Rdb default environment is set 
at V6.1 ($ @sys$share.decrdb$setver 6.1 /system). 

However, whenever he tried to start DDAL$TR_MON, he is getting a bugcheck
with the following error:

 %DDAL-E-ERROR_ACCESS_TD, error accessing the transfer definition database
 -DDAL-E-SUPP, %RDB-F-WRONG_ODS, the on-disk structure of database filename 
               is not supported byt version of facility being used
 -DDAL-E-SUPP, -RDMS-F-ROOMAJVER, database format 61.0 is not compatible with
         software version 42.0
 -SYSTEM-?-NOMSG, Message number 0000BACE

We also tried stopping the Rdb V4.2 monitor and made sure that the Rdb
V6.1 monitor is the only one running.  However, it looks like that the 
DDAL$TR_MON process is always looking for Rdb V4.2.   The error in the
bugcheck this time is:

 %DDAL-E-ERROR_ACCESS_TD, error accessing the transfer definition database
 -DDAL-E-SUPP, %RDMS-F-NOMONITOR, database monitor is not running
 -SYSTEM-?-NOMSG, Message number 0000BACE

I'm totally lost on what is happening here.   I attached the Rdb logical
listing just before executing DDAL$START_TR_MON.COM. 

Any ideas what is going here?  Or I am simply missing something?

thanks,
albert.

-----------------------------------------------------------------------
On $@sys$share:decrdb$shover debug:

(LNM$PROCESS_TABLE)

(LNM$JOB_81164D40)

(LNM$GROUP_000002)

(LNM$SYSTEM_TABLE)

  "RDB$DISPATCH_IDENT" = "V6.1-0"
  "RDB$DISPATCH_VERSION_VARIANT" = "61"
  "RDBPRE" = "SYS$COMMON:[SYSEXE]RDBPRE61.EXE"
  "RDBSERVER" = "SYS$COMMON:[SYSEXE]RDBSERVER61.EXE"
  "RDBVMS$DEMO" = "SYS$COMMON:[SYSHLP.EXAMPLES.RDBVMS]"
  "RDBVMS$IDENT" = "V6.1-0"
  "RDBVMS$IVP_DIR" = "SYS$COMMON:[SYSTEST.DECRDB61]"
  "RDBVMS$LIB" = "SYS$COMMON:[SYSLIB]RDBVMSLIB61.OLB"
  "RDBVMS$OPTION" = "SYS$COMMON:[SYSLIB]RDBVMS61.OPT"
  "RDBVMS$VARIANT" = "61"
  "RDBVMS$VERSION" = "6.1"
  "RDB_13" = "TLV_13:[EDQ_DB.DATA_13]"
  "RDB_14" = "TLV_14:[EDQ_DB.DATA_14]"
  "RDB_15" = "TLV_15:[EDQ_DB.DATA_15]"
  "RDB_16" = "TLV_16:[EDQ_DB.DATA_16]"
  "RDB_17" = "TLV_17:[EDQ_DB.DATA_17]"
  "RDM$BIND_RUJ_EXTEND_BLKCNT" = "500"
  "RDM$DEMO" = "SYS$COMMON:[SYSHLP.EXAMPLES.DECRDB61]"
  "RDM$MAILBOX_CHANNEL" = "MBA546:"
  "RDM$MAILBOX_CHANNEL61" = "MBA6105:"
  "RDM$MONITOR" = "SYS$SYSROOT:[SYSEXE]"
  "RDM$MONITOR61" = "SYS$SYSROOT:[SYSEXE]"
  "RDML" = "SYS$SYSTEM:RDML61.EXE"
  "RDMLRTL" = "SYS$LIBRARY:RDMLRTL61.OLB"
  "RDMS$BIND_SORT_WORKFILES" = "2"
  "RDMS$BIND_WORK_FILE" = "DISK$SCRATCH_18:[RDB_WORK]"
  "RDMS$BIND_WORK_VM" = "65000"
  "RDMS$RMU_VARIANT" = "RMUF"
  "RDMS$RUJ" = "DISK$RUJ:[JOURNAL]"
  "RDMS$VERSION_VARIANT" = "61"
  "RDO" = "SYS$COMMON:[SYSEXE]RDO61.EXE"
  "RMUSTAT" = "SYS$SYSTEM:RMUSTAT61.EXE"
  "RMUWIN" = "SYS$SYSTEM:RMUWIN61.EXE"
  "SORTWORK0" = "DISK$SCRATCH_18:[SORTWORK0]"
  "SORTWORK1" = "DISK$SCRATCH_18:[SORTWORK1]"
  "SQL$" = "SYS$COMMON:[SYSEXE]SQL$61.EXE"
  "SQL$HELP_OLD" = "SYS$COMMON:[SYSHLP]SQL$HELP_OLD61.HLB"
  "SQL$IDENT" = "V6.1-0"
  "SQL$MOD" = "SYS$COMMON:[SYSEXE]SQL$MOD61.EXE"
  "SQL$MSG" = "SYS$COMMON:[SYSMSG]SQL$MSG61.EXE"
  "SQL$PRE" = "SYS$COMMON:[SYSEXE]SQL$PRE61.EXE"
  "SQL$SAMPLE" = "SYS$COMMON:[SYSHLP.EXAMPLES.DECRDB61]"
  "SQL$SHR" = "SYS$COMMON:[SYSLIB]SQL$SHR61.EXE"
  "SQL$USER" = "SYS$COMMON:[SYSLIB]SQL$USER61.OLB"
  "SQL$VERSION_VARIANT" = "61"

(DECW$LOGICAL_NAMES)
 
Symbols
  RDB42P == "@SYS$LIBRARY:RDBVMS_SETVER 4.2 /PROCESS"
  RDB42S == "@SYS$LIBRARY:RDBVMS_SETVER 4.2 /SYSTEM"
  RDB61P == "@SYS$LIBRARY:RDBVMS_SETVER 6.1 /PROCESS"
  RDB61S == "@SYS$LIBRARY:RDBVMS_SETVER 6.1 /SYSTEM"
  RDBRS == "@SYS$LIBRARY:RDBVMS_SETVER RESET"
  RDBSV == "@SYS$LIBRARY:RDBVMS_SHOVER"
  RDO == "RUN SYS$SYSTEM:RDO"
  SQL == "$SYS$SYSTEM:SQL$"
  SQL42 == "$SYS$SYSTEM:SQL$"
  SQL61 == "$SYS$SYSTEM:SQL$61"
 
VAX/VMS V5.5-2  on node TLV01   4-DEC-1996 11:21:40.05   Uptime  40 16:52:24
0000182D RDMS_MONITOR61  LEF15     4630   0 00:00:04.76    116867    400  
000002AA RDMS_MONITOR    LEF15   217583   0 00:03:52.26   1390631    194  

Filename             Image Name      Image Id          
SYS$COMMON:[SYSLIB]RDB$COSIP.EXE;1           "RDB$COSIP"     "RDBDISPV6.1-0"   
 DISK$OPENVMS:<SYS0.SYSCOMMON.SYSLIB>.EXE RDB$COSIP;1 Open Hdr Shar Prot Lnkbl
   ...........
SYS$COMMON:[SYSLIB]RDBSHR.EXE;5              "RDBSHR"        "RDBDSPV6.1-0"    
  DISK$OPENVMS:<SYS0.SYSCOMMON.SYSLIB>.EXE RDBSHR;5 Open Hdr Lnkbl 
SYS$COMMON:[SYSLIB]RDBSHR.EXE;4              "RDBSHR"        "RDBDSPV4.2-1"    
DISK$OPENVMS:<SYS0.SYSCOMMON.SYSLIB>.EXE RDBSHR;5 Open Hdr Lnkbl

    
    Hmmmmmm, at the moment this is a mystery to me.  Out of curiosity, have
    your customer look at the LOGIN.COM procedure for the VMS account used
    to start the transfer monitor.  By any chance does it set the Rdb
    version to 4.2?  If it does, I don't think that matters because of the
    way the DDAL$TR_MON image is run.  But if that account does set the Rdb
    version to 4.2 (presumably at the PROCESS level), try changing that to
    6.1 to see if it makes a difference.

The customer doesn't set his Rdb environment upon login.   This is true both for
the account used to startup the DDAL$TR_MON or the SYSTEM account.   

I know that if you don't set your Rdb environment specifically upon login, the
default version that you will get is the environment defined on the system level
(Rdb V6.1).   This is the part that confuses me a lot - how DDAL thinks that the
Rdb environment is 4.2 if the system environment is specifically set to 6.1?  

Is there a mechanisn in DDAL that records which Rdb version it should be looking
at the system?

Anyhow, I asked the customer to set the Rdb environment at the process level to
6.1.   He will try it and I will update this note later on what happen.

thanks
albert.

    
    Albert,
    
    The only thing that is hard-wired (recorded) in the DDAL software is
    the minimum version of Rdb that is required.  We check that the system
    has a minimum version and that the system environment has been set up
    for that minimum versionm or higher within the DDAL$START_TR_MON.COM
    procedure in SYS$STARTUP.
    
    Claude

>I know that if you don't set your Rdb environment specifically upon login, the
>default version that you will get is the environment defined on the system level
>(Rdb V6.1).  

Except that you don't get your RMU symbol set properly until you do a 
SETVER RESET (I usually suggest that goes into SYLOGIN). So, if DDAL is using 
the RMU command for anything, without the symbol, it is going to pick up the
standard version - 4.2

Brenda

    
    We use RMU in the DDAL$STOP_TR_MON.COM procedure in ROR 6.0.  That is
    changing in ROR 7.0.  I don't think we use RMU in anything else.  I'll
    check to see.