Using dbverify

[dictum9]

A chown was run on the /partition in 11.23 and some system files got messed up.

How do I use DBVerify to ensure the system is good?

Is DBVerify the same thing as dbv?

I cannot find either in my path.

[Pete Randall · Accepted solution]

Do you mean swverify? I've never heard of dbverify.


Pete

[James R. Ferguson]

Hi :

The infamous 'chown' at the root directory?

If so, you should do:

# swverify -F \*

...to fix the ownership of file cataloged in the IPD. This will take some time to run; be patient; and examine the output logs too.

Regards!

...JRF...

[dictum9]

Of course - I meant swverify

When I run it, I get:


ERROR: "sgtest1:/": One or more filesystems that appear in the
filesystem table are not mounted and cannot be mounted.
* The analysis phase failed for "sgtest1:/".
* Verification had errors.

[James R. Ferguson]

Hi (again):

Either mount the missing filesystems or edit their declarations from '/etc/fstab' and rerun the 'swverify'.

Alternately, do:

# swverify -x mount_all_filesystems=false -F \*

Regards!

...JRF...

[dictum9]

That appears to get much farther, but in th end I got this. Did it fix anything?


* Beginning Analysis
* Session selections have been saved in the file
"/.sw/sessions/swverify.last".
* "sgtest1:/": There will be no attempt to mount filesystems
that appear in the filesystem table.
ERROR: "sgtest1:/": 231 files had errors during this operation.
WARNING: "sgtest1:/": 6 files had warnings during this operation.
* The analysis phase failed for "sgtest1:/".
* Verification had errors.

[Mel Burslan]

check the session log in /var.adm/sw/swagentd.log (you can match by the timestamps) and see what those 6 errors were. There is not much information in the output you posted otherwise.

[dictum9]

It ran fine but apparently did not fix anything - looks like you have to use -x switch:

-x fix=true

[dictum9]

swverify -F fix=true \*

results in this. Doesn't seem to work:



* Beginning Analysis
* Session selections have been saved in the file
"/.sw/sessions/swverify.last".
ERROR: A job cannot be created. There is no software specified in
the sessionfile: "/var/adm/sw/queue/logfiles/0128.1/session".
A job must have software specifications.
ERROR: The attempt to create the job failed. (Internal error)

ERROR: Could not change the job queue to "Complete" for job . The
job is not locked.

[Mel Burslan]

seems like your command is missing an "-x" switch before the fix=true

swverify -F -x fix=true \*

I amnot sure if this is the cause but doesn't hurt to try.

[dictum9]

Tried exactly that and it doesn't fix anything.

[Dennis Handly]

>Mel: swverify -F -x fix=true \*

Typically this will work without the fix=true since there are few HP "fix" supplied scripts.
swlist -l control_file | grep fix
finds nothing on my system.

>Tried exactly that and it doesn't fix anything.

What do the swverify logs say? (/var/adm/sw/swagent.log)