On second thought - ignore. The first place I got the message from stripped off the SESSION info. I am looking into the session info, now. Sorry for the DOH!
On Mon, Feb 3, 2014 at 3:16 PM, Zoltan Forray <zfor...@vcu.edu> wrote: > No session info: > > 1/31/2014 12:08:20 PM ANR1439E Allocate prohibited - transaction failed. > 1/31/2014 12:09:14 PM ANR1439E Allocate prohibited - transaction failed. > 1/31/2014 12:10:10 PM ANR1439E Allocate prohibited - transaction failed. > 1/31/2014 12:10:56 PM ANR1439E Allocate prohibited - transaction failed. > > Here is around the time of the first message: > > 01/31/2014 12:08:12 ANR0166I Inventory file expiration finished > processing for > node SOMRS1-VM, filespace > SOMRS1\SystemState\NULL\System > State\SystemState, copygroup BACKUP and object type > GROUP > BASE with processing statistics: examined 97356, > deleted > 97356, retrying 0, and failed 0. (SESSION: 32587, > > PROCESS: 168) > > 01/31/2014 12:08:12 ANR0165I Inventory file expiration started processing > for > node SOMRS1-VM, filespace > SOMRS1\SystemState\NULL\System > State\SystemState, copygroup BACKUP and object type > LOCAL > DATA CONTAINER. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:12 ANR0166I Inventory file expiration finished > processing for > node SOMRS1-VM, filespace > SOMRS1\SystemState\NULL\System > State\SystemState, copygroup BACKUP and object type > LOCAL > DATA CONTAINER with processing statistics: examined > 9, > deleted 9, retrying 0, and failed 0. (SESSION: > 32587, > PROCESS: 168) > > 01/31/2014 12:08:13 ANR0165I Inventory file expiration started processing > for > node SOMRS1-VM, filespace \\somrs1\e$, copygroup > BACKUP > and object type DIRECTORY. (SESSION: 32587, PROCESS: > 168) > 01/31/2014 12:08:13 ANR0166I Inventory file expiration finished > processing for > node SOMRS1-VM, filespace \\somrs1\e$, copygroup > BACKUP > and object type DIRECTORY with processing > statistics: > examined 2, deleted 2, retrying 0, and failed 0. > > (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:16 ANR0166I Inventory file expiration finished > processing for > node RECSAPPVM, filespace > RECSAPPVM\SystemState\NULL\Sys- > tem State\SystemState, copygroup BACKUP and object > type > GROUP BASE with processing statistics: examined > 110210, > deleted 110210, retrying 0, and failed 0. (SESSION: > > 32587, PROCESS: 168) > > 01/31/2014 12:08:17 ANR0165I Inventory file expiration started processing > for > node PORTALDB2.VCU.EDU, filespace /boot, copygroup > BACKUP > and object type DIRECTORY. (SESSION: 32587, > PROCESS: 168) > 01/31/2014 12:08:17 ANR0165I Inventory file expiration started processing > for > node SOMRS1-VM, filespace \\somrs1\c$, copygroup > BACKUP > and object type FILE. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:17 ANR0166I Inventory file expiration finished > processing for > node PORTALDB2.VCU.EDU, filespace /boot, copygroup > BACKUP > and object type DIRECTORY with processing > statistics: > examined 1, deleted 1, retrying 0, and failed 0. > > (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:19 ANR0165I Inventory file expiration started processing > for > node PORTALDB2.VCU.EDU, filespace /, copygroup > BACKUP and > object type FILE. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:20 ANR0166I Inventory file expiration finished > processing for > node SOMRS1-VM, filespace \\somrs1\c$, copygroup > BACKUP > and object type FILE with processing statistics: > examined > 30, deleted 30, retrying 0, and failed 0. (SESSION: > > 32587, PROCESS: 168) > > 01/31/2014 12:08:20 ANR0165I Inventory file expiration started processing > for > node SOMRS1-VM, filespace \\somrs1\c$, copygroup > BACKUP > and object type DIRECTORY. (SESSION: 32587, PROCESS: > 168) > 01/31/2014 12:08:20 ANR0166I Inventory file expiration finished > processing for > node SOMRS1-VM, filespace \\somrs1\c$, copygroup > BACKUP > and object type DIRECTORY with processing > statistics: > examined 32, deleted 32, retrying 0, and failed 0. > > (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:20 ANR0166I Inventory file expiration finished > processing for > node PORTALDB2.VCU.EDU, filespace /, copygroup > BACKUP and > object type FILE with processing statistics: > examined 86, > deleted 86, retrying 0, and failed 0. (SESSION: > 32587, > PROCESS: 168) > > 01/31/2014 12:08:20 ANR0165I Inventory file expiration started processing > for > node PORTALDB2.VCU.EDU, filespace /, copygroup > BACKUP and > object type DIRECTORY. (SESSION: 32587, PROCESS: > 168) > 01/31/2014 12:08:20 ANR0166I Inventory file expiration finished > processing for > node PORTALDB2.VCU.EDU, filespace /, copygroup > BACKUP and > object type DIRECTORY with processing statistics: > > examined 1, deleted 1, retrying 0, and failed 0. > > (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:20 ANR0165I Inventory file expiration started processing > for > node PORTALDB2.VCU.EDU, filespace /u01, copygroup > BACKUP > and object type FILE. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:20 ANR0166I Inventory file expiration finished > processing for > node PORTALDB2.VCU.EDU, filespace /u01, copygroup > BACKUP > and object type FILE with processing statistics: > examined > 1, deleted 1, retrying 0, and failed 0. (SESSION: > 32587, > PROCESS: 168) > > 01/31/2014 12:08:20 ANR0165I Inventory file expiration started processing > for > node SOMWORLDPOINT.ADM.ADP.VCU.EDU, filespace > > \\somworldpoint\c$, copygroup BACKUP and object type > > FILE. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:21 ANR0166I Inventory file expiration finished > processing for > node SOMWORLDPOINT.ADM.ADP.VCU.EDU, filespace > > \\somworldpoint\c$, copygroup BACKUP and object type > FILE > with processing statistics: examined 49, deleted 49, > > retrying 0, and failed 0. (SESSION: 32587, PROCESS: > 168) > 01/31/2014 12:08:21 ANR0165I Inventory file expiration started processing > for > node SOMWORLDPOINT.ADM.ADP.VCU.EDU, filespace > > \\somworldpoint\c$, copygroup BACKUP and object type > > DIRECTORY. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:21 ANR0166I Inventory file expiration finished > processing for > node SOMWORLDPOINT.ADM.ADP.VCU.EDU, filespace > > \\somworldpoint\c$, copygroup BACKUP and object type > > DIRECTORY with processing statistics: examined 35, > > deleted 35, retrying 0, and failed 0. (SESSION: > 32587, > PROCESS: 168) > > 01/31/2014 12:08:22 ANR0165I Inventory file expiration started processing > for > node SOMWORLDPOINT.ADM.ADP.VCU.EDU, filespace > > SOMWORLDPOINT\SystemState\NULL\System > State\SystemState, > copygroup BACKUP and object type GROUP BASE. > (SESSION: > 32587, PROCESS: 168) > > 01/31/2014 12:08:22 ANR0165I Inventory file expiration started processing > for > node ACADNT3.UC.ADP.VCU.EDU, filespace > > ACADNT3\SystemState\NULL\System State\SystemState, > > copygroup BACKUP and object type GROUP BASE. > (SESSION: > 32587, PROCESS: 168) > > 01/31/2014 12:08:25 ANR0166I Inventory file expiration finished > processing for > node MAGIDATA, filespace > MAGIDATA\SystemState\NULL\System > State\SystemState, copygroup BACKUP and object type > GROUP > BASE with processing statistics: examined 98161, > deleted > 98161, retrying 0, and failed 0. (SESSION: 32587, > > PROCESS: 168) > > 01/31/2014 12:08:25 ANR0165I Inventory file expiration started processing > for > node MAGIDATA, filespace \\magidata\d$, copygroup > BACKUP > and object type DIRECTORY. (SESSION: 32587, PROCESS: > 168) > 01/31/2014 12:08:25 ANR0166I Inventory file expiration finished > processing for > node MAGIDATA, filespace \\magidata\d$, copygroup > BACKUP > and object type DIRECTORY with processing > statistics: > examined 2, deleted 2, retrying 0, and failed 0. > > (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:26 ANR0165I Inventory file expiration started processing > for > node MAGIDATA, filespace \\magidata\c$, copygroup > BACKUP > and object type FILE. (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:26 ANR0166I Inventory file expiration finished > processing for > node MAGIDATA, filespace \\magidata\c$, copygroup > BACKUP > and object type FILE with processing statistics: > examined > 12, deleted 12, retrying 0, and failed 0. (SESSION: > > 32587, PROCESS: 168) > > 01/31/2014 12:08:26 ANR0165I Inventory file expiration started processing > for > node MAGIDATA, filespace \\magidata\c$, copygroup > BACKUP > and object type DIRECTORY. (SESSION: 32587, PROCESS: > 168) > 01/31/2014 12:08:26 ANR0166I Inventory file expiration finished > processing for > node MAGIDATA, filespace \\magidata\c$, copygroup > BACKUP > and object type DIRECTORY with processing > statistics: > examined 12, deleted 12, retrying 0, and failed 0. > > (SESSION: 32587, PROCESS: 168) > > 01/31/2014 12:08:26 ANR0165I Inventory file expiration started processing > for > node CREATIVESVS2, filespace > > CREATIVESVS2\SystemState\NULL\System > State\SystemState, > copygroup BACKUP and object type GROUP BASE. > (SESSION: > 32587, PROCESS: 168) > > 01/31/2014 12:08:35 ANR0406I Session 32603 started for node > ADM138.VCU.EDU > (WinNT) (Tcp/Ip 192.168.21.101(1845)). (SESSION: > 32603) > 01/31/2014 12:08:35 ANR0403I Session 32603 ended for node ADM138.VCU.EDU > (WinNT). (SESSION: 32603) > > 01/31/2014 12:08:43 ANR1439E Allocate prohibited - transaction failed. > > (SESSION: 32595, PROCESS: 169) > > > > > > On Mon, Feb 3, 2014 at 2:50 PM, Andrew Raibeck <stor...@us.ibm.com> wrote: > >> 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<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<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 >> > >> > > > > -- > *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 > -- *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
