HomeSearchSite MapContact Us

   RemoteDBA Services for CODASYL DBMS and Rdb Remote Management of OpenVMS Systems Preserving Mission Critical IT Applications Through Virtualization

DATABASE
ADMINISTRATION

 
 

Problems Upgrading From V6.l to V7.0.3 (DBMS only)
TECHNICAL ARTICLES -> UPGRADE ARTICLES
Back ] Next ] Printer Friendly Version ]

Q:

We upgraded from DBMS V6.1 to DBMS V7.0.3 (both multiversion). After the upgrade, our
application failed with the message “DBM-F-ROOTMAJVER, database format 70.1 is not compatible with software version 61.0. If we use “DBO/SHOW version,” it shows “Executing DBO for Oracle CODASYL DBMS V7.0.3,” so I am certain we ARE running DBMS V7.0. What’s up?

 

A:

This condition occurs because your programs were linked with the sharable image, DBMSHR61, rather than DBMSHR. This occurred because the link options file DBMDML61.OPT that was supplied with DBMS 6.1 included this reference. The work-around to this problem is to define DBMSHR61 as DBMSHR70; “$ define dbmshr61 dbmshr70.”

Top


Was this article helpful? 
This information and more was originally published in SCI's technical newsletter, DBAdvisor.
Past issues are available online; you may also fill out a subscription form.

If you have a technical question about this article or about any other 
CODASYL DBMS or Rdb topic, then ask our experts.

How would you rate this article?

5 (Highest)
4
3
2

0 (Did not apply)
Comments about this article or topic suggestions for new articles

Copyright © 2008 Software Concepts International
All Rights Reserved

 

 

Copyright © 2008 Software Concepts International
All Rights Reserved