Direct links to fixes
6.3.6.000-TIV-TSMRPT-AGENT-Linux
6.3.6.000-TIV-TSMRPT-AGENT-AIX
6.3.6.000-TIV-TSMRPT-AIX
6.3.6.000-TIV-TSMRPT-AGENT-Windows
6.3.6.000-TIV-TSMRPT-Linuxx86
6.3.6.000-TIV-TSMRPT-Linuxx86_64
6.3.6.000-TIV-TSMRPT-WindowsI32
6.3.6.000-TIV-TSMRPT-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsI32
6.3.6.000-TIV-TSMAC-SolarisSPARC
6.3.6.000-TIV-TSMAC-Linuxx86
6.3.6.000-TIV-TSMAC-Linuxs390x
6.3.6.000-TIV-TSMAC-AIX
6.3.6.000-TIV-TSMALL-SolarisSPARC
6.3.6.000-TIV-TSMALL-WindowsX64
6.3.6.000-TIV-TSMSTA-WindowsI32
6.3.6.000-TIV-TSMALL-HP-UX
6.3.6.000-TIV-TSMALL-Linuxppc64
6.3.6.000-TIV-TSMALL-AIX
6.3.6.000-TIV-TSMALL-Linuxs390x
6.3.6.000-TIV-TSMALL-Linuxx86_64
IBM Tivoli Storage Manager V6.3 Fix Pack 6 (6.3.6.000) Server Downloads
APAR status
Closed as documentation error.
Error description
The Tivoli Storage Manager Server installation or upgrade will fail at the DB2 installation stage with the following error: ANRI1020E: The DB2 installation failed. To review errors and correct any issues, review: C:\ProgramData\IBM\Installation Manager\logs\native\tsm_logs\db2_install.log The DB2 installation on Windows requires Microsoft 8.3 filename convention and if this is disabled, the installation or upgrade will fail. NOTE: Starting with Microsoft Windows Server 2012 R2, the 8dot3 filename support is disabled by default on non-system drives (e.g. D:\) Starting with WinPE 4.0 (Windows Preinstallation Environment), the 8dot3 filename support is disabled for all volumes including the system drive. Any Windows images created using WinPE 4.0 or later will have 8dot3 filename support disabled. Tivoli Storage Manager Versions Affected: All supported versions of Tivoli Storage Manager Server on Windows platform Initial Impact: Medium Additional Keywords: TSM Installation upgrade server 8.3 filename 8dot3 support ANRI1020E
Local fix
Review the following technote to understand the current DB2 design limitation and how to fix this : http://www-01.ibm.com/support/docview.wss?uid=swg21929296
Problem summary
**************************************************************** * USERS AFFECTED: * * Tivoli Storage Manager Windows users * **************************************************************** * PROBLEM DESCRIPTION: * * see error description * **************************************************************** * RECOMMENDATION: * * Update the install guide. * ****************************************************************
Problem conclusion
Update the Installation Guide with a new topic as follows: Prepare to install DB2 on Windows Before you install DB2 on Windows operating systems, ensure that you correctly configured your directory names. Short file names If DB2 is installed on a drive on which 8.3 file names are disabled, and the DB2 installation directory name has spaces in it, DB2 must be reinstalled on a drive that has 8.3 file names that are enabled, or in a directory that does not have spaces in the name. 8.3 file name support is disabled by default for all non-system drives, for example D:\, since Windows Server 2012 R2. 8.3 file name support is also disabled by default for all volumes since Windows Preinstallation Environment (WinPE) 4.0. To check the current 8.3 file name settings for a drive, in a DB2 command window, run the fsutil.exe behavior query disable8dot3 command. These are the values when you run the command: 0 = Create 8.3 short file names (default) 1 = Do not create 8.3 file names 2 = Set 8.3 file names on a per volume basis 3 = Disable 8.3 file names on all volumes, except the system volume The registry state of NtfsDisable8dot3NameCreation is 0, which means that 8.3 file names are enabled on all volumes To enable 8.3 file names on a global basis, run the fsutil.exe behavior set disable8dot3 0 command. This problem is currently projected to be fixed in levels 6.3.6 and 7.1.4. Note that this is subject to change at the discretion of IBM. Affected platforms: Windows.
Temporary fix
Comments
APAR Information
APAR number
IT09491
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71W
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-17
Closed date
2015-08-10
Last modified date
2015-08-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
Document Information
Modified date:
10 August 2015