Soft Product INDEX file corrupted

[Tallieu]

By installing a new patch on a L1000 server, the /var went full and the /var/adm/sw/products/INDEX file is corrupted. swlist doesn't work anymore. No backup are available :( How can I recreate the INDEX for my system?
Merci!

[Animesh Chakraborty]

Hi,
Have you tried
#/sbin/init.d/swagentd stop
$/sbin/init.d/swagentd start ?

[Alex Glennie]

How do I fix a corrupted IPD (Installed Products Database)?

First, determine where the corruption is. Before the IPD can be rebuilt, the source of the corruption must be eliminated from the lowest level. If swlist is reporting parsing errors, it will point to a line number within the master INDEX (/var/adm/sw/products/INDEX). Look at this file at the given line number to locate the product/fileset where the parsing error occurs. As with any parse, the error may actually have occurred in the previous product/fileset. Once you have this information, the next step is to look at this information at the subINDEX level. Since the master INDEX is basically a concatenation of INDEX files from all products within the IPD, you should try to isolate the problem at the subINDEX level. If this can be done, the choices are usually to try reinstalling this product/fileset, or (on 10.20 only), to mv that product directory structure out of the IPD to /var/tmp, and then try rebuilding the IPD. The simplest way to do this is to take a product/fileset which is already correctly configured on the system, and to use swmodify to mark its state as configured. For example,

# swmodify -a state=configured OS-Core.Q4

This will accomplish nothing other than to force SD-UX to rebuild the IPD. If you have correctly eliminated the troublesome product, swlist will not report any errors on the newly built IPD.

One source of IPD corruption is a lack of disk space in /var. Many times, checking swagent.log will point to errors where disk space was too low in /var, but the software installation was attempted anyway. Because all necessary files cannot be copied into the IPD once space runs out (during the installation process), the missing information may cause IPD corruption. Usually, this can be corrected by adding more space to /var and reinstalling the product/fileset(s) in question, but this may not be possible if the corruption is too extensive.

[Animesh Chakraborty]

I upgraded from 9.04 to 10.01 and now I am having some
serious problems with swlist. There are a ton of errors
and warnings in the swlist -1 file when I run swlist.
Some of them are:

...
WARNING: Ignoring unknown keyword "state" at line 24.
WARNING: Invalid value defined for the keyword "timestamp", at line
670. Valid values for this keyword are: Unsigned integers
(in decimal, octal, or hexidecimal notation).
WARNING: Ignoring duplicate definition for the keyword "tag" at line
671.
WARNING: Ignoring duplicate definition for the keyword
"data_model_revision" at line 672.
WARNING: Ignoring duplicate definition for the keyword "instance_id" at
line 673.
WARNING: Ignoring duplicate definition for the keyword
"control_directory" at line 674.
WARNING: Ignoring duplicate definition for the keyword "revision" at
line 675.
WARNING: Ignoring duplicate definition for the keyword "title" at line
676.

ERROR: Incomplete definition for the bundle "J2166A_APS", beginning
at line 1344. The following attributes are not defined:
contents the software contained in the bundle.
The attribute(s) must be defined before the parsing can
continue.
ERROR: Invalid definition for the bundle "J2166A_APS", beginning at
line 1344. Details described above. The bundle has been
marked as corrupt.

What is the problem?


CONFIGURATION
Operating System -HP-UX
Version -10.01
Hardware System -T500


RESOLUTION
In the /var/adm/sw/products/J2166A_APS/pfiles directory,
the INDEX file is corrupted. It's chopped off at: bundle.

You will need to re-load the J2166A_APS software in order
to fix your problem.

The HP Token Ring/9000 Series 800 product (J2166A) provides
hardware and software connectivity from an HP 9000 Series.





http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x520a6d96588ad4118fef0090279cd0f9,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x81faa14d9abcd4118fef0090279cd0f9,00.html

[Clemens van Everdingen · Accepted solution]

Hi,

Follow the next procedure to correct this:

First, make a backup copy of the INDEX file (if it exists). If problems are encountered, this file can be moved back into place, and the product definitions will be restored to their former state.

To rebuild the INDEX file, use the following procedure which will install a "fake" product on the system. During the installation of this product, the INDEX file will be regenerated.


# cd /var/adm/sw/products
# mv INDEX INDEX.orig
# cd /tmp
# vi void.psf
product
tag void
fileset
tag void
:wq!
# swpackage -s /tmp/void.psf
# swinstall void
# swremove void
# rm void.psf
# swremove -d void

C.