Hello,
I have included my original posting at the bottom of this message.
This is a followup posting as there is not currently a fix for this
problem.
Digital Unix Engineering has been able to duplicate this and is working
on a fix/workaround.
This problem is apparently caused by running the dupatch baseline analysis
and setting a new baseline.
Steve
##############################################################################
# Stephen LaBelle # Internet : labelles_at_mscd.edu #
# Systems Programmer & Postmaster # #
# Metropolitan State College of Denver # #
# Denver, Colorado USA # #
##############################################################################
%%%%%%%%%%%%%%%%%%%%%% My Original Posting Follows %%%%%%%%%%%%%%%%%%%%%%
Hello All,
I am having a problem with DU4.0B patch kit 5, particularly Patch 189
ddr_config Corrections.
Here is the error while running dupatch:
-------------------------------------------------------------------------
Problem installing:
"V4.0B Patch 0189.00 - Patch: ddr_config Corrections" -
./etc/.mrg..sysconfigtab does not exist on your system,
however, it is in the inventory of installed subsets.
This patch can not be installed.
-------------------------------------------------------------------------
I believe I have seen others posting this problem to either osf-managers
or the OSF usenet groups. I have never seen a solution posted however.
A little background:
I have 4 Digital Unix 4.0B machines, all with patch kit 4
installed successfully.
This dupatch error occurs on only 1 out of the 3 machines. Thats
what bothers me most about this!
The actual path its complaining about does not exist on any of my 4
systems. I suspect its failing during some type of a merge and the
file its is talking about is actually:
/etc/#.mrg..sysconfigtab
I suspect the merge operation actually uses that file, which exists
on all 4 machines.
I also strongly suspect that the problem is somehow related to
customizations done to /etc/sysconfigtab which then requires this merge
operation to occur.
On all 4 systems, I have sysconfigtab customizations. Again, what
is different about that one system.
The failing system is an ALPHAserver 8400 5/440.
The systems with no problems ALPHAserver 2100 4/275,
ALPHAserver 2100 5/300, ALPHAstation 600 5/333
I doubt the hardware is any issue with this problem.
I also tryed making a brand new sysconfigtab file using
/etc/.new..sysconfigtab but got the same error???
I do change sysconfigtab with the text editor normally, and I
also know to use the command /usr/sbin/sysconfigdb -s
after altering sysconfigtab
Any help appreciated, and I will summarize the solution.
Received on Mon Oct 20 1997 - 18:34:22 NZDT