HomeSearchSite MapContact Us

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

DATABASE
ADMINISTRATION

 
 

RMU/DUMP And DBO/DUMP Extended?
TECHNICAL ARTICLES -> TROUBLESHOOTING ARTICLES
Back ] Next ] Printer Friendly Version ]

Q:

I’m confused. The output from RMU/DUMP and DBO/DUMP of one of our Rdb and DBMS databases says that all of the areas have extended one time and I know that they have not extended (the database was just created). On another database, it says, “Area has never been extended,” but I know it has extended many times. Is this a bug in Rdb and DBMS?

 

A:

It is not a bug, but it is not clear either! The RMU/DUMP and DBO/DUMP report the number of times that a file has extended since it was last created or restored. Thus, if a database with extended storage areas is restored, the “restored count” will be reset when the database is restored. However, if the database file is on a bound volume set, Rdb and DBMS create an extension for each member of the bound volume set. Therefore, if a database is created on a multi-volume bound volume set, RMU/DUMP and DBO/DUMP will display “area has extended n times” even when the database is created. Yes, it’s confusing.

 

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