Re: [ADSM-L] AW: EXPIRE INVENTORY problem
2015-05-06 12:28:38
Thanks for advice Michael and Rick.
The process is still in "cancel in progress" state, over two hours since
"cancelled."
Normally expire takes only about 60 minutes.
I've opened a PMR with IBM for advice.
I'll update the group when we've resolved the issue.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Michael malitz
Sent: Wednesday, May 06, 2015 10:17 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] AW: EXPIRE INVENTORY problem
Hallo Harold,
you should use the command "cancel expiration" instead of "cancel process".
With cancel expiration you have "checkpointing" at transaction boundaries.
Rgds Michael Malitz
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag
von Rick Harderwijk
Gesendet: Mittwoch, 6. Mai 2015 16:44
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: EXPIRE INVENTORY problem
If you cancel an expiration, does it not log every transaction, so that when
you cancel, it effectively does a rollback on all the entries in the database?
That might take some time as well...
On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS] < Harold.Vandeventer
AT ks DOT gov> wrote:
> I'm running TSM 6.3.4.300 on Windows.
>
> I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40
> WAIT=YES.
>
> It was still running over 2 hours after start.
>
> I issued a CANCEL PRO and it's been in "cancel in progress" for over
> 30 minutes.
>
> During all this time, Q PRO is reporting a constant number of nodes
> processed, objects examined and objects deleted.
>
> Database and log space look fine, Health Monitor via the AdminCenter
> GUI looks fine.
>
> What's happening in that process that would cause this behavior?
>
> ------------------------------------------------------------
> Harold Vandeventer
> Systems Programmer
> State of Kansas - Office of Information Technology Services STE 751-S
> 910 SW Jackson
> (785) 296-0631
>
>
> [Confidentiality notice:]
> **********************************************************************
> * This e-mail message, including attachments, if any, is intended for
> the person or entity to which it is addressed and may contain
> confidential or privileged information. Any unauthorized review, use,
> or disclosure is prohibited. If you are not the intended recipient,
> please contact the sender and destroy the original message, including
> all copies, Thank you.
> **********************************************************************
> *
>
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [ADSM-L] EXPIRE INVENTORY problem, Vandeventer, Harold [OITS]
- Re: [ADSM-L] EXPIRE INVENTORY problem, Rick Harderwijk
- [ADSM-L] AW: EXPIRE INVENTORY problem, Michael malitz
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem,
Vandeventer, Harold [OITS] <=
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem, Vandeventer, Harold [OITS]
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem, Vandeventer, Harold [OITS]
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem, Jeanne Bruno
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem, Erwann SIMON
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem, Jeanne Bruno
- Re: [ADSM-L] AW: EXPIRE INVENTORY problem, Erwann SIMON
|
|
|