Andy, No output occurs on the CLI interface when the crash occurrs, other than TCP/IP timeout, RC -50, re-issue the command.
On the AIX system, there are no messgaes in dsmserv.err. On the windows system we get the following; (As this has also been confirmed by others now, I will be raising a call with IBM) ==================================================================== Exception generated: 01/14/2005 15:16:30 Module name: Unavailable Current version: 5.2.2.3 Build date: Mar 12 2004 12:02:04 Build Type: 32Bit ==================================================================== Crash dump file: C:\Program Files\tivoli\tsm\server\dsmserv.dmp Exception code: C0000005 (ACCESS_VIOLATION) at 001B:10453D81 Registers: EAX=08C9EA50 EBX=00000000 ECX=08C9EA54 EDX=29274D49 ESI=0475F808 EDI=FFFFFFA4 EBP=08C9F15C ESP=08C9E928 EIP=10453D81 FLG=00010202 CS =0000001B DS =00000023 SS =00000023 ES =00000023 FS =00000038 GS =00000000 Call stack: Address Parameters F()+Offset, File(Line#) ------------------------------------------------------------------------ ------ 10453D81 (0x0475F808 0x00000000 0x04724B90 0x00000000) tsmInitializeServer()+44C551, Unavailable 1045643B (0x00000000 0x00000000 0x00000000 0x00000000) tsmInitializeServer()+44EC0B, Unavailable Exception handler complete. RC: 2 Matt. _-'-_ -|- -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Friday, January 14, 2005 3:51 PM To: [email protected] Subject: Re: SELECT statement crashes server My recommendation: 1) Using the specifics of the crash (I imagine you get a stack trace, or other messages when the crash occurs), go to http://www.ibm.com and try searching for any matching APARs. 2) If you don't find a hit, contact IBM support for additional assistance. The server should not crash. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[email protected]> wrote on 01/14/2005 08:39:05: > Hallo, > > 86% util on a DB of 126GB still leaves upwards of 14GB free to work out > a select query, on a stgpool that has less than 60 volumes in it, so I'm > not sure that's it. > > And, as it goes, I never use the GUI! .. as an aside, I've been smiling > to myself at all the cafuffle caused by the switch to ISC and the > admincenter... > > Matt. > > _-'-_ > -|- > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Killam, Perpetua > Sent: Friday, January 14, 2005 3:16 PM > To: [email protected] > Subject: Re: SELECT statement crashes server > > 86% is bit high for pct.utilized. I had the same problem, and it went > away with adding more space to the tsm db.I am not sure how much > temporary space it requires to complete a fairly large output of an > select statement, but I believe you need more than what you have. I also > believe that its better > To run select statements from the command line rather than from the GUI. > > Cheers, > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Warren, Matthew (Retail) > Sent: Friday, January 14, 2005 9:41 AM > To: [email protected] > Subject: Re: SELECT statement crashes server > > Additionally, our DB and LOG stats are as follows - I believe there is > plenty of DB space for the select to complete; > > DB > Available Space (MB): 136,688 > Assigned Capacity (MB): 126,688 > Maximum Extension (MB): 10,000 > Maximum Reduction (MB): 8,940 > Page Size (bytes): 4,096 > Total Usable Pages: 32,432,128 > Used Pages: 28,159,418 > Pct Util: 86.8 > Max. Pct Util: 86.8 > Physical Volumes: 8 > Buffer Pool Pages: 512,000 > Total Buffer Requests: 157,275 > > LOG > > > AVAIL_SPACE_MB: 12284 > CAPACITY_MB: 11284 > MAX_EXTENSION_MB: 1000 > MAX_REDUCTION_MB: 7468 > PAGE_SIZE: 4096 > USABLE_PAGES: 2888192 > USED_PAGES: 975215 > PCT_UTILIZED: 33.7 > MAX_PCT_UTILIZED: 33.7 > PHYSICAL_VOLUMES: 2 > LOG_POOL_PAGES: 256 > LOG_POOL_PCT_UTIL: 0.12 > LOG_POOL_PCT_WAIT: 0.00 > CONSUMPTION_MB: 4281451.30 > CONSUMPTION_DATE: 2004-03-29 15:00:59.000000 > > _-'-_ > -|- > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Warren, Matthew (Retail) > Sent: Friday, January 14, 2005 2:35 PM > To: [email protected] > Subject: SELECT statement crashes server > > Hallo *SM'ers > > AIX 5.2.0.0 > TSM server 5.2.2.3 > > I have discovered a select command that will crash our server instantly > every time.. > > Could anyone confirm they get the same behaviour, or that it's just a > quirk of our site. > > I originally tried this; > > >select volume_name,pct_reclaim from (select * from volumes where > stgpool_name='UKS_NORM_PRIM') where pct_reclaim=>90 > > But TSM complains about the first '(' being an invalid token... It > shouldn't be. > > So, after confirming and doing succesfull sub-selects in other select > commands, I thought it may have something to do with the '>' being the > redirect symbol. So I wrapped part of the command in double-quotes > > When I try this command; > > >select "volume_name,pct_reclaim from ( select * from volumes where > stgpool_name='UKS_NORM_PRIM') where pct_reclaim=>90" > > The server instantly falls over..... > > Can anyone else repeat this? I have tried a couple of very simple select > commands with double quotes around them (none using '>' as yet) and > only the above select command has made the TSM server fall over so far.. > but my testing is far from comprehensive as yet. > > Have Fun! > > Thanks, > > > Matt. > _-'-_ > -|- > > > > > ___________________________ Disclaimer Notice __________________________ > This message and any attachments are confidential and should only be > read by those to whom they are addressed. If you are not the intended > recipient, please contact us, delete the message from your computer and > destroy any copies. Any distribution or copying without our prior > permission is prohibited. > > Internet communications are not always secure and therefore Powergen > Retail Limited does not accept legal responsibility for this message. > The recipient is responsible for verifying its authenticity before > acting on the contents. Any views or opinions presented are solely those > of the author and do not necessarily represent those of Powergen Retail > Limited. > > Registered addresses: > > Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, > CV4 8LG. > Registered in England and Wales No: 3407430 > > Telephone +44 (0) 2476 42 4000 > Fax +44 (0) 2476 42 5432 > > > > -------------------------------- > This e-mail may be privileged and/or confidential, and the sender does > not waive any related rights and obligations. Any distribution, use or > copying of this e-mail or the information it contains by other than an > intended recipient is unauthorized. If you received this e-mail in > error, please advise me (by return e-mail or otherwise) immediately. > > Ce courriel est confidentiel et protege. L'expediteur ne renonce pas aux > droits et obligations qui s'y rapportent. Toute diffusion, utilisation > ou copie de ce message ou des renseignements qu'il contient par une > personne autre que le (les) destinataire(s) designe(s) est interdite. Si > vous recevez ce courriel par erreur, veuillez m'en aviser immediatement, > par retour de courriel ou par un autre moyen. > ================================
