swlist -l product error after restore

[Matthew Pegge_1]

I have recently had to upgrade one of our systems hardware from a D320 to D390. Both systems are on HPUX 11.0. Everything works fine except on the new system I pre-installed UX-Mirror disk as part of the upgrade. However after I haev done the full restore from the old system to the new (excluding some files) an swlist does not show mirror disk as an installed product although it does actually work. Also I get lots of the following message when I do swlist -l product:

# Contacting target "dk871_3"...
ERROR: Duplicate definition for the product "Curses-Color", beginning at line 46583. This product defines the same values for the same version attributes as another product or bundle contained in the root (installation). Those attributes are

Curses-Color,l=/,r=B.11.00,a=HP-UX_B.11.00_32/64,v=HP

The duplicate product has been marked as corrupt, and its tag attribute changed to "_product_46583".


I realise I've must have overwritten the sw catalogue somehow and it is in a bit of a twist, but is there anything I can do to solve this?

[Pete Randall]

How did you do the "full restore from the old system to the new"?

I would use Ignite ( http://www.software.hp.com/products/IUX/index.html ) to make a "make_tape_recovery" image that you can then use to reload the new server. Install MirrorDisk/UX afterwards.


Pete

[Massimo Bianchi]

Hi,
1- a fresh and full restore, as suggested by SEP
2-
swverify \*

this will check all of your catalog, and then le't see which is the less hurting solution...

HTH,
Massimo

[Steven E. Protter]

Ignite would have preserved this data if it was used in the transfer. I have transferred systems including SD-UX data many times.

Unless you want to start over, get out your codeword sheet and reintall mirror/ux.

run swverify \*

This will let you check the extent of the damage. If its serious, its time to start over.

SEP

[T G Manikandan]

check this

http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0x6375402f24d5d61190050090279cd0f9,00.html

[Matthew Pegge_1]

OK... the reasons for not using Ignite were valid, I agree that this would have been the best way however, we had to do this to over 50 server, so we decided to use a generic ignite to base build the boxes and then when they ahd been shipped to site we did a selective restore of the data and recovered it to the new box. It looks the only real damage is the Duplicate Entry Error messages. Any ideas how to get rid of them? Can I just remove the entry in the INDEX file?

[Massimo Bianchi]

Don't you manage to swremove the corrupted product ?

Did you try ?
Massimo

[Dennis van den Hooren]

I've had the same problem and did the following to get rid of the error messages swlist produce.
I tested it with following product and it works

# Spelling B.11.11 Spelling


Steps
1. cd /var/adm/sw/products
2. cp INDEX INDEX.org

In the products directory there were to directory's of Spelleng

Spelling
Spelling.2

3. mv Spelling.2 /tmp/Spelling.2
4. vi INDEX

remove the follwing text:

product
tag Spelling
data_model_revision 2.40
instance_id 2
control_directory Spelling.2
revision B.11.11
title "Spelling"
..
..
..
title "Hewlett-Packard Company"
description "Software Products from Hewlett-Packard"
end

5. Check with "swlist -l fileset | grep -i spelling" if the duplicate product is removed


Regards,

Dennis

[Bill Hassell]

The problem was with the full restore. For software installed using swinstall (the Software Distributor utilities), the directory /var/adm/sw is crucial to tracking what has been installed. By overwriting /var (and /var/adm/sw files) during the restore, the indexes that track bundles and products were replaced (along with other files) and now your system has products and versions installed that do not match /var/adm/sw (the original HP-UX plus MirrorDisk). This may be very complicated to fix since there may be records of patches installed in /var/adm/sw but depending on what you restored, they may not be, or be at a different revision level. This will lead to major problems in the future when patching this system. Similar problems will exist if you restored /etc without selectively excluding files like lvmtab, or restored /dev from another system.

Before you go any further, I would strongly consider starting over. If possible, use an Ignite/UX tape from a similar system to get started. Then add optional products like MirrorDisk, then HWE and QPK patches. That way, /var/adm/sw, /etc and /dev will be valid and future product installs and patching will work OK.