sectorseveng:Yes I do agree with you that I should've not been directly playing with those odm files. Thanks for the inputs regarding the '5' key/F5 key combination for booting into service mode. The catch here is that hitting the F5 key during bootup of my 43P Model 150 RS/6000 gets me into a...
sectorseveng: the lpp_id for bos.net.tcp.client works out to 77 and using this in
odmget -q 'lpp_id=77' inventory or
odmget -q 'lpp_id=77' history returns valid data. Guess as suggested by you it seems that the .vc files are corrupt. As far as the files are concerned, it was typically files...
Hi sectorseveng,
Yup, I understand it's too late now for the backups :) and unfortunately no backups were taken during initial install of the OS. Hmmm, no other option left but to install the entire OS from scratch huh. Well I guess I'll have to do that now.
Well the exact cause of corruption...
Thanks for the steps, but I don't have any tape devices attached to my system. Is there any other way? Can I take backups to local files and then restore them from there? If so how do I go about doing that?
PS: DSMARWAY
Yes echo $ODMDIR returns /etc/objrepos.
Hi,
lppchk -v returns...
"A system error occurred while attempting to access the Software Vital Product Data. Use local problem reporting procedures."
What I was actually doing is that I was trying to figure out which file on the hard disk SMIT uses to extract information about a...
I get the following error when I try to run the lslpp command with any switches allowed.
"lslpp: 0504-302 ODM error 5803 occurred trying to read SWVPD data." If I try lslpp -L all I get...
"A system error occurred while attempting to access the Software Vital Product Data. Use...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.