IBM Support

IC86630: DSMUPGDX UPRADE WIZARD TERMINATE WITH RETURN CODE 499

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • When upgrading from 5.5 to 6.x on new server release using media
    
    method,  the dsmupgdx wizard fails with return code 499.
    
    ANR0900I Processing options file C:\Program
    Files\Tivoli\TSM\Server1\dsmserv.-opt.
    ANR0902W Unsupported keyword found in file C:\Program
    Files\Tivoli\TSM\Server-1\dsmserv.opt.
    
    ANR4726I The ICC support module has been loaded.
    ANR0990I Server restart-recovery in progress.
    ANR0152I Database manager successfully started.
    ANR1380I The buffer pool monitor switch is enabled.
    ANR1628I The database manager is using port xx for server
    connections.
    ANR1636W The server machine GUID changed: old value (), new
    value ()
    ANR7808W Sun Microsystems Library Attach module libacs.dll is
    not available from the system.
    ANR8200I TCP/IP Version 4 driver ready for connection with
    clients on port xx.
    ANR8840E Unable to open device x.x.x.x with error number 2 and
    PVRRC 2839.
    ANR8418E DEFINE PATH: An I/O error occurred while accessing
    library xxx.
    ANR0902W Unsupported keyword found in file ExtracT.mft.
    ANR0906I Line No. : 0
    ANR0907I Statement : DEFINE PATH xxx xxx SRCTYPE=SERVER
    DESTTYPE=LIBRARY DEVICE=x.x.x.x ONLINE=YES
    ANR0369I Stopping the database manager because of a server
    shutdown.
    
    Insertion process completed with return code 499
    
    dsmupgdx.trc shows following error.
    
    com.tivoli.dsm.ServerConfig.ServerDB$GenericThread.run():
    Issuing cmd: "C:\Program Files\Tivoli\TSM\Server\dsmserv" -k
    Server1 INSERTDB MANIFEST=\"ExtracT.mft\" >InsertDB.Out 2>&1
    com.tivoli.dsm.ServerConfig.ProcessMonitor.Constructor(): enter
    com.tivoli.dsm.ServerConfig.ProcessMonitor.Constructor(): exit
    com.tivoli.dsm.ServerConfig.ProcessMonitor.run(): enter,
    Monitoring file C:\Program Files\Tivoli\TSM\Server1\InsertDB.Out
    com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File
    C:\Program Files\Tivoli\TSM\Server1\InsertDB.Out not created
    yet.
    com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File
    C:\Program Files\Tivoli\TSM\Server1\InsertDB.Out now being read.
    com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File
    C:\Program Files\Tivoli\TSM\Server1\InsertDB.Out now being read.
    com.tivoli.dsm.ServerConfig.ServerDB$GenericThread.run(): cmd
    rc: 3
    com.tivoli.dsm.ServerConfig.ProcessMonitor.cancel(): enter
    com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File
    C:\Program Files\Tivoli\TSM\Server1\InsertDB.Out now being read.
    com.tivoli.dsm.ServerConfig.ProcessMonitor.run(): exit
    com.tivoli.dsm.ServerConfig.ProcessMonitor.cancel(): exit
    com.tivoli.dsm.UpgradeWizard.DoInsertPanel$BoxHandler.signalEven
    t(): enter, event=insertDbDone, rc=499
    com.tivoli.dsm.UpgradeWizard.DoInsertPanel.signalDone(): entry,
    insert rc: 499
    com.tivoli.dsm.UpgradeWizard.DoInsertPanel.signalDone():
    extractDone: T, rc: 0
    com.tivoli.dsm.UpgradeWizard.DoInsertPanel.signalDone():
    insertDone: T, rc: 499
    com.tivoli.dsm.UpgradeWizard.DoInsertPanel.signalDone(): exit
    
    The wizard failed because the manifest file includes the
    incorrect device name for define path command which is not
    available on the new server.
    It is required to edit the manifest file to include correct
    device name prior to perform the insertdb step.
    Tivoli storage manager server upgrade guide should include the
    guide.
    
    
    Versions affected:
    Tivoli Storage Manager 6.x server
    
    Additional Keywords
    zztsm61  zztsm62 zztsm63 upgrade wizard dsmupgdx.exe
    
    Additional L2 info:
    
    Initial Impact: Medium
    

Local fix

  • Edit the manifest file to include the correct device name prior
    to perform insertdb step.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users who are upgrading the Tivoli       *
    *                 Storage Manager server from V5 to V6         *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    *
    

Problem conclusion

  • In the "Tivoli Storage Manager Upgrade and Migration Guide for
    V5 Servers," the instructions for loading extracted data into
    a V6 database were updated. More detailed information is
    provided for verifying the manifest file.
    
    In the instructions for a standard upgrade, the step for
    verifying the manifest file was modified as follows:
    
    "Verify the contents of the manifest file and edit the file if
    necessary:
    
    a.   Ensure that the device names are valid for the V6.3 or
    later system. Device names for the same device might be
    different on V5 and V6.3 or later systems.
    
    b.   Ensure that the manifest file contains a list of volumes
    to be used when the extracted data is loaded into the new
    database. For example, if the manifest file contains a list of
    volumes that belong to a FILE device class, ensure that the
    fully qualified path to the volumes is correct for the system."
    
    In the instructions for a migration from V5 on z/OS to V6.3 or
    later on AIX or Linux, the step was modified as follows:
    
    "Verify the contents of the manifest file and edit the file if
    necessary:
    
    a.   Ensure that the device names are valid for the V6.3 or
    later system. In particular, ensure that the definitions for
    accessing the media server are correct. If you are not using a
    media server, ensure that device names for accessing devices
    on the V6.3 system are correct.
    
    b.   Ensure that the manifest file contains a list of volumes
    to be used when the extracted data is loaded into the new
    database."
    
    
    Affected platforms:  AIX, HP-UX, Solaris, Linux, Windows, and
    z/OS
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC86630

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63W

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-19

  • Closed date

    2012-11-09

  • Last modified date

    2012-11-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Publications Referenced
GC27401700    

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"63W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
09 November 2012