I imported over 200000 (closed) tickets in Maximo.
Now Maximo is really slow.
CPU and memory usage are still very well not over 30%.
Default query for ticket app is to show only open but still working with application is to slow.
Do someone have experience working with large number of tickets in the system and slow performance?
What to do to make it faster?
I will really appreciate some help.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
5 replies Latest Post - 2012-10-03T16:42:26Z by SystemAdmin
Pinned topic MAXIMO too slow after importing large number of tickets
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-03T16:42:26Z at 2012-10-03T16:42:26Z by SystemAdmin
gulfsoft 1000008G2Y65 PostsACCEPTED ANSWER
Re: MAXIMO too slow after importing large number of tickets2012-09-27T08:23:44Z in response to VeljkoCGoogle "Maximo database tuning" to get links on tuning your database, depending on which DB and version you're using.
We can make Tivoli software work for you!www.gulfsoft.com
bportaluri 120000GS1X60 PostsACCEPTED ANSWER
Re: MAXIMO too slow after importing large number of tickets2012-09-27T15:37:18Z in response to VeljkoCLots of useful information in the Maximo IBM Wiki.
200000 (closed) tickets are not too many. I have seen few millions of work orders in Maximo environments working quite well.
If CPU consumption on the app server is not high the problem should be in the DB.
Keep in mind that you have to monitor each CPU core separately. Java cannot split the CPU workload across multiple cores for each user request. If you have a 4-core CPU and there is only one user connected you will never see CPU consumption higher than 25% (apart from background cron tasks and escalations).
VeljkoC 270003YA7D82 PostsACCEPTED ANSWER
Re: MAXIMO too slow after importing large number of tickets2012-09-28T09:26:32Z in response to bportaluriBruno thanks for reply so what is your suggestions for database tuning?
I only found this.
I set them on ON.
Also I found this but my parameters are similar set as in link.
So do you please know some concrete more tuning stuff which I can do on database?
You are probably right it is problem with database because in DBVisualizer every time I want to connect to database it takes up to long 10 seconds (while in some other environments it takes only 1 second)
Thank you very much
swkim90049 270004FKBD278 PostsACCEPTED ANSWER
Re: MAXIMO too slow after importing large number of tickets2012-10-01T23:08:55Z in response to VeljkoCLook at http://www-01.ibm.com/support/docview.wss?uid=swg21291250
When you review your maximo.log, you can possibly see which queries are taking a long time.
I'm not familiar with DB2, but you may want to review the query and if it is utilizing the current indexes optimally. If you have customer queries, you may see benefit from creating a new index... although when you update records, all indexes have to be touched during the update which is a performance lag.
SystemAdmin 110000D4XK5842 PostsACCEPTED ANSWER
Re: MAXIMO too slow after importing large number of tickets2012-10-03T16:42:26Z in response to VeljkoCYou might also want to check out the best practices for performance white papers that are available for download. They have information related to tuning the database as well as maintaining it for best performance.
The version for Maximo 7.1.1.x releases is located at:
And the version for Maximo 7.5.x releases is located at: