swverify producing 'Verify failed' messages

[Berd]

I am looking after a 11.11 RP4440 machine. I will shortly be patching the machine to the Dec 2006 patch bundles.

Before commencing with the patching I have run a swverify -v \*.\* to confirm that all installed products are configured correctly.

This returns the below output

WARNING: "wlux01:/": 1 check scripts had warnings.
ERROR: "wlux01:/": The software dependencies for 3 products or
filesets cannot be resolved.
ERROR: "wlux01:/": 115 files had errors during this operation.
WARNING: "wlux01:/": 16 files had warnings during this operation.
* The analysis phase failed for "wlux01:/".
* Verification had errors.


NOTE: More information may be found in the agent logfile using the
command "swjob -a log wlux01-0132 @ wlux01:/".

When I run the swjob command I get the below;

ERROR: 44 of 1901 filesets had Errors.
WARNING: 1 of 1901 filesets had Warnings.
* 1856 of 1901 filesets had no Errors or Warnings.
ERROR: The Analysis Phase had errors and warnings. See the above
output for details.

If I swverify individual filesets I get output which tells me that some files are fo the incorrect mtime or size. However, if i run swlist -l fileset -a state, this tells me that the fileset is configured ???

Is this an issue ?

Regards,
Berd

[Steven E. Protter]

Shalom,

I've never run a swverify that didn't have some problems.

If all the patches are configured, you are in good shape and can probably proceed with the patch no issues.

Do an Ignite make_tape_recovery or make_net_recovery as a matter of course prior to a major patch upgrade.

Your error rate is rather low.

You might wish to do swverify \* and see if you can identify individual patches or products that require attention.

SEP

[Sundar_7]

Berd,

swverify compares the mtime and the size of the file with the IPD (Installed Products Database) it maintains.

If the files have been manually modified after the swinstall, then you will run in to this problem.

Find the list of files that is marked as failed, most probably nothing to worry about.

There is a better tool for verifying the patch status.

# /usr/contrib/bin/check_patches

This analyzes the patches in the system and creates a report in /tmp/check_patches.report.

Sundar

[Dennis Handly]

You can use swverify -F to fix things but it would be a good idea to find out why it reports the error. Perhaps keep the swverify output.

[Berd]

If I run a swlist -l fileset -a state, all of my filesets are configured. I think I will push on with my patching. I will run a install analysis and see if that comes back clean.

I'll post the results when I've done this.

Regards,
Berd

[Berd]

Thanks for input, swinstall ran cleanly.