APAR status
Closed as program error.
Error description
Mirrorlogfiles may not be copied while TSM Server starting. The problem occurs after we make Point in Time restore. You will see the symptom in the following steps: ---------------------------------------- 1) Configure TSM Server environment with adding mirrorlogdir entry in dsmserv.opt. 2) Remove TSMDB1 DB: "dsmserv removedb TSMDB1" 3) Make a PIT restore: For example "dsmserv restore db todate=today totime=now" 4) Start dsmserv. ---------------------------------------- Then, you can see that activelogfiles are not copied to mirrorlogdir though there is a mirrorlogdir entry in dsmserv.opt. Customer/L2 Diagnostics: ---------------------------------------- Result of "db2 get db cfg for TSMDB1" shows the following result: (MIRRORLOGPATH) = <mirrorlogdir>/NODE0000/ However, there is not NODE0000 directory under <mirrorlogdir> after PIT restore. db2diag.log will show the following record: 2010-12-**-17.51.13.295076-360 E234064A629 LEVEL: Error PID : 10879056 TID : 1801 PROC : db2sysc 0 INSTANCE: tsminst1 NODE : 000 DB : TSMDB1 APPHDL : 0-8 APPID: *LOCAL.tsminst1.101201235113 AUTHID : TSMINST1 EDUID : 1801 EDUNAME: db2agent (TSMDB1) 0 FUNCTION: DB2 UDB, data protection services, sqlpgnlp, probe:4420 MESSAGE : ADM1810E The new value of the MIRRORLOGPATH DB configuration parameter is invalid or cannot be used. DB2 will ignore the new value. Confirm the new path value and ensure that it is valid. ---------------------------------------- TSM Versions Affected: TSM 6.X Servers on all platforms. Initial Impact: Low Additional Keywords: zz61 zz62 mirrorlogdir NODE0000
Local fix
Create "NODE0000" directory by the Tivoli Storage Manager/DB2 instance user under the path of Mirrorlogdir and reboot dsmserv.
Problem summary
**************************************************************** * USERS AFFECTED: All Tivoli Storage Manager server users. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 6.1.5 and 6.2.3. Note that this * * is subject to change at the discretion of * * IBM. * **************************************************************** *
Problem conclusion
This problem was fixed. Affected platforms: AIX, HP-UX, Sun Solaris, Linux and Windows .
Temporary fix
Comments
APAR Information
APAR number
IC73104
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-12-08
Closed date
2011-01-10
Last modified date
2011-01-10
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
R62A PSY
UP
R62H PSY
UP
R62L PSY
UP
R62S PSY
UP
R62W 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":"61A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
10 January 2011