![]() Some 6 months later in Dec 2010 I had a customer with six AIX servers running at 95% utilization and all from remote TEMS processing. That was probably the single most expensive PMR I ever worked on. The customer decided to recycle the affected remote TEMSes once a week. The conclusion was that a certain type of situation caused a severe storage fragmentation and a TEMS failure in 10-12 days. In 2008 I began work on a year-old customer problem that took until Spring 2010 to resolve. In addition, there may be important error messages in the diagnostic log. Situations are the most common workload but SOAP calls, historical data collection and Portal Client workspaces can be involved. ![]() This condition is usually caused by workloads, configuration or environmental conditions. In some cases, the TEMS experienced a steady storage growth and failure after some days. Version 2.34000 18 August 2021 John Alvord, IBM Corporation have been cases every year where a TEMS was running with high enough CPU/Storage resource usage that the customer was concerned.
0 Comments
Leave a Reply. |