This has been submitted to Tivoli support, but I wanted to see if anyone else has experienced this problem.
Environment: TSM server version 4.2.1.19 running on AIX version 5.1 Windows 2000 server client running SQL server 7.0 TSM client ver 5.1.0.1 TDP for SQL 2.2.1 What happens: As soon as backup using TDP for SQL begins, the TSM server gets the following messages, then goes down. Backup using B/A client is ok. 05/02/02 13:58:21,ANR0406I Session 43 started for node USHERNT49_SQL (TDP MSSQLV2 NT) (Tcp/Ip 10.130.10.64(2877)). 05/02/02 13:58:21,ANR0406I Session 44 started for node USHERNT49_SQL (TDP MSSQLV2 NT) (Tcp/Ip 10.130.10.64(2878)). 05/02/02 13:58:21,"ANR9999D smnode.c(6243): ThreadId<48> Error receiving EventLog Verb - invalid data type, 21300, received for event number 4995 from node (TDP MSSQLV2 NT)USHERNT49_SQL. " TSM server crashes, AIX 5.1, TSM server 4.2.1.11, 3494 library 3590E1AXL tape drives, SSA disk pools 05/02/02 14:35:17,"ANR9999D smnode.c(6243): ThreadId<77> Error receiving EventLog Verb - invalid data type, 21300, received for event number 4995 from node (TDP MSSQLV2 NT)USHERNT49_SQL. " 05/02/02 14:35:17,ANR9999D pkshmem.c(337): ThreadId<77> Invalid attempt to free memory; called from 10031057c (SmDoEventLog). 05/02/02 14:35:17,ANR9999D pkshmem.c(337): ThreadId<77> Invalid attempt to free memory; called from 10031057c (SmDoEventLog). 05/02/02 14:35:18,"ANR9999D smnode.c(6243): ThreadId<77> Error receiving EventLog Verb - invalid data type, 21300, received for event number 4991 from node (TDP MSSQLV2 NT)USHERNT49_SQL. " 05/02/02 14:35:18,ANR9999D pkshmem.c(337): ThreadId<77> Invalid attempt to free memory; called from 10031057c (SmDoEventLog). 05/02/02 14:35:18,ANR9999D pkshmem.c(337): ThreadId<77> Invalid attempt to free memory; called from 10031057c (SmDoEventLog). 05/02/02 14:35:18,"ANR9999D smnode.c(6243): ThreadId<77> Error receiving EventLog Verb - invalid data type, 21300, received for event number 4991 from node (TDP MSSQLV2 NT)USHERNT49_SQL. " 05/02/02 14:35:18,ANR9999D pkshmem.c(337): ThreadId<77> Invalid attempt to free memory; called from 10031057c (SmDoEventLog). 05/02/02 14:35:18,ANR9999D pkshmem.c(337): ThreadId<77> Invalid attempt to free memory; called from 10031057c (SmDoEventLog). 05/02/02 14:35:45,ANR0407I Session 65 started for administrator MCOZART (AIX) (Tcp/Ip 10.5.10.81(35257)). 05/02/02 14:35:45,ANR2017I Administrator MCOZART issued command: QUERY PROCESS 05/02/02 14:35:45,ANR0405I Session 65 ended for administrator(AIX). 05/02/02 14:36:07,"ANR9999D smnode.c(6243): ThreadId<77> Error receiving EventLog Verb - invalid data type, 21300, received for event number 4991 from node (TDP MSSQLV2 NT)USHERNT49_SQL. " Background of events: Node was originally a TDP for SQL v1.1 client running SQL 7.0 SP2. Backups were going fine. I updated all the TSM agents to latest, renamed node, registered new node in different policy domain. First backup brought down the TSM server. I didn't realize at the time that the SQL server was only at SP2 and that is not supported by the latest TDP for SQL. So I tried going to the 2.2.0 version for SQL, that still brought down TSM. The SQL team upgraded it to SP3. Still bringing down the TSM server using TDP for SQL agent 2.2.0 and 2.2.1. The following message has occurred in the dsierror.log: 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 ANS0106E ReadIndex: Message index not found for message 1005. 05/02/2002 14:00:32 sessOpen: Error -50 receiving IdentifyResp verb from server 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 sessOpen: Error -50 receiving IdentifyResp verb from server 05/02/2002 14:00:32 sessOpen: Error -50 receiving IdentifyResp verb from server 05/02/2002 14:00:32 sessOpen: Error -50 receiving IdentifyResp verb from server 05/02/2002 14:00:32 cuIdentifyResp: Error -50 reading IdentifyResp from server. 05/02/2002 14:00:32 sessOpen: Error -50 receiving IdentifyResp verb from server 05/02/2002 14:00:32 sessOpen: Error -50 receiving IdentifyResp verb from server I have successfully backed up the SQL node to a TSM test server running W2K and running TSM server levels 4.2.1.9 and 4.2.1.11, however when it goes to our production AIX server, no matter what level of TDP for SQL version we use, it brings the server down. Any thoughts on this?? Thanks, Matt Adams Tivoli Storage Manager Team Hermitage Site Tech Deloitte & Touche USA LLP 615.882.6861 - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
