Re: tdp for ms sql client download
The best place is Passport Advantage http://www-01.ibm.com/software/passportadvantage/pao_customer.html On Thu, Jul 9, 2015 at 8:14 AM, Lee, Gary g...@bsu.edu wrote: Trying to find this client. Where does it live? We are licensed for tsm extended edition, tdp for databases, hsm, and other stuff.
tdp for ms sql client download
Trying to find this client. Where does it live? We are licensed for tsm extended edition, tdp for databases, hsm, and other stuff.
Re: tdp for ms sql client download
I can find the latest (7.1.2.0) maintenance release here: ftp://service.boulder.ibm.com//storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntsql/v712/windows but you have to have the license-key which comes via Passport. On Thu, Jul 9, 2015 at 10:23 AM, Nick Marouf mar...@gmail.com wrote: The best place is Passport Advantage http://www-01.ibm.com/software/passportadvantage/pao_customer.html On Thu, Jul 9, 2015 at 8:14 AM, Lee, Gary g...@bsu.edu wrote: Trying to find this client. Where does it live? We are licensed for tsm extended edition, tdp for databases, hsm, and other stuff. -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Issued with TDP SQL 7.1.2.0 and 2014 SQL server
Thank you for the details. That definitely seems to be our problem. Will see if I can get through and subscribe for when the APAR is resolved. You said there was a hot fix. How would we get it? On Thu, Jul 9, 2015 at 12:55 PM, J. Pohlmann jpohlm...@shaw.ca wrote: Hi Zoltan. Here is a clip of the APAR: IT09192: DATABASE BACKUPS USING DATA PROTECTION FOR SQL CAN CRASH DURING PROCESSING WITH REFERENCES TO MODULE CLR.DLL Description • When attempting a legacy backup of a Microsoft SQL database • the Tivoli Storage Manager for Databases: Data Protection • for Microsoft SQL Server application can crash with the • following details when run from the MMC: • Problem signature: • Problem Event Name: BEX64 • Application Name: mmc.exe • Application Version: 6.1.7600.16385 • Application Timestamp: 4a5bc808 • Fault Module Name: clr.dll • Fault Module Version: 4.0.30319.17929 • Fault Module Timestamp: 4ffa59b1 • Exception Offset: 003faddb • Exception Code: c409 • Exception Data: • OS Version: 6.1.7601.2.1.0.274.10 • Locale ID: 1033 • Additional Information 1: 3381 • Additional Information 2: 338146cd4c3fffe86b5c5e62544c183c • Additional Information 3: 936b • Additional Information 4: 936bc181c072ab550a04c713d644b771 • • When run via the CLI, these details are reported: • Problem signature: • Problem Event Name: BEX64 • Application Name: tdpsqlc.exe • Application Version: 7.1.2.0 • Application Timestamp: 55102a96 • Fault Module Name: clr.dll • Fault Module Version: 4.0.30319.17929 • Fault Module Timestamp: 4ffa59b1 • Exception Offset: 003faddb • Exception Code: c409 • Exception Data: • OS Version: 6.1.7601.2.1.0.274.10 • Locale ID: 1033 • Additional Information 1: f566 • Additional Information 2: f56603cc7a58ea5bb439787f63f14af5 • Additional Information 3: f62c • Additional Information 4: f62c63d10952430866f64bd780cbbed3 • • In either method of execution, the backup is successful, however • there will be no summary information in the tdpsql.log or • /logfile parameter value. The backup objects can still be • viewed in the recovery tab, or from the 'query tsm' output. • Scheduled command operations may not report this crash to the • console, but the crash details will be seen in the event logs. • Restores of SQL databases using backups created when this crash • occurs is possible. • • Customer/L2 Diagnostics: The DP SQL trace may end abnormally • near the entries from SQLAPI-CSqlApi::GetSqlDatabaseNames() or • updateProtectSize() funtions: • • SqlApi.cpp (1230): SQLAPI-CSqlApi::GetSqlDatabaseNames •enter 15:11:03 • SqlApi.cpp (6847): SQLAPI-CSqlApi::LogonServer • enter 15:11:03 • SqlApi.cpp (7237): SQLAPI-CSqlApi::LogonServer • exit rc(0):RC_OK 15:11:03 • ... • backupdb.cpp(2473): Calling DSMUPDATEFS() • backupdb.cpp(2491): DSMUPDATEFS() was successful. • backupdb.cpp(2505): Exiting updateProtectSize(): • Returning with rc = 0. • • • The call stack retrieved from the crash dump may show the • following call sequence: • DBaseEri.ProcessRequest(...) - eriBackupSqlDatabase(...) - • updateProtectSize(...) - CSqlApi.GetSqlDatabaseNames(...) • • Versions Affected: Tivoli Storage Manager for Databases: Data • Protection for Microsoft SQL 7.1.2 • • Initial Impact: Medium • • Additional Keywords: dpsql core wer • Local fix • Since the backups are successful, the crash can be ignored. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: July 9, 2015 09:46 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Issued with TDP SQL 7.1.2.0 and 2014 SQL server On Thu, Jul 9, 2015 at 12:39 PM, J. Pohlmann jpohlm...@shaw.ca wrote: IT09192 Thank you for the information. Unfortunately I can not get to the pertinent information. When I Google that APAR, the link takes me to the IBM Support Portal and when I attempt to sign-in, I get a Our apologies...The page you requested cannot be displayed - 504 Gateway Timeout If you can get to it, can you send me the details/description? IBM seems to be having some problems. -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University
Re: Issued with TDP SQL 7.1.2.0 and 2014 SQL server
Hi Zoltan. Here is a clip of the APAR: IT09192: DATABASE BACKUPS USING DATA PROTECTION FOR SQL CAN CRASH DURING PROCESSING WITH REFERENCES TO MODULE CLR.DLL Description • When attempting a legacy backup of a Microsoft SQL database • the Tivoli Storage Manager for Databases: Data Protection • for Microsoft SQL Server application can crash with the • following details when run from the MMC: • Problem signature: • Problem Event Name: BEX64 • Application Name: mmc.exe • Application Version: 6.1.7600.16385 • Application Timestamp: 4a5bc808 • Fault Module Name: clr.dll • Fault Module Version: 4.0.30319.17929 • Fault Module Timestamp: 4ffa59b1 • Exception Offset: 003faddb • Exception Code: c409 • Exception Data: • OS Version: 6.1.7601.2.1.0.274.10 • Locale ID: 1033 • Additional Information 1: 3381 • Additional Information 2: 338146cd4c3fffe86b5c5e62544c183c • Additional Information 3: 936b • Additional Information 4: 936bc181c072ab550a04c713d644b771 • • When run via the CLI, these details are reported: • Problem signature: • Problem Event Name: BEX64 • Application Name: tdpsqlc.exe • Application Version: 7.1.2.0 • Application Timestamp: 55102a96 • Fault Module Name: clr.dll • Fault Module Version: 4.0.30319.17929 • Fault Module Timestamp: 4ffa59b1 • Exception Offset: 003faddb • Exception Code: c409 • Exception Data: • OS Version: 6.1.7601.2.1.0.274.10 • Locale ID: 1033 • Additional Information 1: f566 • Additional Information 2: f56603cc7a58ea5bb439787f63f14af5 • Additional Information 3: f62c • Additional Information 4: f62c63d10952430866f64bd780cbbed3 • • In either method of execution, the backup is successful, however • there will be no summary information in the tdpsql.log or • /logfile parameter value. The backup objects can still be • viewed in the recovery tab, or from the 'query tsm' output. • Scheduled command operations may not report this crash to the • console, but the crash details will be seen in the event logs. • Restores of SQL databases using backups created when this crash • occurs is possible. • • Customer/L2 Diagnostics: The DP SQL trace may end abnormally • near the entries from SQLAPI-CSqlApi::GetSqlDatabaseNames() or • updateProtectSize() funtions: • • SqlApi.cpp (1230): SQLAPI-CSqlApi::GetSqlDatabaseNames •enter 15:11:03 • SqlApi.cpp (6847): SQLAPI-CSqlApi::LogonServer • enter 15:11:03 • SqlApi.cpp (7237): SQLAPI-CSqlApi::LogonServer • exit rc(0):RC_OK 15:11:03 • ... • backupdb.cpp(2473): Calling DSMUPDATEFS() • backupdb.cpp(2491): DSMUPDATEFS() was successful. • backupdb.cpp(2505): Exiting updateProtectSize(): • Returning with rc = 0. • • • The call stack retrieved from the crash dump may show the • following call sequence: • DBaseEri.ProcessRequest(...) - eriBackupSqlDatabase(...) - • updateProtectSize(...) - CSqlApi.GetSqlDatabaseNames(...) • • Versions Affected: Tivoli Storage Manager for Databases: Data • Protection for Microsoft SQL 7.1.2 • • Initial Impact: Medium • • Additional Keywords: dpsql core wer • Local fix • Since the backups are successful, the crash can be ignored. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: July 9, 2015 09:46 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Issued with TDP SQL 7.1.2.0 and 2014 SQL server On Thu, Jul 9, 2015 at 12:39 PM, J. Pohlmann jpohlm...@shaw.ca wrote: IT09192 Thank you for the information. Unfortunately I can not get to the pertinent information. When I Google that APAR, the link takes me to the IBM Support Portal and when I attempt to sign-in, I get a Our apologies...The page you requested cannot be displayed - 504 Gateway Timeout If you can get to it, can you send me the details/description? IBM seems to be having some problems. -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit
Re: Issued with TDP SQL 7.1.2.0 and 2014 SQL server
Zoltan, you are experiencing APAR IT09192 - there is an e-fix for the crash at program termination. Please not the local fix - ignore the crash. There is no patch yet. Joerg Pohlmann -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: July 9, 2015 08:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Issued with TDP SQL 7.1.2.0 and 2014 SQL server My SQL guy is having some interesting problems/crashes with the latest and greatest SQL/TDP He is running TSM client 7.1.2.0 and was running 7.1.1.2 TDP SQL. They he started getting error messages and not able to backup mirrored DB's. *ACO6113I Backup of database 'AMCASV2' is bypassed because it is a mirrored database. Database attributes are Normal|AutoClosed.* So, he install 7.1.2.0 and started having problems with transaction log backups at first and now all over. The TDP would backup 1-database and crash/severely disconnect from the TSM server (TSM server is 6.3.5.100 Linux). Messages like this: 07/07/2015 06:27:49 ANS1577I The Windows console event handler received a 'Shutdown' console event. 07/07/2015 06:27:49 ANS2820E An interrupt has occurred. The current operation will end and the client will shut down. We would also see what looks like memory corruption in the dsmerror.log files: 07/7//2015 06:37:061:37:2177I S1577I indohe windows colo evole enent hahdlnr dlerrreeeived daa 'Shutdotdown' conse eveeven. t. 07//09/2015 06 :06:6:56 6 ANS157 ThI ehei Wins console s vect hsndle er receive dana dSlutr rwne eionsvled 'Senhut down' console event. He tried everything he could but eventually had to return to TDP 7.1.1.2 to be able to backup everything else but the mirrored DB's. Additional error message in the Windows logs: Faulting application name: tdpsqlc.exe, version: 7.1.2.0, time stamp: 0x55102a96 Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0x5348a1ef Exception code: 0xc409 Fault offset: 0x00355714 Faulting process id: 0xfec Faulting application start time: 0x01d0b8bf99e51e51 Faulting application path: C:\Program Files\Tivoli\TSM\TDPSql\tdpsqlc.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Any thoughts / suggestions? Don't see any patches for TDP SQL 7.1.2, yet. -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Issued with TDP SQL 7.1.2.0 and 2014 SQL server
On Thu, Jul 9, 2015 at 12:39 PM, J. Pohlmann jpohlm...@shaw.ca wrote: IT09192 Thank you for the information. Unfortunately I can not get to the pertinent information. When I Google that APAR, the link takes me to the IBM Support Portal and when I attempt to sign-in, I get a Our apologies...The page you requested cannot be displayed - 504 Gateway Timeout If you can get to it, can you send me the details/description? IBM seems to be having some problems. -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
What are these activity types in the ACTIVITY_SUMMARY table
In the ACTIVITY_SUMMARY table, there are two activity types that I do not understand: POOLCOPYUTILGB POOLPRIMUTILGB I can see these activities are running frequently, but I can't figure out what they are. I haven't been able to find any documentation on the activity types in the ACTIVITY_SUMMARY, and googling hasn't turned up anything either. Can anyone clue me into what they are? Thanks, -- Brian Kunst Storage Administrator Large Scale Storage Systems UW Information Technology
Re: Issued with TDP SQL 7.1.2.0 and 2014 SQL server
You will need to open a PMR with IBM and reference this APAR. Best regards, Joerg -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: July 9, 2015 10:08 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Issued with TDP SQL 7.1.2.0 and 2014 SQL server Thank you for the details. That definitely seems to be our problem. Will see if I can get through and subscribe for when the APAR is resolved. You said there was a hot fix. How would we get it? On Thu, Jul 9, 2015 at 12:55 PM, J. Pohlmann jpohlm...@shaw.ca wrote: Hi Zoltan. Here is a clip of the APAR: IT09192: DATABASE BACKUPS USING DATA PROTECTION FOR SQL CAN CRASH DURING PROCESSING WITH REFERENCES TO MODULE CLR.DLL Description • When attempting a legacy backup of a Microsoft SQL database • the Tivoli Storage Manager for Databases: Data Protection • for Microsoft SQL Server application can crash with the • following details when run from the MMC: • Problem signature: • Problem Event Name: BEX64 • Application Name: mmc.exe • Application Version: 6.1.7600.16385 • Application Timestamp: 4a5bc808 • Fault Module Name: clr.dll • Fault Module Version: 4.0.30319.17929 • Fault Module Timestamp: 4ffa59b1 • Exception Offset: 003faddb • Exception Code: c409 • Exception Data: • OS Version: 6.1.7601.2.1.0.274.10 • Locale ID: 1033 • Additional Information 1: 3381 • Additional Information 2: 338146cd4c3fffe86b5c5e62544c183c • Additional Information 3: 936b • Additional Information 4: 936bc181c072ab550a04c713d644b771 • • When run via the CLI, these details are reported: • Problem signature: • Problem Event Name: BEX64 • Application Name: tdpsqlc.exe • Application Version: 7.1.2.0 • Application Timestamp: 55102a96 • Fault Module Name: clr.dll • Fault Module Version: 4.0.30319.17929 • Fault Module Timestamp: 4ffa59b1 • Exception Offset: 003faddb • Exception Code: c409 • Exception Data: • OS Version: 6.1.7601.2.1.0.274.10 • Locale ID: 1033 • Additional Information 1: f566 • Additional Information 2: f56603cc7a58ea5bb439787f63f14af5 • Additional Information 3: f62c • Additional Information 4: f62c63d10952430866f64bd780cbbed3 • • In either method of execution, the backup is successful, however • there will be no summary information in the tdpsql.log or • /logfile parameter value. The backup objects can still be • viewed in the recovery tab, or from the 'query tsm' output. • Scheduled command operations may not report this crash to the • console, but the crash details will be seen in the event logs. • Restores of SQL databases using backups created when this crash • occurs is possible. • • Customer/L2 Diagnostics: The DP SQL trace may end abnormally • near the entries from SQLAPI-CSqlApi::GetSqlDatabaseNames() or • updateProtectSize() funtions: • • SqlApi.cpp (1230): SQLAPI-CSqlApi::GetSqlDatabaseNames •enter 15:11:03 • SqlApi.cpp (6847): SQLAPI-CSqlApi::LogonServer • enter 15:11:03 • SqlApi.cpp (7237): SQLAPI-CSqlApi::LogonServer • exit rc(0):RC_OK 15:11:03 • ... • backupdb.cpp(2473): Calling DSMUPDATEFS() • backupdb.cpp(2491): DSMUPDATEFS() was successful. • backupdb.cpp(2505): Exiting updateProtectSize(): • Returning with rc = 0. • • • The call stack retrieved from the crash dump may show the • following call sequence: • DBaseEri.ProcessRequest(...) - eriBackupSqlDatabase(...) - • updateProtectSize(...) - CSqlApi.GetSqlDatabaseNames(...) • • Versions Affected: Tivoli Storage Manager for Databases: Data • Protection for Microsoft SQL 7.1.2 • • Initial Impact: Medium • • Additional Keywords: dpsql core wer • Local fix • Since the backups are successful, the crash can be ignored. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: July 9, 2015 09:46 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Issued with TDP SQL 7.1.2.0 and 2014 SQL server On Thu, Jul 9, 2015 at 12:39 PM, J. Pohlmann jpohlm...@shaw.ca wrote: IT09192 Thank you for the information. Unfortunately I can not get to the pertinent information. When I Google that APAR, the link takes me to the IBM Support Portal and when I attempt to sign-in,
Re: What are these activity types in the ACTIVITY_SUMMARY table
Brian, My guess is that these entries are used for capacity trend graphs in Operations Center. Le 10 juillet 2015 00:42:05 GMT+07:00, Brian G. Kunst bku...@uw.edu a écrit : In the ACTIVITY_SUMMARY table, there are two activity types that I do not understand: POOLCOPYUTILGB POOLPRIMUTILGB I can see these activities are running frequently, but I can't figure out what they are. I haven't been able to find any documentation on the activity types in the ACTIVITY_SUMMARY, and googling hasn't turned up anything either. Can anyone clue me into what they are? Thanks, -- Brian Kunst Storage Administrator Large Scale Storage Systems UW Information Technology -- Erwann SIMON Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
Re: What are these activity types in the ACTIVITY_SUMMARY table
Are ther any tasks like backup storage pool? On Jul 9, 2015 12:43 PM, Brian G. Kunst bku...@uw.edu wrote: In the ACTIVITY_SUMMARY table, there are two activity types that I do not understand: POOLCOPYUTILGB POOLPRIMUTILGB I can see these activities are running frequently, but I can't figure out what they are. I haven't been able to find any documentation on the activity types in the ACTIVITY_SUMMARY, and googling hasn't turned up anything either. Can anyone clue me into what they are? Thanks, -- Brian Kunst Storage Administrator Large Scale Storage Systems UW Information Technology
Issued with TDP SQL 7.1.2.0 and 2014 SQL server
My SQL guy is having some interesting problems/crashes with the latest and greatest SQL/TDP He is running TSM client 7.1.2.0 and was running 7.1.1.2 TDP SQL. They he started getting error messages and not able to backup mirrored DB's. *ACO6113I Backup of database 'AMCASV2' is bypassed because it is a mirrored database. Database attributes are Normal|AutoClosed.* So, he install 7.1.2.0 and started having problems with transaction log backups at first and now all over. The TDP would backup 1-database and crash/severely disconnect from the TSM server (TSM server is 6.3.5.100 Linux). Messages like this: 07/07/2015 06:27:49 ANS1577I The Windows console event handler received a 'Shutdown' console event. 07/07/2015 06:27:49 ANS2820E An interrupt has occurred. The current operation will end and the client will shut down. We would also see what looks like memory corruption in the dsmerror.log files: 07/7//2015 06:37:061:37:2177I S1577I indohe windows colo evole enent hahdlnr dlerrreeeived daa 'Shutdotdown' conse eveeven. t. 07//09/2015 06 :06:6:56 6 ANS157 ThI ehei Wins console s vect hsndle er receive dana dSlutr rwne eionsvled 'Senhut down' console event. He tried everything he could but eventually had to return to TDP 7.1.1.2 to be able to backup everything else but the mirrored DB's. Additional error message in the Windows logs: Faulting application name: tdpsqlc.exe, version: 7.1.2.0, time stamp: 0x55102a96 Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0x5348a1ef Exception code: 0xc409 Fault offset: 0x00355714 Faulting process id: 0xfec Faulting application start time: 0x01d0b8bf99e51e51 Faulting application path: C:\Program Files\Tivoli\TSM\TDPSql\tdpsqlc.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Any thoughts / suggestions? Don't see any patches for TDP SQL 7.1.2, yet. -- *Zoltan Forray* TSM Software Hardware Administrator Xymon Monitor Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
