RDBPROD: Problems Using RMU command definitions in Rdb multiversion environment (Doc ID 732926.1)

Last updated on AUGUST 03, 2016

Applies to:

Oracle Rdb Server on OpenVMS - Version 7.0 to 7.3 [Release 7.0 to 7.3]
HP OpenVMS Alpha
HP OpenVMS Itanium
HP OpenVMS VAX

Symptoms

When only Oracle Rdb standard version is installed (7.0.x or earlier), it is possible to define symbols that contain RMU commands to show stall messages, locks, the version, etc.

For example, to show the Rdb version:

$ RMUV :== RMU/SHO VERSION
$ RMUV
Executing RMU for Oracle Rdb V7.0-9
$

Using Rdb multiversion 7.0.x (or earlier), or using Rdb 7.1.x, 7.2.x or 7.3.x (which are always multiversion) a user defined symbol using RMU may result in errors.

For example:

$ LOCKS :== RMU /SHOW LOCKS /MODE=BLOCK
$ LOCKS 
%DCL-W-ACTIMAGE, error activating image RDMPRV 
-CLI-E-IMGNAME, image file DSA1:[SYS0.SYSCOMMON.][SYSLIB]RDMPRV.EXE;2 
-SYSTEM-W-SYSVERDIF, system version mismatch; please relink 

$ RMUV :== RMU/SHOW VERSION
$ RMUV
%DCL-W-ACTIMAGE, error activating image RDMPRV 
-CLI-E-IMGNAME, image file DSA1:[SYS0.SYSCOMMON.][SYSLIB]RDMPRV.EXE;2 
-SYSTEM-W-SYSVERDIF, system version mismatch; please relink
 
$

Using an RMU command at the OpenVMS prompt still works:

$ RMU/SHOW VERSION  
Executing RMU for Oracle Rdb V7.2-531  
$

Changes

This problem occurs whenever more than one Rdb version is installed on the system, e.g. 7.2.x and 7.3.x.

Cause

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