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: 00000000003faddb
> •         Exception Code: c0000409
> •         Exception Data: 0000000000000000
> •         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: 00000000003faddb
> •         Exception Code: c0000409
> •         Exception Data: 0000000000000000
> •         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 http://infosecurity.vcu.edu/phishing.html
>



--
*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

Reply via email to