ADSM-L

Re: [ADSM-L] Active log

2012-11-29 03:14:38
Subject: Re: [ADSM-L] Active log
From: Grigori Solonovitch <Grigori.Solonovitch AT AHLIUNITED DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 29 Nov 2012 11:06:13 +0300
I am not wrong there is only one way to release active logs - run full TSM 
database backup.......

Grigori G. Solonovitch
Senior Technical Architect  Ahli United Bank Kuwait  www.ahliunited.com.kw

Please consider the environment before printing this E-mail


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
duholm
Sent: Thursday, November 29, 2012 11:01 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Active log

Hi All

My TSM server have trouble commiting the Active log to the database. At the 
moment I have an active log at 55 GB, so I had to cancel all my tasks running, 
and it has not stop the log from growing.

So can anybody tell me, how I empty my Active log and what the normel 
bottlenecks are. My DB2 database and active logs are located on 7 200 GB SSD 
discs and I am running TSM ver 6.3.2.0. The CPU and RAM of the server are not 
used up nor are there any big disc queue lengths on any disc's.

Hope somebody can help my

Tanks
Bo

+----------------------------------------------------------------------
|This was sent by bdh AT itrelation DOT dk via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.

<Prev in Thread] Current Thread [Next in Thread>