Maximo List Archive

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.



text search issue

From: Ian Wright (2013-11-13 09:54)

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server

IBM WebSphere Application Server 7.0.0.25


Version

IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05


Server OS

Windows Server 2008 R2 6.1 build 7601 Service Pack 1


Server DB

Microsoft SQL Server 10.50 (10.50.2500)



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.
**************************************************************************************************************


From: (2013-11-13 04:14)

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.



---In MAXIMO@yahoogroups.com, <ian.wright@...> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25
Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05
Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1
Server DB
Microsoft SQL Server 10.50 (10.50.2500)



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.
****************************************************************************************************************************************************************************************



From: (2013-11-13 04:19)

Not sure why my first post did not go through? Hopefully it will not double post.


Ian,


I just tested our system:
7.5.0.4
WebSphere
Oracle


And a search for "2" returned the following and many more:
.2
2
1/2
2 x 150
2,3


This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.






---In MAXIMO@yahoogroups.com, <mlevinson@...> wrote:

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.



---In MAXIMO@yahoogroups.com, <ian.wright@...> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25
Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05
Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1
Server DB
Microsoft SQL Server 10.50 (10.50.2500)



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.
****************************************************************************************************************************************************************************************





From: Ian Wright (2013-11-13 12:26)

I know wildcard has different behaviour to text searches
I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare

Oracle may also have a different behaviour to SQL Server

Thanks for the reply
Rgds Ian


From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@ledgesoft.com
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: RE: text search issue



Not sure why my first post did not go through? Hopefully it will not double post.



Ian,



I just tested our system:

7.5.0.4

WebSphere

Oracle



And a search for "2" returned the following and many more:

.2

2

1/2

2 x 150

2,3



This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.




---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <mlevinson@...<mailto:mlevinson@...>> wrote:

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.

---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************


From: (2013-11-13 04:29)

Ian,


I just tested our system:
7.5.0.4
WebSphere
Oracle


And a search for "2" returned the following and many more:
.2
2
1/2
2 x 150
2,3


This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.





---In maximo@yahoogroups.com, <ian.wright@...> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25
Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05
Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1
Server DB
Microsoft SQL Server 10.50 (10.50.2500)



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.
****************************************************************************************************************************************************************************************



From: (2013-11-13 04:37)

This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.



---In maximo@yahoogroups.com, <ian.wright@...> wrote:

I know wildcard has different behaviour to text searches
I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare

Oracle may also have a different behaviour to SQL Server

Thanks for the reply
Rgds Ian


From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: RE: text search issue




Not sure why my first post did not go through? Hopefully it will not double post.

Ian,

I just tested our system:
7.5.0.4
WebSphere
Oracle

And a search for "2" returned the following and many more:
.2
2
1/2
2 x 150
2,3

This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.




---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <mlevinson@... mailto:mlevinson@...> wrote: Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.

---In MAXIMO@yahoogroups.com, <ian.wright@... mailto:ian.wright@...> wrote:
Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25
Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05
Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1
Server DB
Microsoft SQL Server 10.50 (10.50.2500)


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.
****************************************************************************************************************************************************************************************













From: Ian Wright (2013-11-13 12:45)

Yep been there – but this client likes the text search facility so would like to get a resolution but if not I think we will need to go wildcard – we get or inventory descriptions from SAP and they use “ in the description as the field is so short ☹

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@ledgesoft.com
Sent: 13 November 2013 12:37
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: text search issue



This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.




---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

I know wildcard has different behaviour to text searches

I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare



Oracle may also have a different behaviour to SQL Server



Thanks for the reply

Rgds Ian





From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: RE: text search issue





Not sure why my first post did not go through? Hopefully it will not double post.



Ian,



I just tested our system:

7.5.0.4

WebSphere

Oracle



And a search for "2" returned the following and many more:

.2

2

1/2

2 x 150

2,3



This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.




---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <mlevinson@...<mailto:mlevinson@...>> wrote:

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.



---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************


From: (2013-11-13 06:41)

SQL Server does behave differently than Oracle.

This is what I've read; I haven't upgraded far enough to actually "do" this. But out-of-the-box, SQL Server will not full-text index a one-character word (such as your 2). However, in SQL Server 2010 there's supposed to be a way you can go in to SQL's dictionary and add words for it to index. So you might need to add 2 and 2" to it's dictionary, and rebuild the full-text index, then it **should** work.


---In MAXIMO@yahoogroups.com, <ian.wright@...> wrote:

Yep been there – but this client likes the text search facility so would like to get a resolution but if not I think we will need to go wildcard – we get or inventory descriptions from SAP and they use “ in the description as the field is so short L

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:37
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: text search issue




This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.



---In maximo@yahoogroups.com mailto:maximo@yahoogroups.com, <ian.wright@... mailto:ian.wright@...> wrote: I know wildcard has different behaviour to text searches
I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare

Oracle may also have a different behaviour to SQL Server

Thanks for the reply
Rgds Ian


From: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: RE: text search issue




Not sure why my first post did not go through? Hopefully it will not double post.

Ian,

I just tested our system:
7.5.0.4
WebSphere
Oracle

And a search for "2" returned the following and many more:
.2
2
1/2
2 x 150
2,3

This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.


---In MAXIMO@yahoogroups.com, <mlevinson@... mailto:mlevinson@...> wrote:
Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.

---In MAXIMO@yahoogroups.com, <ian.wright@... mailto:ian.wright@...> wrote:
Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25
Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05
Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1
Server DB
Microsoft SQL Server 10.50 (10.50.2500)


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.
****************************************************************************************************************************************************************************************



















From: Ian Wright (2013-11-13 15:13)

That’s great thanks I’ll let you know if our dba solves it
This looks like it may help
http://stackoverflow.com/questions/17526458/sql-server-fulltext-search-for-multilevel-list-strings

Rgds Ian

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of therron@pcci.edu
Sent: 13 November 2013 14:42
To: MAXIMO@yahoogroups.com
Subject: RE: RE: [MAXIMO List] RE: text search issue



SQL Server does behave differently than Oracle.



This is what I've read; I haven't upgraded far enough to actually "do" this. But out-of-the-box, SQL Server will not full-text index a one-character word (such as your 2). However, in SQL Server 2010 there's supposed to be a way you can go in to SQL's dictionary and add words for it to index. So you might need to add 2 and 2" to it's dictionary, and rebuild the full-text index, then it **should** work.


---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Yep been there – but this client likes the text search facility so would like to get a resolution but if not I think we will need to go wildcard – we get or inventory descriptions from SAP and they use “ in the description as the field is so short ☹



From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:37
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: text search issue





This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.




---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

I know wildcard has different behaviour to text searches

I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare



Oracle may also have a different behaviour to SQL Server



Thanks for the reply

Rgds Ian





From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: RE: text search issue





Not sure why my first post did not go through? Hopefully it will not double post.



Ian,



I just tested our system:

7.5.0.4

WebSphere

Oracle



And a search for "2" returned the following and many more:

.2

2

1/2

2 x 150

2,3



This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.





---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <mlevinson@...<mailto:mlevinson@...>> wrote:

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.



---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************


From: (2013-11-13 09:05)

I think your database is using the system stoplist. System stopwords do not show in sys.fulltext_stopwords, they appear in sys.fulltext_system_stopwords.
To check if your tables are using stoplists:


select stoplist_id
from sys.fulltext_indexes



Anything that returns not NULL is using a stoplist. 0 is the system stoplist.
I used the following to remove the stoplist from all tables:

DECLARE @stoplistname VARCHAR(50), @textcatalogname VARCHAR(50), @sql VARCHAR(500)
SET @stoplistname='off'
SET @textcatalogname='textcatalog'
SET @sql='IF EXISTS(SELECT 1 FROM sys.fulltext_indexes WHERE object_id = OBJECT_ID(''?'')) ALTER FULLTEXT INDEX ON ? SET STOPLIST '+@stoplistname

EXEC sp_msforeachtable @sql
EXEC ('ALTER FULLTEXT CATALOG '+@textcatalogname+' REBUILD')
GO


Using text search with numbers will look for numerical values.
Searching for "3" will find:
3
03
will not find:
30
0.3
X3 (where X is any letter)


I could not find a way to search for the quote character.

Let me know if this helps.

---In maximo@yahoogroups.com, <ian.wright@...> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25

Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05

Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1

Server DB
Microsoft SQL Server 10.50 (10.50.2500)



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.
****************************************************************************************************************************************************************************************





---In maximo@yahoogroups.com, <ian.wright@...> wrote:

That’s great thanks I’ll let you know if our dba solves it
This looks like it may help
http://stackoverflow.com/questions/17526458/sql-server-fulltext-search-for-multilevel-list-strings http://stackoverflow.com/questions/17526458/sql-server-fulltext-search-for-multilevel-list-strings

Rgds Ian

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of therron@...
Sent: 13 November 2013 14:42
To: MAXIMO@yahoogroups.com
Subject: RE: RE: [MAXIMO List] RE: text search issue




SQL Server does behave differently than Oracle.

This is what I've read; I haven't upgraded far enough to actually "do" this. But out-of-the-box, SQL Server will not full-text index a one-character word (such as your 2). However, in SQL Server 2010 there's supposed to be a way you can go in to SQL's dictionary and add words for it to index. So you might need to add 2 and 2" to it's dictionary, and rebuild the full-text index, then it **should** work.



---In MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com, <ian.wright@... mailto:ian.wright@...> wrote: Yep been there – but this client likes the text search facility so would like to get a resolution but if not I think we will need to go wildcard – we get or inventory descriptions from SAP and they use “ in the description as the field is so short L

From: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:37
To: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: text search issue




This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.


---In maximo@yahoogroups.com, <ian.wright@... mailto:ian.wright@...> wrote:
I know wildcard has different behaviour to text searches
I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare

Oracle may also have a different behaviour to SQL Server

Thanks for the reply
Rgds Ian


From: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com mailto:MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: RE: text search issue




Not sure why my first post did not go through? Hopefully it will not double post.

Ian,

I just tested our system:
7.5.0.4
WebSphere
Oracle

And a search for "2" returned the following and many more:
.2
2
1/2
2 x 150
2,3

This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.


---In MAXIMO@yahoogroups.com, <mlevinson@... mailto:mlevinson@...> wrote:
Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.

---In MAXIMO@yahoogroups.com, <ian.wright@... mailto:ian.wright@...> wrote:
Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch J )– we have a description : - CHECK VALVE, 2”
Searching for 2 does not find it neither does %2%
When you enter 2” the “ (inch) sign is removed when maximo creates the where clause
Note it does find a 12

The database has no stopword’s enforced

use [MAXUAT]
select * from sys.fulltext_stopwords
(0 row(s) affected)

App Server
IBM WebSphere Application Server 7.0.0.25
Version
IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05
Server OS
Windows Server 2008 R2 6.1 build 7601 Service Pack 1
Server DB
Microsoft SQL Server 10.50 (10.50.2500)


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.
****************************************************************************************************************************************************************************************

























From: Ian Wright (2013-11-13 17:13)

Many thanks our dba will apply and I’ll check tomorrow with the users if they are happy with the results
Rgds Ian

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of krosemanp@ci.superior.wi.us
Sent: 13 November 2013 17:05
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: text search issue



I think your database is using the system stoplist. System stopwords do not show in sys.fulltext_stopwords, they appear in sys.fulltext_system_stopwords.

To check if your tables are using stoplists:



select stoplist_id
from sys.fulltext_indexes



Anything that returns not NULL is using a stoplist. 0 is the system stoplist.

I used the following to remove the stoplist from all tables:


DECLARE @stoplistname VARCHAR(50), @textcatalogname VARCHAR(50), @sql VARCHAR(500)
SET @stoplistname='off'
SET @textcatalogname='textcatalog'
SET @sql='IF EXISTS(SELECT 1 FROM sys.fulltext_indexes WHERE object_id = OBJECT_ID(''?'')) ALTER FULLTEXT INDEX ON ? SET STOPLIST '+@stoplistname

EXEC sp_msforeachtable @sql
EXEC ('ALTER FULLTEXT CATALOG '+@textcatalogname+' REBUILD')
GO



Using text search with numbers will look for numerical values.

Searching for "3" will find:

3

03

will not find:

30

0.3

X3 (where X is any letter)

I could not find a way to search for the quote character.

Let me know if this helps.

---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************




---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

That’s great thanks I’ll let you know if our dba solves it

This looks like it may help

http://stackoverflow.com/questions/17526458/sql-server-fulltext-search-for-multilevel-list-strings



Rgds Ian



From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of therron@...
Sent: 13 November 2013 14:42
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: RE: RE: [MAXIMO List] RE: text search issue





SQL Server does behave differently than Oracle.



This is what I've read; I haven't upgraded far enough to actually "do" this. But out-of-the-box, SQL Server will not full-text index a one-character word (such as your 2). However, in SQL Server 2010 there's supposed to be a way you can go in to SQL's dictionary and add words for it to index. So you might need to add 2 and 2" to it's dictionary, and rebuild the full-text index, then it **should** work.


---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Yep been there – but this client likes the text search facility so would like to get a resolution but if not I think we will need to go wildcard – we get or inventory descriptions from SAP and they use “ in the description as the field is so short ☹



From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:37
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: text search issue





This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.





---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

I know wildcard has different behaviour to text searches

I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare



Oracle may also have a different behaviour to SQL Server



Thanks for the reply

Rgds Ian





From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: RE: text search issue





Not sure why my first post did not go through? Hopefully it will not double post.



Ian,



I just tested our system:

7.5.0.4

WebSphere

Oracle



And a search for "2" returned the following and many more:

.2

2

1/2

2 x 150

2,3



This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.





---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <mlevinson@...<mailto:mlevinson@...>> wrote:

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.



---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************


From: Ian Wright (2013-11-14 09:40)

Thanks that worked a treat

The quote character is a bit of an issue but I think they can live with it

Rgds Ian

------------------------------------------------------------------------------------------

I think your database is using the system stoplist. System stopwords do not show in sys.fulltext_stopwords, they appear in sys.fulltext_system_stopwords.

To check if your tables are using stoplists:



select stoplist_id
from sys.fulltext_indexes



Anything that returns not NULL is using a stoplist. 0 is the system stoplist.

I used the following to remove the stoplist from all tables:


DECLARE @stoplistname VARCHAR(50), @textcatalogname VARCHAR(50), @sql VARCHAR(500)
SET @stoplistname='off'
SET @textcatalogname='textcatalog'
SET @sql='IF EXISTS(SELECT 1 FROM sys.fulltext_indexes WHERE object_id = OBJECT_ID(''?'')) ALTER FULLTEXT INDEX ON ? SET STOPLIST '+@stoplistname

EXEC sp_msforeachtable @sql
EXEC ('ALTER FULLTEXT CATALOG '+@textcatalogname+' REBUILD')
GO



Using text search with numbers will look for numerical values.

Searching for "3" will find:

3

03

will not find:

30

0.3

X3 (where X is any letter)

I could not find a way to search for the quote character.

Let me know if this helps.

---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************




---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

That’s great thanks I’ll let you know if our dba solves it

This looks like it may help

http://stackoverflow.com/questions/17526458/sql-server-fulltext-search-for-multilevel-list-strings



Rgds Ian



From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of therron@...
Sent: 13 November 2013 14:42
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: RE: RE: [MAXIMO List] RE: text search issue





SQL Server does behave differently than Oracle.



This is what I've read; I haven't upgraded far enough to actually "do" this. But out-of-the-box, SQL Server will not full-text index a one-character word (such as your 2). However, in SQL Server 2010 there's supposed to be a way you can go in to SQL's dictionary and add words for it to index. So you might need to add 2 and 2" to it's dictionary, and rebuild the full-text index, then it **should** work.


---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Yep been there – but this client likes the text search facility so would like to get a resolution but if not I think we will need to go wildcard – we get or inventory descriptions from SAP and they use “ in the description as the field is so short ☹



From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:37
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: text search issue





This is one of the many configuration issue with MX out of the box. Some description fields are set to wildcard searches and some are not. One of the first things I do in any implementation is set all description fields search type to wildcard and required. After all what good is a record with no description.........Also any attribute that is presented on the list tab are set to wildcard search.
This problem also causes users issues when presented with a dialog box. Some search attributes are wildcard enabled, while others are not. I have found that many users get very confused if this is not corrected right up front.
Another gotcha I have found is although a particular application may be set to autonumber,, that autonumber can be overwritten by the user. So as a general rule, if an record is set to autonumber I also make that field read only on the screen.

Okay....... off my soapbox now.





---In maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

I know wildcard has different behaviour to text searches

I didn’t want to have to change all my description fields to wildcard or have a mixture of wildcard and text as it’ll be a training nightmare



Oracle may also have a different behaviour to SQL Server



Thanks for the reply

Rgds Ian





From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlevinson@...
Sent: 13 November 2013 12:20
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] RE: RE: text search issue





Not sure why my first post did not go through? Hopefully it will not double post.



Ian,



I just tested our system:

7.5.0.4

WebSphere

Oracle



And a search for "2" returned the following and many more:

.2

2

1/2

2 x 150

2,3



This test was done in the work order application searching the description attribute. In DB config the description attribute is set up as search type = wildcard.





---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <mlevinson@...<mailto:mlevinson@...>> wrote:

Also as a follow up test I changed the description from 2 to 2" and re-queried for 2" and it only returned 1 record.



---In MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>, <ian.wright@...<mailto:ian.wright@...>> wrote:

Anybody come across this and better still has a resolution (please don’t say 50mm or 2 Inch ☺ )– we have a description : - CHECK VALVE, 2”

Searching for 2 does not find it neither does %2%

When you enter 2” the “ (inch) sign is removed when maximo creates the where clause

Note it does find a 12



The database has no stopword’s enforced



use [MAXUAT]

select * from sys.fulltext_stopwords

(0 row(s) affected)



App Server


IBM WebSphere Application Server 7.0.0.25



Version


IBM Maximo Asset Management 7.5.0.4 Build 20130129-2023 DB Build V7504-00
Tivoli's process automation engine 7.5.0.4 Build 20130129-2023 DB Build V7504-38
IBM Maximo Adapter for Primavera 7.5.0.0 Build 20110418-1030 DB Build V7500-05
IBM Maximo Asset Management Scheduler 7.5.1.0 Build 20130129-2023 DB Build V7510-124
IBM Maximo for Oil And Gas 7.5.1.0 Build 20130227-1708 DB Build V7510-67
IBM Maximo Mobile 7.5.1.0 Build 20130305-1333 DB Build V7510-05



Server OS


Windows Server 2008 R2 6.1 build 7601 Service Pack 1



Server DB


Microsoft SQL Server 10.50 (10.50.2500)




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.
****************************************************************************************************************************************************************************************