Missing Database file

[odwillia]

Is there a log in VMS that will tell me if a file was deleted or moved?

I'm using OpenVMS V7.2-2

We are getting this error for a DB file:

%RMU-W-BADDBNAME, can't find database root RMADSK05:[APPL.VARSHNEY]PROD_DB.RDB;
-RMS-E-FNF, file not found
%RMU-F-CANTOPNROO, cannot open root file "PROD_DB"
%RMU-F-FTL_ANA, Fatal error for ANALYZE operation at 5-JAN-2009 06:46:05.48
$ rmu/show stat prod_db
%RMU-W-BADDBNAME, can't find database root RMADSK05:[APPL.VARSHNEY]PROD_DB.RDB;
-RMS-E-FNF, file not found
%RMU-F-CANTOPNROO, cannot open root file "PROD_DB"
%RMU-F-FTL_SHOW, Fatal error for SHOW operation at 5-JAN-2009 07:58:08.25
Thanks for your help

[Robert Gezelter]

Odwilla,

Generally, there is no record of when a file is moved or deleted. If various types of auditing are enabled, more detailed records can be maintained.

Obviously, if this is a production file, I would use caution in presuming that what appears to be a copy of the file in another location is in fact a copy of the true production file.

The best immediate course of action is probably to speak with your colleagues and check the backups.

- Bob Gezelter, http://www.rlgsc.com

[Hoff]

The answer to your question here is site-specific. You will have to answer that question yourself. There CAN be a log, but there may NOT be a log.

The original "I have been given the task of administrating Openvms for the next 6 months" is rapidly approaching two years, eh?

This configuration is ripe for a security and operational review, as the data stored here is clearly exposed.

Based solely on the variety and the types of reports from your site (and how you've seemingly gotten yourself onto a three hour cruise on the S.S. Minnow :-) ), I'd be looking to reduce the numbers of privileges available to users on this cluster, and toward implementing auditing and change tracking and appropriate archiving, and up-rating the experience with and the available training with OpenVMS and with Rdb available on-site.

[Hein van den Heuvel]

When did it last work?
What changed since then?

Don't panic just yet.

Just start a simple drill down...

Is prod_db a logical or is is just 'where you are'?

That "RMADSK05", is it a logical, or just 'where you are'.

Does RMADSK05 exist?
The name suggests it is a logical name created my mounting a production disk.

What does a simple DIR RMADSK05:[000000]*.DIR give?

Now drill down further...

It could 'just' be
- a disk which failed to mount.
- A fat-fingered logical name defintion.
- a miss-communicationed rename.
:

It could be that someone deleted a critical file. Start looking for backups or a resume!


Good luck!
Hein.