HP3000-L Archives

February 1996, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Thu, 29 Feb 1996 15:52:37 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
Brett,
 
I've seen similar symptoms after a system restart because a disk failed
to mount and the mount error wasn't caught by the operator.  Of course,
this affected more than one file, and you mentioned that no disk
problems were found.  If you have VESoft's 'VEAUDIT' utility, you can
quickly scan your system logfiles for FCLOSE/purge records on that
dataset; otherwise, you could use HP's SYSDIAG:logtool to do so (this
all assumes that you log these events - Logging Event 105 set in
SYSGEN's Logging Configurator).  Such a log record might tell you who
or what purged the file.  Maybe HP has already done this for you?
 
Lee Gunter      503-375-4498        [log in to unmask]
HMO Oregon      503-375-4401  fax
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.
 
______________________________ Reply Separator _________________________________
Subject: missing data set
Author:  Brett Rickard <[log in to unmask]> at ~INTERNET
Date:    2/29/96 3:41 PM
 
 
Hp3000 957 Mpe/ix 5.0 powerpatch 3
 
Here is an interesting/scary one that happened to me.
 
What happened was a detail data set in an Image database
"disappeared" between the 1:00am backup  and when the users
logged on at 9:00am.
 
There are "were" 41 data sets in the database. The 22nd set and
only the 22nd set was missing. (i.e. the data base name is SPRING
and SPRING22 was a nonexistent permanent file).
 
Sequence of events.
 
1. 1:00am unattended full backup.
 
2. Several nightly jobs, one which updated another data set in
the SPRING database and one which just did a report with no
updating. Neither of those accessed the missing data set. None of
the other jobs accessed the Spring database.
 
3. copied and purged some other databases in the same acct using
DBUTIL and ADAGER
 
4. 9:00 am shutdown and restart the system.(change in printer
configs).
 
5. 10 minutes after startup users call about programs aborting.
 
The database was backed up and so we were able to recover. I
called the response center and hprc checked my log files for disk
problems etc. and found no unusual events or errors logged. The
response center has no similar events recorded.
 
I still have no idea what happened to that file.
 
Brett Rickard             -   Internet email: [log in to unmask]
Systems Analyst           -   Voice: (805) 546-3248 Fax: (805) 546-3102
Cuesta College            -   P.O. Box 8106, San Luis Obispo, CA 93403-8106

ATOM RSS1 RSS2