Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-05 Thread Zoltan Forray
Frankly, I think it has something to do with the 6.3.4.200 patches. All of my 6.3 servers are at 6.3.4.200 except for this one (HADES), which is at 6.3.4.000. I will schedule to upgrade to 6.3.4.300. The expires are kicked off at the same time on all servers. Naturally, reclaim then kicks in, s

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-05 Thread Michael Stahlberg
HI, Zoltan, we have the same problem. We opened also a case for this. The result was that the expire process and the reclamation process (in our case it was only the copy storage pool) should not run at the same time. We try to disable now the reclamation process if front of the expiration proces

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Andrew Raibeck
rote on 2014-02-03 16:04:01: > From: Zoltan Forray > To: ADSM-L@vm.marist.edu, > Date: 2014-02-03 16:06 > Subject: Re: Diagnosing ANR1439E Allocate prohibited - transaction failed. > Sent by: "ADSM: Dist Stor Manager" > > It is a library sharing session from the

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Zoltan Forray
r > Product Wiki: > https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli > +Storage+Manager/page/Home > > "ADSM: Dist Stor Manager" wrote on 2014-02-03 > 15:24:25: > > > From: Zoltan Forray > > To: ADSM-L@vm.marist.edu, > > Date: 2014-02-03 15

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Andrew Raibeck
/wikis/home/wiki/Tivoli +Storage+Manager/page/Home "ADSM: Dist Stor Manager" wrote on 2014-02-03 15:24:25: > From: Zoltan Forray > To: ADSM-L@vm.marist.edu, > Date: 2014-02-03 15:47 > Subject: Re: Diagnosing ANR1439E Allocate prohibited - transaction failed. > Sent by:

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Zoltan Forray
To clarify - the errors are on my HADES server. In these messages, SUN is the tape library / drive owning server. On Mon, Feb 3, 2014 at 3:24 PM, Zoltan Forray wrote: > The session seems to be for another server asking for a tape? > > 01/31/2014 12:05:15 ANR0408I Session 32595 started for ser

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Zoltan Forray
The session seems to be for another server asking for a tape? 01/31/2014 12:05:15 ANR0408I Session 32595 started for server SUN (Linux/x86_64) (Tcp/Ip) for library sharing. (SESSION: 32595, PROCESS: 169) 01/31/2014 12:05:15 ANR0409I Session 32595 en

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Zoltan Forray
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 wrote: > No session info: > > 1/31/2014 12:08:20 PM ANR1439E Allocate prohibited - trans

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Zoltan Forray
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 - transacti

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.\

2014-02-03 Thread Skylar Thompson
We've only run into this once, and it was with reclamation. I believe that was on v6.2, and we haven't seen it since. On Mon, Feb 03, 2014 at 02:50:42PM -0500, Andrew Raibeck wrote: > Hi Zoltan, > > If you query the actlog, does it show a session or process ID associated > with that message, e.g.:

Re: Diagnosing ANR1439E Allocate prohibited - transaction failed.

2014-02-03 Thread Andrew Raibeck
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