Results 1 to 4 of 4
-
05-30-2012, 04:15 AM #1Member
- Join Date
- Jul 2004
- Location
- Belgium
- Posts
- 34
- Thanks
- 0
- Thanked 0 Times in 0 Posts
TDP for Domino : "Inactivate logs" ends with ANS0246E & ANS0266I
Hi,
We get next error during 'inactivate logs' on 2 of our 15 Domino clients using Archival logging
05/30/2012 09:22:47 ANS0246E Issue dsmEndTxn and then begin a new transaction session.
05/30/2012 09:22:47 ANS0266I The dsmEndTxn vote is ABORT, so check the reason field.
With the result that no logs ever are inactivated from our backup storage for those 2 Domino clients.
The domina log says there are 255 logs inactivated, but this is not true, nothing is inactivated
Current date is: wo 30/05/2012
Current time is: 09:22
IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 5, Level 3.0
(C) Copyright IBM Corporation 1999, 2010. All rights reserved.
ACD5221I The C:\Program Files\Tivoli\TSM\domino\dominasch.log log file has been pruned successfully.
Number of Logs Inactivated: 255
TDP for Domino version = 5.5.3.0 (we got the same error for 6.3.0.0)
Win OS = 2003
Domino = 8.5.2.3
API = 6.3.0.0
BA client = 6.3.0.0
TSM server = 5.5.5.0 (on Mainframe)
We get the same error on one other client :
TDP for Domino version = 6.3.0.0
Win OS = 2008
Domino = 8.5.2.3
API = 6.3.0.0
BA client = 6.2.1.03
Our other 13 domino clients using archiving logging have no problems.
Can anybody help us with this ?
-
05-30-2012, 05:04 AM #2Member
- Join Date
- Jul 2004
- Location
- Belgium
- Posts
- 34
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Forgotten to mention :
My guess is that it has something to do with a ' 255 limit/threshold '
On both clients the TSM log says always 'Number of logs inactivated 255' although there should be more logs to inactivate
and as I mentioned before there are no logs at all inactivated.
-
05-31-2012, 08:38 AM #3Member
- Join Date
- Jul 2004
- Location
- Belgium
- Posts
- 34
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Some extra info found in activity log :
MSG ANS0266I (RC2302) The dsmEndTxn vote is ABORT
MSG ANE4993E ACD5233 Data Protection for Domino: Inactivation of S0000255.TXN transaction log archive failed.
Extraction activity log :
05/31/2012 12:58:47 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5231 Data Protection for Domino: Starting inactivation of transaction log archives for server
XXXXXXX. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
MSG ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5235 Data Protection for Domino: Starting
inactivation of transaction log archive S0000000.TXN. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5234 Data Protection for Domino: Inactivation of S0000000.TXN transaction log archive succeeded.
- deleted similar lines as above -
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5235 Data Protection for Domino: Starting
inactivation of transaction log archive S0000254.TXN. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5234 Data Protection for Domino: Inactivation of
S0000254.TXN transaction log archive succeeded. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5235 Data Protection for Domino: Starting
inactivation of transaction log archive S0000255.TXN. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4993E (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5233 Data Protection for Domino: Inactivation of
S0000255.TXN transaction log archive failed. (SESSION: xxxxxxx)
05/31/2012 12:58:52 ANE4991I (Session: xxxxxxx, Node: nodename) TDP Domino
ACD5232 Data Protection for Domino: Ending inactivation
of transaction log archives for server XXXXXXX. There
were 255 transaction log archives inactivated. (SESSION:xxxxxxx)
05/31/2012 12:58:52 ANR0403I Session 475008 ended for node nodename (TDP Domino). (SESSION: xxxxxxx)
-
05-31-2012, 10:11 AM #4Member
- Join Date
- Jul 2004
- Location
- Belgium
- Posts
- 34
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Problem solved.
TXNGroupmax option for node increased to 2048
Was using the default value 256 (tsm server option)
Similar Threads
-
TDP for Domino "already in progress" message
By p305491 in forum TDP/Application Layer BackupReplies: 0Last Post: 09-14-2007, 12:47 PM -
Difference between "move data" & "move nodedata"?
By cheffern in forum Backup / Archive DiscussionReplies: 2Last Post: 12-11-2006, 09:30 AM -
TDP for SQL: Backups changing DB recovery mode from "normal" to "simple"?
By c.j.hund in forum TDP/Application Layer BackupReplies: 1Last Post: 09-12-2006, 04:29 AM -
inactivate logs in DOMINO stalled by active backups
By biduxe in forum TDP/Application Layer BackupReplies: 0Last Post: 06-06-2006, 07:56 AM -
TDP for Domino - "file being used be some1 else" errors
By Monkeh in forum TDP/Application Layer BackupReplies: 2Last Post: 09-08-2005, 07:27 AM


