IC61029: TSM 6.1 RESTORE DB FAILS WITH ANR4602E OR ANR2025E ERROR WHEN LANGUAGE SERVER OPTION USES LANGUAGE OTHER THAN ENGLISH.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A TSM 6.1 server will be unable to restore its database if the
    BACKUP DB was done using a language other the default American
    English language. Under such circumstances, the restore fails
    with ANR4602E or ANR2025E errors.
    
    Customer/L2 Diagnostics:
    The error receive depends on which language is used for the
    BACKUP DB command and which language is used for the
    "dsmserv restore db" operation. Examples provided below.
    
    1)  BACKUP DB done with "LANGUAGE Ja_JP" server option.
        The "dsmserv restore db" is done with "LANGUAGE Ja_JP".
        This fails with ANR4602E error. For example :
    
    $ dsmserv restore db
    ANR7800I DSMSERV generated at 16:29:44 on Mar 13 2009.
    ...
    ANR4602E TODATE 09/05/01 23:59:59 ...
    $
    
    2)  BACKUP DB done with "LANGUAGE Ja_JP" server option.
        The "dsmserv restore db" is done with "LANGUAGE AMENG".
        This fails with ANR4602E error. For example :
    
    $ dsmserv restore db
    ...
    ANR4636I Starting roll-forward database restore.
    ANR4602E No volumes found for TODATE 05/01/09 23:59:59.
    $
    
    3) BACKUP DB done with default "LANGUAGE AMENG" server option.
       The "dsmserv restore db" is done with "LANGUAGE Ja_JP".
       This fails with ANR2025E error. For example :
    
    $ dsmserv restore db
    ANR7800I DSMSERV generated at 16:29:44 on Mar 13 2009.
    ...
    ANR2025E RESTORE DB: ...
    $
    
    4)  BACKUP DB done with default "LANGUAGE AMENG" server option.
        The "dsmserv restore db" is done with "LANGUAGE AMENG".
        This operation works.
    
    TSM Versions Affected:
    TSM 6.1 servers on all platforms. It affects both point-in-time
    and roll-forward database restores.
    
    Additional Keywords:
    database recovery disaster zz61
    

Local fix

  • 1) Use the defaut LANGUAGE server option (LANGUAGE AMENG) to
       perform both the BACKUP DB and "dsmserv restore db"
       operations.
    --OR--
    2) If a LANGUAGE option other than Amenrican English must be
       used for the BACKUP DB operation, the volume history file
       needs to be translated into the english language and the
       "dsmserv restore db" operation must be done with the default
       "LANGUAGE AMENG" server option. Use the below example as a
       template for translating the volume history file.
     **************************************************
     Operation Date/Time:   2009/05/04 05:24:31
     Volume Type:  BACKUPFULL
    * Location for volume /opt/tivoli/tsm/file/41439894.DBV is: ''
     Database Backup LLA:  FULL_BACKUP.20090504052431.2
     Database Backup HLA:  /NODE0000/
     Volume Name:  "/opt/tivoli/tsm/file/41439894.DBV"
     Backup Series:       3
     Backup Op:       0
     Volume Seq:       2
      Device Class Name:  FILEDEV
     Database Backup ID:         0 ,    4098
      Database Backup Home Position:      0
      Database Backup Total Data Bytes :           0 , 338305035
      Database Backup Total Log Bytes:           0 ,  12627979
      Database Backup Log Block Number:          -1 ,        -1
     **************************************************
    The parameters in the volume history file are both case
    sensitive and position sensitive. For example,
    Database Backup LLA:
    cannot be :
    Database Backup LLA :
    Be sure to keep the appropriate format in the volume
    history file as per above template.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manage server users of    *
    *                 restore DB in a non-English environment.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR Description.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the fix pack containing this fix       *
    *                 when available. This problem is currently    *
    *                 projected to be fixed                        *
    *                   in fix pack 6.1.2.  Note that this is      *
    *                 subject to change at the discretion of IBM.  *
    ****************************************************************
    *
    

Problem conclusion

  • The issue has been corrected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC61029

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-05

  • Closed date

    2009-06-11

  • Last modified date

    2009-06-11

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

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

Fix information

  • Fixed component name

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61L PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager

Software version:

61A

Reference #:

IC61029

Modified date:

2009-06-11

Translate my page

Machine Translation

Content navigation