Operating System - OpenVMS
1748117 Members
3779 Online
108758 Solutions
New Discussion юеВ

Re: OpenVMS Analyze/disk/repair : marked for deletion

 
eddouik
Occasional Contributor

OpenVMS Analyze/disk/repair : marked for deletion

Hi all
Aparently we have somme inconsistancies problems on a disk, when we execute analyze/disk we have the following output :
%ANALDISK-W-DELHEADER, file (5903,6,0) beqlsnr0.com;1
marked for delete
%ANALDISK-W-DELHEADER, file (8833,17,0) beqlsnr0.com;1
marked for delete
But evenif we execute analyze/disk/repair we the same output.
There is a way to repair those errors ?
If we still have those error, there's some risks ?


BR.

6 REPLIES 6
Karl Rohwedder
Honored Contributor

Re: OpenVMS Analyze/disk/repair : marked for deletion

Those files are marked for delete, but are currently open by some process. When those processes finish, the files should disappear.

Try a SHO DEVICE xxx /FILES and search the output for the filename to get the processes.

regards Kalle
Jess Goodman
Esteemed Contributor

Re: OpenVMS Analyze/disk/repair : marked for deletion

Or alternately you can recover the file using the DFU utiility, avaiable on the VMS V7 Freeware CD
http://www.openvms.compaq.com/openvms/freeware/

Use the command:
DFU UNDELETE disk:/MARKED/FILE=beqlsnr0.com;1
I have one, but it's personal.
Ian Miller.
Honored Contributor

Re: OpenVMS Analyze/disk/repair : marked for deletion

for DFU get it from

http://www.digiater.nl/dfu.html

I expect something has those files open.
____________________
Purely Personal Opinion
Hoff
Honored Contributor

Re: OpenVMS Analyze/disk/repair : marked for deletion

In isolation, DELHEADER can be normal and expected. Ignore it -- unless there's a secondary symptom showing up elsewhere.

DELHEADER alone is entirely harmless, and does not imply a corruption.

Here, I'd *guess* that some command procedure has deleted itself, or there's a temporary file in use somewhere.
Hein van den Heuvel
Honored Contributor

Re: OpenVMS Analyze/disk/repair : marked for deletion

>> There is a way to repair those errors

Those are no errors, just warnings.
As the others replied, the file is probably still open. No risk with that.

If the name is for real, then this certainly looks like a potentially temporary file generated by ORACLE to fire up the LISTENER.

On my system I get:

$ pipe show dev/file disk$oracle | search sys$pipe beq
ORA_2600075110 20400399 [ORACLE.10g2.network]beqlsnr0_HEINA.com;1
ORA_2600075110 20400399 [ORACLE.10g2.bin]BEQLSNR.EXE;1

For Oracle 10.2, on OpenVMS Alpha 8.3 this file is not pre-deleted, and ANAL/DISK does no rat it out.
But I suppose I could be pre-deleted on earlier version. I never needed to look into it. It is a generated file according to the contents and date stamps:
"$! CREATED by CREATE_BEQLSNR.COM on ..."

fwiw,
Hein.
comarow
Trusted Contributor

Re: OpenVMS Analyze/disk/repair : marked for deletion


The one thing I didn't see mentioned are
files still open but marked for delete.
After rebooting, re-running the utility
will get rid of these files.

There are often a lot created when on upgrades
a system or product.

Bob C