This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi, we are currently on Maximo 6.2.8
One of the supervisors in Work Order Tracking selected the All Records (above All Bookmarks). We have 3 million rows in workorder tracking.
This the warning that shows up in the log:
15 Aug 2013 13:14:40:981 [WARN] USER = (XXXXXXX) SPID = (166) app (WOTRACK) object (WORKORDER) :select * from workorder where (siteid = 'FAC') order by wonum desc (execution took 314893 milliseconds)
Is there a way to prevent this?
I was thinking perhaps I could remove the All Records from Work Order Tracking?
Or perhaps trying mxe.db.fetchResultStopLimit although the tech note says it is for Maximo 7.1 and above:
http://www-01.ibm.com/support/docview.wss?uid=swg21412865
Any suggestions or thoughts on this matter? Trying to keep the application and database running without these type of runaway queries.
I believe you are on the right path thinking in terms of fetchResultStopLimit. There could be something similar in your version or you could think of an archiving purging strategy to another instance
--- In MAXIMO@yahoogroups.com, "sunk818" <swkim@...> wrote:
>
> Hi, we are currently on Maximo 6.2.8
>
> One of the supervisors in Work Order Tracking selected the All Records (above All Bookmarks). We have 3 million rows in workorder tracking.
>
> This the warning that shows up in the log:
>
> 15 Aug 2013 13:14:40:981 [WARN] USER = (XXXXXXX) SPID = (166) app (WOTRACK) object (WORKORDER) :select * from workorder where (siteid = 'FAC') order by wonum desc (execution took 314893 milliseconds)
>
> Is there a way to prevent this?
>
> I was thinking perhaps I could remove the All Records from Work Order Tracking?
>
> Or perhaps trying mxe.db.fetchResultStopLimit although the tech note says it is for Maximo 7.1 and above:
> http://www-01.ibm.com/support/docview.wss?uid=swg21412865
>
> Any suggestions or thoughts on this matter? Trying to keep the application and database running without these type of runaway queries.
>
One thing that is curious from the query in your logs, by default work
orders a filtered on the history flag = N and I didn't see that filter
in the query. That seems like it might narrow your result set to the
point where performance would be acceptable.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
Of sunk818
Sent: Thursday, August 15, 2013 6:34 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Work Order Tracking -> Select All Records took
over 5 minutes (Maximo 6.2.8)
Hi, we are currently on Maximo 6.2.8
One of the supervisors in Work Order Tracking selected the All Records
(above All Bookmarks). We have 3 million rows in workorder tracking.
This the warning that shows up in the log:
15 Aug 2013 13:14:40:981 [WARN] USER = (XXXXXXX) SPID = (166) app
(WOTRACK) object (WORKORDER) :select * from workorder where (siteid =
'FAC') order by wonum desc (execution took 314893 milliseconds)
Is there a way to prevent this?
I was thinking perhaps I could remove the All Records from Work Order
Tracking?
Or perhaps trying mxe.db.fetchResultStopLimit although the tech note
says it is for Maximo 7.1 and above:
http://www-01.ibm.com/support/docview.wss?uid=swg21412865
Any suggestions or thoughts on this matter? Trying to keep the
application and database running without these type of runaway queries.
order by wonum desc - is a killer
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Hanna, Christopher A CTR
Sent: 19 August 2013 15:07
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Work Order Tracking -> Select All Records took over 5 minutes (Maximo 6.2.8)
One thing that is curious from the query in your logs, by default work
orders a filtered on the history flag = N and I didn't see that filter
in the query. That seems like it might narrow your result set to the
point where performance would be acceptable.
-----Original Message-----
From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf
Of sunk818
Sent: Thursday, August 15, 2013 6:34 PM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Work Order Tracking -> Select All Records took
over 5 minutes (Maximo 6.2.8)
Hi, we are currently on Maximo 6.2.8
One of the supervisors in Work Order Tracking selected the All Records
(above All Bookmarks). We have 3 million rows in workorder tracking.
This the warning that shows up in the log:
15 Aug 2013 13:14:40:981 [WARN] USER = (XXXXXXX) SPID = (166) app
(WOTRACK) object (WORKORDER) :select * from workorder where (siteid =
'FAC') order by wonum desc (execution took 314893 milliseconds)
Is there a way to prevent this?
I was thinking perhaps I could remove the All Records from Work Order
Tracking?
Or perhaps trying mxe.db.fetchResultStopLimit although the tech note
says it is for Maximo 7.1 and above:
http://www-01.ibm.com/support/docview.wss?uid=swg21412865
Any suggestions or thoughts on this matter? Trying to keep the
application and database running without these type of runaway queries.
Come and visit us at Offshore Europe 2013
Find out more on our website
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************
Historyflag = n is part of the query if you go to > work Oder tracking.
The question is does your supervisor needs to see all work orders or only his work orders,
1st ) Lead can be a where clause
2nd) which status he is interested in plan, waiting for approval, waiting for scheduling, in progress or any synonyms you may have used.
3rd) you don't have is task = 'N' if you don't have this clause you will retrieve all operations which is certainly not what your supervisor requires unless he wants to know if other crew are involved which could be an other query.
3rd) coming back to all replies history flag = y, this only applies if your techs, spy or anyone responsible for closing your work orders (close), this is really essential as it flags work order with the history flag and must important release all material reserved but not issued.
hope this would help
On 20 ao�t 2013, at 17:48, sunk818 <swkim@getty.edu> wrote:
>
> Historyflag = n is part of the query if you go to > work Oder tracking.
>
> From there if you select all records, the query maximo runs is select * from workorder
>
> You can try it yourself in test environment if you'd like with SQL logging turned on.
>
> I'm looking for a way to remove "all records" or to hide it. I'm not looking for suggestions or comments about the query or where clause.
>
> Could I modify the .class file that displays the all records drop down command?
>
> --- In MAXIMO@yahoogroups.com, "Hanna, Christopher A CTR" <christopher.a.hanna@...> wrote:
> >
> > One thing that is curious from the query in your logs, by default work
> > orders a filtered on the history flag = N and I didn't see that filter
> > in the query. That seems like it might narrow your result set to the
> > point where performance would be acceptable.
> >
> > -----Original Message-----
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> > Of sunk818
> > Sent: Thursday, August 15, 2013 6:34 PM
> > To: MAXIMO@yahoogroups.com
> > Subject: [MAXIMO List] Work Order Tracking -> Select All Records took
> > over 5 minutes (Maximo 6.2.8)
> >
> >
> >
> > Hi, we are currently on Maximo 6.2.8
> >
> > One of the supervisors in Work Order Tracking selected the All Records
> > (above All Bookmarks). We have 3 million rows in workorder tracking.
> >
> > This the warning that shows up in the log:
> >
> > 15 Aug 2013 13:14:40:981 [WARN] USER = (XXXXXXX) SPID = (166) app
> > (WOTRACK) object (WORKORDER) :select * from workorder where (siteid =
> > 'FAC') order by wonum desc (execution took 314893 milliseconds)
> >
> > Is there a way to prevent this?
> >
> > I was thinking perhaps I could remove the All Records from Work Order
> > Tracking?
> >
> > Or perhaps trying mxe.db.fetchResultStopLimit although the tech note
> > says it is for Maximo 7.1 and above:
> > http://www-01.ibm.com/support/docview.wss?uid=swg21412865
> >
> > Any suggestions or thoughts on this matter? Trying to keep the
> > application and database running without these type of runaway queries.
> >
>
>
IBM has a workaround, but it is only for Maximo 7.1 and up.
http://www-01.ibm.com/support/docview.wss?uid=swg21573826
Since we are upgrading to Maximo 7 soon, we can put this in place after the upgrade.