IBM Maximo consultant, geek, agile evangelist
OmniEasyDataArchiving+ is a data archiving solution for Maximo delivered by OMNINECS. Supports any Maximo environment: Maximo 7.6 or MAS 8, DB2/Oracle/SqlServer database, on-premise and cloud deployments. Predefined archiving templates to start as fast as possible.
Have you ever experienced a delay when entering data on a field and validation is triggered after several seconds? The asyncronous data validation has been introduced in Maximo 7.5 to improve responsiveness of the user interface. However there are some situations where this is really annoying. For example, if you have developed your own scripts […]
Today I had to face an issue deleting a large set of records from a Maximo table using an automation script. My script was something like this. mboSet = MXServer.getMXServer().getMboSet(“MYTABLE”, mbo.getUserInfo())mboSet.deleteAll()mboSet.save() Unfortunately the table I had to purge (MYTABLE in the example) was having more than 5000 rows so when I launched the script I […]
We all know Maximo is a complex product. It has plenty of features and is very flexible but sometimes complex to manage especially when system performances are poor.A lot of things may affect the perceived performances of Maximo and it may be hard to have an overview of the entire system configuration. What are the […]
Maximo and other IBM service management products based on TPAE (like SmartCloud Control Desk) can be seen as sitting at the apex of a pyramid that consists of network, hardware, and software services. As you can see, network performance are the foundation of the pyramid.The simplest way of measuring network performances and speed is the […]
During a performance assessment of a production customer environment I have set the mxe.db.logSQLTimeLimit system property to 2000 to log all long-running SQL statements (see this TechNote for details). Looking at the system logs I have noticed many entries like this. select * from doclinks where (ownertable=’WORKORDER’ and ownerid=1065680) or (ownertable=’WORKORDER’ and ownerid in (select […]
My job brings me across Europe to meet many different customers and work with a vast variety of Maximo environments. One of the most important tasks is to be able to quickly assess a Maximo environment that I have never seen before. How much data? One of the tools I use is a set of […]
I this article I have explained how to list the larger database tables and indexes on Oracle.On DB2 you can use the following one. SELECT name, card, npages, fpages, stats_timeFROM sysibm.systablesWHERE creator = ‘MAXIMO’ AND type=’T’ORDER BY card DESC; The returned columns are: NAME: Name of the table CARD: Number of rows NPAGES: Total number of pages […]
When you have to assess the system performance of a Maximo server it may be useful to have a quickly see what are the larger database tables and indexes. This can quickly spot some performance issues in your system.Large tables generates heavy database I/O workloads when are nor accesses through an index. Large indexes are also inefficient. Creating indexes with too […]
Maximo Activity Dashboard (also known as MAD or PerfMon) is a useful tool to analyze and troubleshoot Maximo performances and is available starting from TPAE 7.1.1.6. This great tool tracks execution times for each browser request (user-click) including the time spent querying DB with a great detail about executed queries and time spent for each sub-step […]