Hi Zoltan, If you query the actlog, does it show a session or process ID associated with that message, e.g.:
02/03/2014 14:44:57 ANR1439E Allocate prohibited - transaction failed. (PROCESS: 1444) Review the activity log to see what else was going on around the time this occurred. When data is backed up or archived to the TSM server, the client sends a size "estimate" of the object, so the TSM server knows how much space to allocate. The regular backup-archive client should send exact sizes. API application behavior depends on the API application, but in practice the application should send an estimate that is as close as possible, if not exact, to the server. Slightly inaccurate estimates might not cause a problem, but odds of problems occurring increase as the inaccuracy of the estimate increases. On its face, that is what ANR1139E is talking about. However, it looks like this probably could potentially occur with other server operations such as reclamation. Hence the suggestion to look at the activity log to see if you can find context. Best regards, - Andy ____________________________________________________________________________ Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 2014-02-03 14:27:22: > From: Zoltan Forray <zfor...@vcu.edu> > To: ADSM-L@vm.marist.edu, > Date: 2014-02-03 14:29 > Subject: Diagnosing ANR1439E Allocate prohibited - transaction failed. > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > I am starting to get a lot of these messages: > > 1/31/2014 6:53:44 PM ANR1439E Allocate prohibited - transaction failed. > > on one of my TSM servers (my only RH Linux *6.3.4.000* server - other are > at 6.3.4.200 - not sure if there is a connection?). > > How can I figure out what / who is causing this? > > Last occurrence was 01/31/2014 from *12:08 PM* till *11:27 PM* - > 245-messages (in the middle of daily backup processing). The book doesn't > offer much help: > > *Explanation:* While attempting to preallocate storage on a storage pool, > the server detected that the transaction for this operation has previously > failed. This error may occur when a large file is selected for backup and > the client did not properly estimate the file size. There may not be enough > space in the storage pool for the file. > *System action:* An internal error is reported by the server and the > operation being performed is ended. *User response:* Examine error messages > that may have been displayed prior to this message for more information. > The only messages around these is the same error messages and normal backup > chatter. > > One thing I noticed with this last occurrence was that Inventory Expiration > was running when the first ANR1439E (12:08) message occurred but finished > at 12:13. > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html >
