ANR0299I A full database backup will be started. The
archive log space used is 99 % and the archive log space
used threshold is 80 percent. (PROCESS: 23)
This is continually happening, I have had this issue in the past but I don't
recall the resolution.
The prior backup that ran before that
What version of TSM?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Tuesday, August 26, 2014 10:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] tsm archive log full, causes repeated backups
ANR0299I A full database backup
I just went through this with a long running, single transaction, 350GB
Oracle TDP backup. The usual answer of doing a DB backup did nothing. When
I killed the backup session, the log went to 0. We contacted the user
about changing their config to split the Oracle backup into multiple chunks.
6.3.1
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, 26 August, 2014 10:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups
What version of TSM?
-Original
DOHYour There are no sessions or processes running part of the
message was hidden..
On Tue, Aug 26, 2014 at 11:09 AM, Tim Brown tbr...@cenhud.com wrote:
6.3.1
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
You could have a reorg running and pinning the log.
Try: q actlog begindate=today-2 search=reorg
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Tuesday, August 26, 2014 11:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L]
I had even restarted the tsm server today
If I enter with just =today it comes right back
If I enter with today-1 the query hangs
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, 26 August, 2014 11:16 AM
To:
That usually means your activity log is enormous! :)
But restarting the server would have killed any reorg or pinning transaction.
Try 2 db backups in a row now, your archive log should clear.
W
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
There have actually been 5 backups completed in a row since server was started
all with success! ?
All started due to ANR0299I A full database backup will be started. The
archive log space used is 99 % and the archive log space used threshold is 80
percent.
Tim
-Original Message-
[http://infonet.txfb-ins.com//images//email-signature-image.jpg]
WWW.TXFB-INS.COMhttp://www.txfb-ins.com
Cound something wrong with your archive log filesystem? Might it be unmounted
or something?
Rick
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Tuesday, August 26, 2014 12:13 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: tsm
Archive logs are in j:\tsm\archlog
Drive J is 250Gb total, free space just 386mb
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Rhodes, Richard L.
Sent: Tuesday, 26 August, 2014 12:26 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm
Since it appears that my archive log drive is full, I found the steps to follow
relocate to larger drive.
Create an new archive log directory.
Update the dsmserv.opt option file for the new archive log directory.
Halt and restart the server.
Move the archive logs from the old directory to the
Can you create the ARCHFAILOVERLOGDirectory?
That would give you additional space without moving your current files from
ARCHIVELOG to the new volume.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Tuesday, August 26, 2014
There is one on another drive that is full , OOPS C:
c:\tsmarchlogfailover
If I create a new one on a new drive x:\tsmarchlogfailover and update
dsmserv.opt
will it eventually free up the files on c:
never realized it was on C: to begin with, have had this environment for over 2
years
Or Is
I lean to your halt system, move folder approach.
Dangerous to have a full C: drive I suspect; Windows won't be happy trying to
do anything on a full boot disk.
You'll have better luck giving Windows room to do its work; while letting TSM
deal with the new x:\ path.
-Original
Thanks
Will try now
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 2:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups
I lean to
Almost, did all that TSM server starts and stops. Where is log indicating
failures
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 2:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re:
Server does not stay up!!
2014-08-26-14.37.09.781000 Instance:SERVER1 Node:000
PID:8188(db2syscs.exe) TID:12844 Appid:none
data protection services sqlpgArchiveLogFile Probe:3150
ADM1848W Failed to archive log file S0102568.LOG to
Your TSM service account has appropriate permissions on J:\tsm\
It looks like a failure to deal with a move/copy from I: to J:.
I've not looked at ADM1848W yet.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Tuesday,
I and J were there from before, I just added o:\tsmarchlogfailover and updated
its security
To be same as I and J
Still fails!
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 2:43
I don't find an ADM1848W message in TSM messages.
Anything in Windows Event Log?
Can you set the TSM service to not auto-start, boot the server, then login on
the console and try a foreground start of TSM?
You'd see the live log messages appear in that console window.
-Original
check the following:
- db2 recovery history retention. IIRC it should be set to 0 for TSM. In one
environment I used to manage a db2 DBA once decided to sanitize all db2
installations to a recovery history retention of 30 days… major pains. You’ll
have to do the google foo yourself, I don’t
23 matches
Mail list logo
