To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Error There is insufficient recovery log space to
complete the database transaction
Follow the Admin Guide manual to perform an Extend Log operation, as a
command within a TSM server session, if you can get in, else as a
stand-alone operation. You
Good Morning
I have an old TSM server running 4.1.1 on a AIX 4.3 server.
When I tried to logon this morning I'm receiving an error
Insufficient recovery log spaceThere is insufficient recovery log
space to complete the database transaction
What's the best way to recovery from
-L] Error There is insufficient recovery log
space to complete the database transaction
To: ADSM-L@VM.MARIST.EDU
Good Morning
I have an old TSM server running 4.1.1 on a AIX 4.3 server.
When I tried to logon this morning I'm receiving an error
Insufficient recovery log space
:[EMAIL PROTECTED] On Behalf Of
Fred Johanson
Sent: Saturday, October 15, 2005 7:06 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Error There is insufficient recovery log space to
complete the database transaction
Yes. If you have not hit the max size for version 4, then format and
allo9cate
Follow the Admin Guide manual to perform an Extend Log operation, as
a command within a TSM server session, if you can get in, else as a
stand-alone operation. You need to to through the usual formatting
procedure if the log volume is an OS file, but not if it is a raw
logical volume.
I am getting a message of
The server does not have enough recovery log space to continue the current operation
Unable to establish session with server
when trying to log into the manager console.
Anyone know how what I can do to fix this?
Jacque
if the TSM server crashes because of lack of Recovery Log
Space. First format the volume, let's say you need 500 meg of Recovery log
Space to be added. To format the 500 meg volume type in the following:
# dsmfmt -log /path_of_tsm_logs/additional_log_name 500 ENTER
When that has been completed and you
Your TSM Server is not running because it has run out of recovery log space. You need
to define a log volume and extend the log volume(emergency extend) to start the Server.
So use the dsmfmt command to format a new log volume and then use the dsmserv extend
log command to extend the log
- ) )-,_. ,\ ( `'-'
St. Louis, Missouri '---''(_/--' `-'\_)
Cat Pics: http://andyc.dyndns.org/animal.html
On Wed, 30 Oct 2002, Rajesh Oak wrote:
Your TSM Server is not running because it has run out of recovery log space. You
need to define a log volume and extend the log volume
is not running because it has run out of recovery log space. You
need to define a log volume and extend the log volume(emergency extend) to start the
Server.
So use the dsmfmt command to format a new log volume and then use the dsmserv
extend log command to extend the log (possible in 4.2.x version
, IBM [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 24, 2002 8:23 AM
To: [EMAIL PROTECTED]
Subject: Recovery log space problem
Hi
We have TSM server 3.7.0 with TDP for Informix 3.7. Yesterday we got
following warning messages (blue font).
06/23/02 04:06:43 ANR0314W Recovery log usage exceeds 90
]
Subject: Re: Recovery log space problem
Hi.
The log gets filled up all the time.
When you backup the TSM database, it gets empty.
So, you should define a backup trigger for the database ( Admin Guide )
and consider increasing the size of the log in case it gets filled up too
soon.
Ran
for the first time since last two years. Do you see still increasing size is
recommended
Thanks regards
Sachin
-Original Message-
From: Bill Boyer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 11:54 PM
To: [EMAIL PROTECTED]
Subject:Re: Recovery log space
Hi
We have TSM server 3.7.0 with TDP for Informix 3.7. Yesterday we got
following warning messages (blue font).
06/23/02 04:06:43 ANR0314W Recovery log usage exceeds 90 % of its
assigned
capacity.
06/23/02 04:06:51 ANR0314W Recovery log usage exceeds 92 % of its
The maximum size of the recovery log is 5.5GB, my recovery log is 4.5 GB
now and I have just recently increased it 1GB from 3.5GB. It filled up
again last night. My database is 59.5 GB. Could I have a problem that is
causing my recovery log to fill up or is this normal for this size of
]@VM.MARIST.EDU - 04/10/2001 13:46
Veuillez répondre à [EMAIL PROTECTED]
Envoyé par : [EMAIL PROTECTED]
Pour :ADSM-L
cc :
ccc :
Objet : Recovery log space spikes
The maximum size of the recovery log is 5.5GB, my recovery log is 4.5 GB
now and I have just recently increased it 1GB from
.
Ronald Bazuin
-Original Message-
From: David Browne. [mailto:[EMAIL PROTECTED]]
Sent: donderdag 4 oktober 2001 13:46
To: [EMAIL PROTECTED]
Subject: Recovery log space spikes
The maximum size of the recovery log is 5.5GB, my recovery log is 4.5 GB
now and I have just recently increased it 1GB
: Recovery log space spikes
The maximum size of the recovery log is 5.5GB, my recovery log is 4.5 GB
now and I have just recently increased it 1GB from 3.5GB. It filled up
again last night. My database is 59.5 GB. Could I have a problem that
is
causing my recovery log to fill up or is this normal
-
From: Joshua S. Bassi [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, October 04, 2001 9:48 AM
To: [EMAIL PROTECTED]
Subject:Re: Recovery log space spikes
Are you using roll forward recovery? From what you are saying it
appears so. I would
Alain Gourves [EMAIL PROTECTED]@VM.MARIST.EDU on 2001-10-04
05:32:36
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Réf. : Recovery log space spikes
Hi,
Be carefull about the max log size
- Version 3, Release 7, Level 2.15
(C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved.
Enter your user id: x
ANS1316E The server does not have enough recovery log space to
continue the current operation
ANS8023E Unable to establish session with server.
ANS8002I Highest return code
I am running TSM on AIX 4.3. Most of the suggestions I have seen
for correcting a recovery log issue involve having access to TSM.
Unfortunately I don't have any access. Does anyone have and suggestions?
Jon - Contact your TSM administrator to have that person address it.
And
zprva-
Od: Martin, Jon R. [SMTP:[EMAIL PROTECTED]]
Odeslno: 12. ervna 2001 15:05
Komu: [EMAIL PROTECTED]
Pedmt: Recovery Log Space
Good Morning,
I am running TSM on AIX 4.3. Most of the suggestions I have seen
for correcting a recovery log issue involve having access
:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 3:05 PM
To: [EMAIL PROTECTED]
Subject: Recovery Log Space
Good Morning,
I am running TSM on AIX 4.3. Most of the suggestions I have seen
for correcting a recovery log issue involve having access to TSM.
Unfortunately I don't
How can u increase without admin access?
If u get access ,still u need to increase log space .
p.b
-Original Message-
From: Martin, Jon R. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 8:05 AM
To: [EMAIL PROTECTED]
Subject: Recovery Log Space
Good Morning,
I am
Wolkerstorfer
[EMAIL PROTECTED] (Martin. Jon R.) am 12.06.2001 15:04:36
Bitte antworten an [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT)
Thema:Recovery Log Space
Good Morning,
I am running TSM on AIX 4.3. Most
-Original Message-
From: PINNI, BALANAND (SBCSI) [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 8:48 AM
To: [EMAIL PROTECTED]
Subject:Re: Recovery Log Space
Importance: Low
How can u increase without admin access
PROTECTED]
To: [EMAIL PROTECTED]
cc:(bcc: Stan Vernaillen/BE/CCE)
Subject: Re: Recovery Log Space
Hi Joe,
your Recocery log is full, you cannot make any action, I have the same
problem a few weeks ago. Stop TSM server and restart it and recovery log
becomes empty. Then you should set
28 matches
Mail list logo
