ARSMAINT Error :SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT,Reason=1

[Jaydeep Mehta]

Hello Everyone ,

I am running the ARSMIANT Process and getting the below TSM Error.

SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=1, File=arssmsms.cpp, Line=412  Srvr->UNKNOWN CLIENT non-SSL<-
Cache Migration Failed: ApplGroup(stmt) Agid(5858) ObjName(11774FAA1) Date(15738) Server(XXXXXXXXX)
SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=41, File=arssmsms.cpp, Line=2074  Srvr->UNKNOWN CLIENT non-SSL<-
Cache Migration Failed: ApplGroup(IIS) Agid(6054) ObjName(14FAAA) Date(14427) Server(XXXXXXXXXXXX)
SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=2, File=arssmsms.cpp, Line=412  Srvr->UNKNOWN CLIENT non-SSL<-
Cache Migration Failed: ApplGroup(IIS) Agid(6054) ObjName(1FAAH) Date(14397) Server(XXXXXXXXXX)


I also Checked the IBM Link

http://www.ibm.com/support/knowledgecenter/SS36V9_3.1.0/com.ibm.itsm.msgs.client.doc/msg-ANS0266I.html?lang=en

But didn't get  Reason=1,  and  Reason=2 information.

Please Suggest it is Error or Just Information.

Should we go ahead with arsmaint process or not .


Thanks in Advance

Regards
Jaydeep Mehta

[Alessandro Perucchi]

Hello Jaydeep,

I have seen the following error in your example:

SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=41, File=arssmsms.cpp, Line=2074  Srvr->UNKNOWN CLIENT non-SSL<-

With error 41.

Reason 41 means you don't have enough mount point in TSM (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.msgs.client.doc/msg-0041_E.html)

Reason 1 means you need to check with your TSM admin (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.msgs.client.doc/msg-0001_E.html)

Reason 2 means No objects on server match query (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.msgs.client.doc/msg-0002_E.html)

So basically, the main error is "reason 41", and the two others are simply a consequence of the reason 41.

Do you use disk pool in TSM, or tapes?
If you use disk pool, then you must increase the mount point in TSM to at least 255. Any value less than 255 will give you, if you "stress" a little bit CMOD/TSM such error.
If could be more than 255, but 255 is the minimum recommended for CMOD with TSM with disk pools.

[Justin Derrick]

And if you have tapes or optical platters, it means the library was busy doing other things. 

-JD.

[Jaydeep Mehta]

Thanks  Alessandro  & JD...

we are using disk pool ,and we increased the TSM  mount point value  to 255.

so now we are not getting the Error with Reason=41 But still we are still getting Reason=1.

For Reason=1 we have Checked  the Activity Log and getting below error .

        DATE_TIME     MESSAGE           
------------------     ------------------
        2016-03-23     ANR0102E imutil.c-
   03:00:31.000000      (5264): Error 1 
                        inserting row in
                        table "Expiring.-
                        Objects".       
                        (SESSION: 2065) 
        2016-03-23     ANR0103E imutil.c-
   03:00:57.000000      (5303): Error 2 
                        updating row in 
                        table "Archive.O-
                        bjects".         
                        (SESSION: 2073) 
        2016-03-23     ANR0103E imutil.c-
   03:01:39.000000      (5303): Error 2 
                        updating row in 
                        table "Archive.O-
                        bjects".



How to fix this error .


Regards
JD

[Justin Derrick]

Looks like you have a database issue inside TSM. 

It could be as simple as being out of database space, or much, much worse.

Check on available database space with "query database".  Or check the filesystem assigned to TSM database storage.

You should be doing database backups regularly (and keeping them) to minimize any loss.

I'd be opening a PMR as a Sev 2 if this is your production system.

Good luck!

-JD.