Thanks Zoltan, – I somehow missed your earlier posting about this topic. I'll try to get my hands on the IT17642 article (why on earth does IBM show it only to "authorized" users? I hate this vendor BS.).
But in addition to slowness, it seems that EXPIRE INVENTORY NODE=* at least attempts to expire all nodes, unlike EXPIRE INVENTORY without the NODE or DOMAIN options. Have you seen this? On Thu, Nov 10, 2016, at 18:07, Zoltan Forray wrote: > Henrik, > > If you check recent posts here, you will see there is a major issue with > 6.3.6.000 server and expirations. I have been fighting it since I > upgrade > one server. IBM has a hotfix to address it or you can simply upgrade to > 7.1.6, which is what I did. You must contact IBM support for it. They > say > the impact has been minimal and hit-or-miss (not everyone who upgrades to > 6.3.6.000 has the problem) so an official patch has not been released so > far. > > Search Google for IT17642. > > On Thu, Nov 10, 2016 at 10:50 AM, Henrik Ahlgren <[email protected]> > wrote: > > > The documentation for EXPIRE INVENTORY command says "If you do not > > specify either NODE or DOMAIN with value, data for all nodes is > > processes". That is in fact how it works up to 6.3.6.100, but it seems > > that there is a bug in 6.3.6 that causes it to only expire a handful of > > randomly selected nodes, unless you specify "NODE=*". > > > > Have any of you run into this? If you're using 6.3.6, I would urge you > > to check the expire history, i.e. > > > > select date(start_time) as date,count(*) as nodes,sum(affected) as > > expired > > from summary > > where activity='EXPIRED' > > group by date(start_time) > > > > > > -- > *Zoltan Forray* > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator (in training) > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > [email protected] - 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
