topic PCSI Database corrupt? in Operating System - OpenVMS

PCSI Database corrupt?

Dieter Rossbach — Mon, 29 Sep 2003 02:17:23 GMT

I have a problem with the PCSI product database. Before reinstalling the whole system, one of you might have some hints about fixing it easier:

sys_dr_HVTEST>product sh hist

JFP AXPVMS MYSQL V4.0-14 Full LP Install 25-AUG-2003 09:28:27
JFP AXPVMS ZLIB V1.1-4 Full LP Install 25-AUG-2003 09:27:39
DEC AXPVMS JAVA141 V1.4-11 Full LP Install 21-JUL-2003 10:08:38
CPQ AXPVMS SSL V1.0-B Full LP Install 21-JUL-2003 10:00:49
DEC AXPVMS DNVOSIECO02 V7.3-1 Patch Install 21-JUL-2003 09:59:34
DEC AXPVMS TCPIP_SSH T5.3-6A Full LP Install 21-JUL-2003 09:57:35
DEC AXPVMS VMS731_RMS V4.0 Patch Install 21-JUL-2003 09:51:54
DEC AXPVMS VMS731_UPDATE V1.0 Patch Install 21-JUL-2003 09:39:54
DEC AXPVMS TCPIP_ECO V5.3-182 Patch Install 21-JUL-2003 09:30:13
DEC AXPVMS VMS731_PCSI V1.0 Patch Install 21-JUL-2003 09:26:47
CPQ AXPVMS CDSA V1.0-2 Full LP Install 17-JUL-2003 13:38:05
DEC AXPVMS DECNET_OSI V7.3-1 Full LP Install 17-JUL-2003 13:38:05
DEC AXPVMS DWMOTIF V1.2-6 Full LP Install 17-JUL-2003 13:38:05
DEC AXPVMS OPENVMS V7.3-1 Platform Install 17-JUL-2003 13:38:05
DEC AXPVMS TCPIP V5.3-18 Full LP Install 17-JUL-2003 13:38:05
DEC AXPVMS VMS V7.3-1 Oper System Install 17-JUL-2003 13:38:05

HVTEST>product install csws
%PCSI-E-OPENIN, error opening SYS$COMMON:[SYSEXE]PCSI$PROCESSOR.PCSI$DATABASE;1
as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
HVTEST>

HVTEST>dir /full SYS$COMMON:[SYSEXE]PCSI$PROCESSOR.PCSI$DATABASE;1

Directory SYS$COMMON:[SYSEXE]

PCSI$PROCESSOR.PCSI$DATABASE;1 File ID: (13781,2,0)
Size: 2/3 Owner: [SYSTEM]
Created: 25-AUG-2003 09:28:27.55
Revised: 25-SEP-2003 07:26:57.96 (4)
Expires:
Backup:
Effective:
Recording:
Accessed:
Attributes:
Modified:
Linkcount: 1
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 3, Extend: 0, Global buffer count: 0
No version limit
Record format: Fixed length 512 byte records
Record attributes: None
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:RWED
Access Cntrl List: None
Client attributes: None

Total of 1 file, 2/3 blocks.
----

Even after opening the security for that file, the problem still exists. And it is the same with SYSTEM or any other privileged account?

Any idea?

Dieter

Re: PCSI Database corrupt?

Willem Grooters — Mon, 29 Sep 2003 03:41:11 GMT

Dieter,

What's the output of:

$ SHO LOG SYS$COMMON /FULL

(You may have this as a searchlist, for any reason, which _may_ cause your problem....)

Re: PCSI Database corrupt?

Dieter Rossbach — Mon, 29 Sep 2003 03:50:41 GMT

I checked that before, here is the result:

HVTEST>sh log sys$common/full
"SYS$COMMON" [exec] = "HVTEST$DRA6:[SYS0.SYSCOMMON.]" [concealed,terminal] (LNM$SYSTEM_TABLE)

Re: PCSI Database corrupt?

Martin P.J. Zinser — Mon, 29 Sep 2003 10:35:08 GMT

Hello,

try set watch file/class=all
Then the PCSI install
then set watch file/class=none

You should receive detailed information on the terminal what exactly PCSI is trying to do.

Greetings, Martin

Re: PCSI Database corrupt?

Åge Rønning — Mon, 29 Sep 2003 10:59:21 GMT

This problem may occur because the VMS$COMMON.DIR synonymed (aliases)
directory file does not exist. Do a DIR/FILE of syscommon.dir and vms$common.dir and see if they have the same file id. If NOT the solution should be(Use with caution!!):

I would also ask myself how this could happen and what else might be wrong on this disk....

SOLUTION:
Create the VMS$COMMON.DIR synonymed directory file using the following commands:

$ SET FILE/ENTER=SYS$SYSDEVICE:[000000]VMS$COMMON.DIR -
_$ SYS$SYSDEVICE:[000000.SYS0]SYSCOMMON.DIR

Once the synonymed entry is established, both the PRODUCT commands above
work successfully.

Re: PCSI Database corrupt?

Dieter Rossbach — Tue, 30 Sep 2003 01:15:08 GMT

Where did the vms$common.dir go?

Thank you, that was it! After creating the vms$common-link, everything works fine.

Why did this happen?

I run a ODS-5 disk with hard links. Deleting vms$common does not make a system unusuable/unbootable.

There is one more question now: How deleted vms$common on my testsystem? :-)

Thank you

Dieter