IBM Support

IC54652: ANR2032E BACKUP NODE: COMMAND FAILED - INTERNAL SERVER ERROR DETECTED WHEN NO DATA TO BACK UP.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A "BACKUP NODE" command ran via admin schedule to backup
    differential data incorrectly reports a command failure when
    there is no data to backup.
    
    The following conditions must be met for this problem to occur :
    
    1. The BACKUP NODE must be run from the TSM admin scheduler.
    2. The WAIT=YES paramater must be specified.
    3. There is no data to process for the differential backup or
       full backup.
    
    Under these conditions, the ANR1136W message along with ANR2032E
    message will be issued. For example :
    
    ANR1136W NAS Backup process XXX completed - There is no data to
     process for the  differential backup of NAS node MYNAS, file
     space /MYFS.
    
    ANR2032E BACKUP NODE: Command failed - internal server error
     detected.
    
    An example of actlog messages received for the BACKUP NODE
    run under the NAS_SCHED admin schedule follows :
    
    ANR2017I Administrator XXXXX issued command: BACKUP NODE
     MYNAS /MYFS mgmtclass=MYMGMT MODE=DIFF wait=yes
    ANR2753I (NAS_SCHED):ANR0984I Process XXX for BACKUP NAS
    ANR2753I (NAS_SCHED):(DIFFERENTIAL) started in the
    ANR2753I (NAS_SCHED):FOREGROUND at <timestamp>
    ANR2753I (NAS_SCHED):ANR1064I Differential backup of NAS
    ANR2753I (NAS_SCHED):node MYNAS, file system
    ANR2753I (NAS_SCHED):/MYFS, started as process XXX
    ANR2753I (NAS_SCHED):by administrator XXXXX.
    ANR2753I (NAS_SCHED):ANR1136W NAS Backup process XXX
    ANR2753I (NAS_SCHED):completed - There is no data to
    ANR2753I (NAS_SCHED):process for the differential backup
    ANR2753I (NAS_SCHED):of NAS node  MYNAS, file space
    ANR2753I (NAS_SCHED):/MYFS.
    ANR2753I (NAS_SCHED):ANR0985I Process XXX for BACKUP NAS
    ANR2753I (NAS_SCHED):(DIFFERENTIAL) running in the
    ANR2753I (NAS_SCHED):FOREGROUND completed with
    ANR2753I (NAS_SCHED):completion state SUCCESS at
    ANR2753I (NAS_SCHED):<timestamp>.
    ANR2753I (NAS_SCHED):ANR2032E BACKUP NODE: Command
    ANR2753I (NAS_SCHED):failed - internal server error
    ANR2753I (NAS_SCHED):detected.
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> issued
    ANR2753I (NAS_SCHED):message 2032 from:
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn>   0x00000001-
    ANR2753I (NAS_SCHED):006301d0 AdmBackupNode
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x00000001-
    ANR2753I (NAS_SCHED):001581f4 AdmCommandLocal
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x00000001-
    ANR2753I (NAS_SCHED):0015900c admCommand
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x00000001-
    ANR2753I (NAS_SCHED):005f06dc SmExecScheduledCommand
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x00000001-
    ANR2753I (NAS_SCHED):005f090c smScheduledConsoleSession
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x00000001-
    ANR2753I (NAS_SCHED):005ee9a0 CsRunCmdThread
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x00000001-
    ANR2753I (NAS_SCHED):0000fc2c StartThread
    ANR2753I (NAS_SCHED):ANR9999D ThreadId <nn> 0x09000000-
    ANR2753I (NAS_SCHED):00403448 _pthread_body
    ANR2752E Scheduled command NAS_SCHED failed.
    
    Platforms affected:
    TSM 5.3, 5.4 and 5.5 servers on all platforms.
    
    Additional Keywords:
    Celera Celerra ndmp
    

Local fix

  • To avoid the ANR2032E and ANR9999D messages, run the BACKUP NODE
    command via the admin command line or ISC instead of admin
    scheduler or do not specify WAIT=YES.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: "Backup node xxx mode=diff wait=yes" from    *
    *                 admin client to backup differential data     *
    *                 while there is no data to backup.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available.           *
    *                 This problem is currently projected to be    *
    *                 fixed in levels 5.4.4 and 5.5.1.             *
    *                 Note that this is subject to change at the   *
    *                 discretion of IBM.                           *
    ****************************************************************
    *
    

Problem conclusion

  • The TSM server has been corrected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC54652

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    54A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-12-10

  • Closed date

    2008-02-05

  • Last modified date

    2008-09-24

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

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

    PK60516

Fix information

  • Fixed component name

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R54A PSY

       UP

  • R54H PSY

       UP

  • R54L PSY

       UP

  • R54S PSY

       UP

  • R54W PSY

       UP

  • R55A PSY

       UP

  • R55H PSY

       UP

  • R55L PSY

       UP

  • R55S PSY

       UP

  • R55W PSY

       UP

[{"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":"54A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
24 September 2008