Becky-- you said BMC-- are you running SQL BackTrack?  If so, there is a known
memory leak problem with all the OBSI modules prior to 2.4.10.2.

SQL-BackTrack? OBSI Module for ADSM
Technical Bulletin

Version 2.4.10
August 16, 2000

*100033286*



Problem
BMC Software is alerting users of SQL-BackTrack OBSI Module for ADSM, all
versions on all
platforms, to a problem. This technical bulletin describes a patch for
SQL-BackTrack OBSI
Module for ADSM to prevent the problem from occurring.


There is a memory leak in the SQL-BackTrack OBSI Module for ADSM product. For
every 64k
block of data recovered, there is a loss of 8 bytes. Depending on the minimum
bytes allocated
by your memory management system, this could result in a greater loss for each
64k block of
data being recovered.


Solution
To fix this problem, download the patch from the BMC ftp site using the
following
instructions:



Connect to the ftp site:

ftp ftp.bmc.com



|--------+----------------------->
|        |          Tim Melly    |
|        |          <Tim.Melly.B@|
|        |          BAYER.COM>   |
|        |                       |
|        |          10/13/2000   |
|        |          07:11 AM     |
|        |          Please       |
|        |          respond to   |
|        |          "ADSM: Dist  |
|        |          Stor Manager"|
|        |                       |
|--------+----------------------->
  >------------------------------------------------------------|
  |                                                            |
  |       To:     [EMAIL PROTECTED]                         |
  |       cc:     (bcc: Lisa Cabanas/SC/MODOT)                 |
  |       Subject:     Re: periodic ADSM/TSM shutdown          |
  >------------------------------------------------------------|





Pat,

I'm running 3.1.2.40 on AIX 4.3.2 (yes, were upgrading shortly) and I've
encountered a similar problem. What happens is that after a DB backup the
recovery log is not reset to zero and will eventually fill up. The only way
around this problem is to halt the server and then restart. I talked to IBM
about this and it has been fixed in 3.1.2.58 and subsequent *SM versions. Were
planning to upgrade to TSM 4.1.1 shortly, so in the interim I'm living with it.

Tim Melly
Bayer Pharma




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/12/2000 08:03:23 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
cc:

Subject: Re: periodic ADSM/TSM shutdown

We have never seen any issues with long running ADSM servers
(note we're further down level than you are!):

tsm: DLADSM>q stat
ADSM Server for AIX-RS/6000 - Version 3, Release 1, Level 1.5


                                Server Name: DLADSM
              Server Installation Date/Time: 08/06/1996 17:18:36
                   Server Restart Date/Time: 05/21/2000 20:58:39
[...]


Folks who recommend periodic reboots and restarts are offering
solutions that simply mask or alleviate any problems that may
exist.


On Thu, 12 Oct 2000, Pat Wilson wrote:

>I've never seen any evidence that a periodic restart is needed.
>
>Pat Wilson
>Dartmouth College
>[EMAIL PROTECTED]
>
>
>>  I am running
>>  AIX 4.3.3 on an S80
>>  ADSM 3.1.2.40 (yes I know I am trying to get us to upgrade but you ever see
>>  anything move fast in corporate world?)
>>
>>  A couple of weeks ago I ran into a problem that the server couldn't
>>  successfully backup the database and my log file filled up...I solved it by
>>  cycling the ADSM server.  Then two days later BMC told us that we need to
>>  cycle the ADSM server on a regular basis.  What are everyone's thoughts on
>>  that?  I looked around and haven't seen any recommendations.
>>
>>  TIA
>>
>>  Becky Davidson
>>  Data Manager/AIX Administrator
>>  EDS/Earthgrains
>>  voice: 314-259-7589
>>  fax: 314-877-8589
>>  email: [EMAIL PROTECTED]
>
>

Reply via email to