OnDemand User Group

Support Forums => MP Server => Topic started by: pankaj.puranik on February 05, 2013, 02:23:42 AM

Title: Storage object issue.
Post by: pankaj.puranik on February 05, 2013, 02:23:42 AM

Hi

I get the following  error while loading data into CMOD.
Iam using the default storage object size of 10 mb and compressed object size of 100k

arsload: Processing file >00012462.aa<
arsload: Load Version <8.5.0.5> Operating System <AIX> <6.1>
arsload: Server Version <8.5.0.5> Operating System <AIX> <6.1> Database <DB2> <09.07.0005>
arsload: 02/05/13 00:57:27 -- Loading started, 74385 bytes to process
Resource 00012462.aa.res will be added as resource >2998-3-0<.  Compression Type(Disable) Original Size(452288) Compressed Size(452288)
The field name 'PageNumber' found in the index file does not match any expected fields.  The field will be ignored.
The field name 'DocType' found in the index file does not match any expected fields.  The field will be ignored.
The field name 'RunType' found in the index file does not match any expected fields.  The field will be ignored.
OnDemand Load Id = >5099-3-0-2990FAA-14610-14610<
An error occurred.  Contact your system administrator and/or consult the System Log.  File=arsadmp.c, Line=1191
Unable to store the object >2990FAA1<.  Object size 593Loaded 10 rows into the database
arsload: 02/05/13 00:57:33 Loading failed
arsload: Processing failed for file >00012462.aa<
arsload: 02/05/13 00:57:33 -- Unloading started
OnDemand UnLoad Successful - LoadId(5099-3-0-2990FAA-14610-14610) Rows Deleted(10)
 
02/05/13 00:57:39 -- Unloading of data was successful

Title: Re: Storage object issue.
Post by: Justin Derrick on February 05, 2013, 06:23:13 AM

Check the System Log for error messages around the same time.

Also check the TSM activity log for any errors.

Report back and let us know what you find.

Also, is there a reason you're not compressing resources? 

-JD.

Title: Re: Storage object issue.
Post by: pankaj.puranik on February 05, 2013, 06:25:26 AM

Hi JD

With PDF indexer, i do not see an option to compress resource file.
Is there any other way I can tell CMOD to compress the .res file.

Thanks
Pankaj.

Title: Re: Storage object issue.
Post by: pankaj.puranik on February 05, 2013, 06:26:33 AM

And here is what I see in the System Log.

SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=41, File=arssmsms.cpp, Line=1455  Srvr->cmodhudbp1.nam.nsroot.net 169.171.135.117 non-SSL<-

Title: Re: Storage object issue.
Post by: Alessandro Perucchi on February 05, 2013, 08:37:19 AM

Hello Pankaj,

if I'm not wrong this is the signification of the Reason=49:

DSM_RC_ABORT_INVALID_DATA_FORMATA target storage pool does not have the correct data format for the given node type.

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmm.doc/anrcmsg9658.htm (http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmm.doc/anrcmsg9658.htm)

Quick and stupid question, are you trying to mix TSM node from a Windows and a Unix CMOD?

Maybe you should check with your TSM admin... seem quite strange...

Sincerely yours,
Alessandro

Title: Re: Storage object issue.
Post by: pankaj.puranik on February 08, 2013, 12:18:13 AM

Here's the reply on PMR.
I don't understand this well so I have forwarded this to the TSM admin.
Just for everyone's benefit here's the update on PMR.

SM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=41, File=arssmsms.cpp,  Line=1455  Srvr->cmodhudbp1.nam.nsroot.net 169.171.135.117 non-SSL<- 
ANS0266I means:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmm.doc_5.4/anrcms585316.htm
ANS0266I
The dsmEndTxn vote is ABORT, so check the reason field.
Explanation:
After a dsmEndTxn call, the transaction is aborted by either the server or client with a DSM_VOTE_ABORT and the reason is returned.
System action:
The system returns to the calling procedure.
User response:
Check the reason field for the code which explains why the transactionhas been aborted.
 
Reason=41 means that the TSM Client (OnDemand) was attempting to use more mountpoints for a backup or archive (archive in your case) operation than permitted by the server: see "0041 E: DSM_RC_ABORT_EXCEED_MAX_MP This node has exceeded its maximum number of mount points." at http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmm.doc_5.4/anrcms589408.htm
 
To correct, this, have your TSM administrator run QUERY NODE nodename FORMAT=DETAILED to determine the maximum allowed mountpoints for the node. You may need to use UPDATE NODE to increase this value.
 
Please let me know if this information is sufficient to resolve your issue. If not, please let me know and I will engage TSM support.

Title: Re: Storage object issue.
Post by: Alessandro Perucchi on February 11, 2013, 12:42:18 AM

Ooops... I think I was drunk :-) I misread reason=41 and reason=49 !!

Sorry <.,.>