To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
Hi TSM-ers!
Good news, my database inconsistencies are removed.
Just for future reference (although I doubt there are many more TSM 5.3
users out there) I will post here what I have been instructed by IBM
Support to
paces successfully.
Thank you all very much for your help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
km
Sent: vrijdag 21 augustus 2009 19:18
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohi
tility called the Repair Orphans Utility.
I will open a PMR and hope IBM will deliver the utility although my
server is out of support...
Thanks again!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
On 21/08, Loon, EJ van - SPLXM wrote:
> Hi KM!
>
> sho aggr 0 1086967169:
>
> AggrId: 0.1086967169, AggrSize: 0.717, LogSize: 0.717, NumFiles: 1.
> Aliases: None.
>
> I guess I have to parc the undeletable nodes somewhere until the TSM
> server is upgraded to a supported level...
> Kind regards,
>
Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
km
Sent: donderdag 20 augustus 2009 19:16
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
On 20/08, Loon, EJ van - SPLXM wrote:
> Hi KM!
> I already tried the delete object comma
On 20/08, Loon, EJ van - SPLXM wrote:
> Hi KM!
> I already tried the delete object command. In fact, the objectid is in
> the error itself:
>
> ANRD imutil.c(7001): ThreadId <51> unexpected rc=87 from bfDestroy
> for objId=0.106696510
>
> So when I issue a delete object 0 106696510 the same err
ic van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
km
Sent: woensdag 19 augustus 2009 19:57
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
On 19/08, Loon, EJ van - SPLXM wrote:
>
@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
One more thing. Are any of your database volumes marked stale or
offline? It could be possible that a bad DBMIRROR would cause this.
Gary
On Aug 19, 2009, at 2:33 PM, Clark, Margaret wrote:
> Did you try deleting by F
: woensdag 19 augustus 2009 21:33
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
Did you try deleting by FSID? Laborious, but it works when other
methods fail... e.g. (for filespace 1): DELETE FILESPACE KL10143J 1
NAMETYPE=FSID
- Margaret Clark
-Original Message
...@vm.marist.edu] On
Behalf Of
km
Sent: dinsdag 18 augustus 2009 18:34
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
On 18/08, Loon, EJ van - SPLXM wrote:
Hi TSM-ers!
I have two nodes which I cannot delete. When I issue a DELETE
FILESPACE
* for one of these node, I see the
[mailto:ads...@vm.marist.edu] On
Behalf Of Loon, EJ van - SPLXM
Sent: Wednesday, August 19, 2009 12:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Dealloc prohibited - transaction failed
I was hoping to be able to solve it myself, since the server is
running
an unsupported TSM level (5.3.4.0), so
: Wednesday, August 19, 2009 12:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Dealloc prohibited - transaction failed
I was hoping to be able to solve it myself, since the server is running
an unsupported TSM level (5.3.4.0), so I cannot open a PMR.
Thanks anyway.
Kind regards,
Eric van Loon
essage-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> km
> Sent: dinsdag 18 augustus 2009 18:34
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Dealloc prohibited - transaction failed
>
> On 18/08, Loon, EJ van - SPLXM wrote:
> > Hi TSM-ers!
> &g
Of
km
Sent: dinsdag 18 augustus 2009 18:34
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Dealloc prohibited - transaction failed
On 18/08, Loon, EJ van - SPLXM wrote:
> Hi TSM-ers!
> I have two nodes which I cannot delete. When I issue a DELETE
FILESPACE
> * for one of these node, I see the
> ANR0800I DELETE FILESPACE * for node KL10143J started as process 59041.
> ANR0802I DELETE FILESPACE * (backup/archive data) for node KL10143J
> started.
> ANRD ssalloc.c(1532): ThreadId <51> Dealloc prohibited - transaction
> failed.
> ANRD ThreadId <51> i
59041.
ANR0802I DELETE FILESPACE * (backup/archive data) for node KL10143J
started.
ANRD ssalloc.c(1532): ThreadId <51> Dealloc prohibited - transaction
failed.
ANRD ThreadId <51> issued message from:
ANRD ThreadId <51> 0x000100017f78 outDiagf
ANR
16 matches
Mail list logo
