Install correct version of Veritas product but pkginfo show different version

Problem

Install correct version of Veritas product but pkginfo show different version

Solution

After upgrade Veritas product, if you run
# modinfo | grep vx
27  1241dbc  28f54 246   1  vxdmp (VxVM 4.0R_p4.7 (MP2): DMP Drive)
28 78018000 1cf418 247   1  vxio (VxVM 4.0R_p4.7 (MP2) I/O driver)
30 781c74d8    847 248   1  vxspec (VxVM 4.0R_p4.7 (MP2) control/st)
127 787c33e9    c23 249   1  vxportal (VxFS 4.0_REV-MP2f portal driver)
128 784ac000 165c95   8   1  vxfs (VxFS 4.0_REV-MP2f,116689-02 (Su)
157 78766000   5972 253   1  vxgms (VxGMS 4.0 (SunOS))
158 787a0000  39799 245   1  vxfen (VRTS Fence 4.0MP2)
165 7832e000  1c638 252   1  vxglm (VxGLM 4.0 (SunOS 5.9))

In this case we have version 4.0 for example VRTSvxfs but when you run
#pkginfo -l VRTSvxfs
  PKGINST:  VRTSvxfs
     NAME:  VERITAS File System
 CATEGORY:  system,utilities
     ARCH:  sparc
  VERSION:  3.2,REV=GA04
  BASEDIR:  /
   VENDOR:  VERITAS Software
     DESC:  Commercial File System
   PSTAMP:  VERITAS-FS-3.2.0-2002-06-17-3.2MP4
 INSTDATE:  May 04 2002 13:41
  HOTLINE:  (800) 342-0652
    EMAIL:  support@veritas.com
   STATUS:  completely installed
    FILES:      233 installed pathnames
                 36 shared pathnames
                  5 linked files
                 48 directories
                 74 executables
                  5 setuid/setgid executables
              51407 blocks used (approx)

Here it show version 3.2 and you know for sure you install a correct version 4.0 or check the package which you installed from to make sure it is a correct version

Here are the steps we need to check:

1/- check in /var/sadm/pkg/<Product name>/pkginfo ----> in this example it will be /var/sadm/pkg/VRTSvxfs/pkginfo   make sure it show a correct version
2/- make sure you are boot up from correct boot device by running
# prtconf -vp | grep boot
   boot-retained-page:  
       bootargs:  00
       bootpath:  '/pci@1c,600000/scsi@2/disk@0,0:a'
       auto-boot-on-error?:  'true'
       auto-boot?:  'true'
       boot-command:  'boot'
       boot-file:  
       boot-device:  'disk0:a'

and check the bootpath and boot-device are correct

3/- system is mounted correctly so pkginfo are getting information from a correct boot disk - not meta disk suite or mirror boot disk

4/- Lastly run the truss command to see whether pkginfo get the information from after checking you have correct version installed
#truss -failed pkginfo -l VRTSvxfs

After long message , you will see

22836/1:        access("/var/sadm/pkg/.save.VRTSvxfs/pkginfo", 0) = 0
22836/1:        open("/var/sadm/pkg/.save.VRTSvxfs/pkginfo", O_RDONLY) = 3
22836/1:        fstat64(3, 0xFFBFED20)                          = 0
22836/1:        fstat64(3, 0xFFBFEBC8)                          = 0
22836/1:        ioctl(3, TCGETA, 0xFFBFECAC)                    Err#25 ENOTTY
22836/1:        read(3, " C L A S S E S = a l l  ".., 8192)     = 1340
22836/1:        read(3, 0x000F0EB4, 8192)                       = 0
22836/1:        llseek(3, 0, SEEK_CUR)                          = 1340
22836/1:        close(3)                                        = 0


It read from /var/sadm/pkg/.save.VRTSvxfs/pkginfo. Check if the directory /var/sadm/pkg/.save.<Product name>. Move the directory away from the current directory, If modinfo show correct version and you can run pkginfo now to check . If the version are matched, then the problem is resolved. Otherwise you will need to remove and reinstall product.

This ran after remove .save.VRTSvxfs without reinstall product
# pkginfo -l VRTSvxfs
  PKGINST:  VRTSvxfs
     NAME:  VERITAS File System
 CATEGORY:  system,utilities
     ARCH:  sparc
  VERSION:  4.0,REV=GA04
  BASEDIR:  /
   VENDOR:  VERITAS Software
     DESC:  Commercial File System
   PSTAMP:  VERITAS-FS-4.0.2.0-2005-06-17-4.0MP2=116689-02
 INSTDATE:  May 04 2006 13:41
  HOTLINE:  (800) 342-0652
    EMAIL:  support@veritas.com
   STATUS:  completely installed
    FILES:      233 installed pathnames
                 36 shared pathnames
                  5 linked files
                 48 directories
                 74 executables
                  5 setuid/setgid executables
              51407 blocks used (approx)



Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)