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.
Hello everyone. I have a bit of an issue that, quite frankly, is driving me crazy. About a week ago I started noticing that when entering data into the DESCRIPTION (in various apps) the system would NOT return any values. All other fields work (for example: vendor #'s, item #'s MFR #'s commodity etc) as long as the DESCRIPTION field is left unpopulated - else the return value is 0. If, for another example, I go to the INVENTORY screen and hit enter the data is populated for all fields; which tells me that the TABLE.COLUMN relationship is sound. I have been going back and forth with IBM support for a week now and they had me focus on the SEARCH TYPE of each OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that my test environment is not having this issue and the SEARCH TYPE of these objects match in both environments thus eliminating IBM's theory.
If I may explain a bit further, when populating data into the DESCRIPTION field and hitting enter no error is displayed....the screen just yields 0 results. Out of curiousity, I attempted a search utilizing the ADVANCED SEARCH function and when I hit enter I received the following error: Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service (Microsoft Search) is not available. The system administrator must start this service. Now, when I received this error I was excited as I had hopes that this would point me in the direction of achieving a solution. I searched the forums and learned that this feature is handled within our SQL server and so I contacted our DBA and they confirmed that it had been "disabled" to improve server performance. I asked IBM how to proceed and they said to enable MS Search, stop the Maximo application, restart the Maximo application. We did this with 0 change in the DESCRIPTION fields behavior.
I am reaching out to you in hopes that someone will have an idea as to what my issue is. I was almost positive that the MS Search was the issue, but am again discouraged. IBM, so far, is as confused as I am. One would think that these symptoms would easily identify the culprit given that they were presented to the right individual - which obviously is not me.
My apologies for the lengthy e-mail, but I wanted to include as many details as possible. My system info is as follows:
V6.2.6
SERVER OS: WINDOWS 2003 5.2
APP SERVER: IBM WEBSPHERE 6.0
Thanks in advance for your time
Did your DBA restart the services or a complete reboot of the sql server? I
have found in the past it required a complete reboot..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
Office: 571-403-8940
Cell: 571-970-7965
(Embedded image moved to file: pic02600.gif)
From: Zeroxpectations <zeroxpectations@yahoo.com>
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Date: 03/09/2012 12:52 AM
Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
ASSETS, COMPANIES ETC)
Sent by: MAXIMO@yahoogroups.com
Hello everyone. I have a bit of an issue that, quite frankly, is driving
me crazy. About a week ago I started noticing that when entering data into
the DESCRIPTION (in various apps) the system would NOT return any values.
All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
etc) as long as the DESCRIPTION field is left unpopulated - else the return
value is 0. If, for another example, I go to the INVENTORY screen and hit
enter the data is populated for all fields; which tells me that the
TABLE.COLUMN relationship is sound. I have been going back and forth with
IBM support for a week now and they had me focus on the SEARCH TYPE of each
OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
my test environment is not having this issue and the SEARCH TYPE of these
objects match in both environments thus eliminating IBM's theory.
If I may explain a bit further, when populating data into the DESCRIPTION
field and hitting enter no error is displayed....the screen just yields 0
results. Out of curiousity, I attempted a search utilizing the ADVANCED
SEARCH function and when I hit enter I received the following error:
Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
(Microsoft Search) is not available. The system administrator must start
this service. Now, when I received this error I was excited as I had hopes
that this would point me in the direction of achieving a solution. I
searched the forums and learned that this feature is handled within our SQL
server and so I contacted our DBA and they confirmed that it had been
"disabled" to improve server performance. I asked IBM how to proceed and
they said to enable MS Search, stop the Maximo application, restart the
Maximo application. We did this with 0 change in the DESCRIPTION fields
behavior.
I am reaching out to you in hopes that someone will have an idea as to what
my issue is. I was almost positive that the MS Search was the issue, but
am again discouraged. IBM, so far, is as confused as I am. One would
think that these symptoms would easily identify the culprit given that they
were presented to the right individual - which obviously is not me.
My apologies for the lengthy e-mail, but I wanted to include as many
details as possible. My system info is as follows:
V6.2.6
SERVER OS: WINDOWS 2003 5.2
APP SERVER: IBM WEBSPHERE 6.0
Thanks in advance for your time
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.
You may also have to rebuild your Full-Text Index since it's been turned off for awhile.
Travis Herron
(Sorry if this shows up twice. . .I've typed this once already but it isn't showing up for some reason)
--- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@...> wrote:
>
> Did your DBA restart the services or a complete reboot of the sql server? I
> have found in the past it required a complete reboot..
>
>
>
> Shannon Sutton
> CMMS Specialist
> EMCOR Government Services
> Office: 571-403-8940
> Cell: 571-970-7965
>
> (Embedded image moved to file: pic02600.gif)
>
>
>
> From: Zeroxpectations <zeroxpectations@...>
> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> Date: 03/09/2012 12:52 AM
> Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
> ASSETS, COMPANIES ETC)
> Sent by: MAXIMO@yahoogroups.com
>
>
>
>
>
>
> Hello everyone. I have a bit of an issue that, quite frankly, is driving
> me crazy. About a week ago I started noticing that when entering data into
> the DESCRIPTIONÂ (in various apps) the system would NOT return any values.
> All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
> etc) as long as the DESCRIPTION field is left unpopulated - else the return
> value is 0.  If, for another example, I go to the INVENTORY screen and hit
> enter the data is populated for all fields; which tells me that the
> TABLE.COLUMN relationship is sound. I have been going back and forth with
> IBM support for a week now and they had me focus on the SEARCH TYPE of each
> OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
> my test environment is not having this issue and the SEARCH TYPE of these
> objects match in both environments thus eliminating IBM's theory.
>
> If I may explain a bit further, when populating data into the DESCRIPTION
> field and hitting enter no error is displayed....the screen just yields 0
> results. Out of curiousity, I attempted a search utilizing the ADVANCED
> SEARCH function and when I hit enter I received the following error:
> Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> (Microsoft Search) is not available. The system administrator must start
> this service. Now, when I received this error I was excited as I had hopes
> that this would point me in the direction of achieving a solution. I
> searched the forums and learned that this feature is handled within our SQL
> server and so I contacted our DBA and they confirmed that it had been
> "disabled" to improve server performance. I asked IBM how to proceed and
> they said to enable MS Search, stop the Maximo application, restart the
> Maximo application. We did this with 0 change in the DESCRIPTION fields
> behavior.
>
> I am reaching out to you in hopes that someone will have an idea as to what
> my issue is. I was almost positive that the MS Search was the issue, but
> am again discouraged. IBM, so far, is as confused as I am. One would
> think that these symptoms would easily identify the culprit given that they
> were presented to the right individual - which obviously is not me.
>
> My apologies for the lengthy e-mail, but I wanted to include as many
> details as possible. My system info is as follows:
>
> V6.2.6
> SERVER OS: WINDOWS 2003 5.2
> APP SERVER: IBM WEBSPHERE 6.0
>
> Thanks in advance for your time
>
>
>
>
>
>
> This message is for the named person's use only. It may contain confidential,
> proprietary or legally privileged information. No confidentiality or privilege
> is waived or lost by any mistransmission. If you receive this message in error,
> please immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part of this message if you are
> not the intended recipient.
>
>
>
>
>
>
My DBA is telling me that she rebooted the server, but the Database error is still rearing it's ugly head when using the ADVANCED SEARCH function.
On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@emcor.net> wrote:
> Did your DBA restart the services or a complete reboot of the sql server? I
> have found in the past it required a complete reboot..
>
>
>
> Shannon Sutton
> CMMS Specialist
> EMCOR Government Services
> Office: 571-403-8940
> Cell: 571-970-7965
>
> (Embedded image moved to file: pic02600.gif)
>
>
>
> From: Zeroxpectations <zeroxpectations@yahoo.com>
> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> Date: 03/09/2012 12:52 AM
> Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
> ASSETS, COMPANIES ETC)
> Sent by: MAXIMO@yahoogroups.com
>
>
>
>
>
>
> Hello everyone. I have a bit of an issue that, quite frankly, is driving
> me crazy. About a week ago I started noticing that when entering data into
> the DESCRIPTION (in various apps) the system would NOT return any values.
> All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
> etc) as long as the DESCRIPTION field is left unpopulated - else the return
> value is 0. If, for another example, I go to the INVENTORY screen and hit
> enter the data is populated for all fields; which tells me that the
> TABLE.COLUMN relationship is sound. I have been going back and forth with
> IBM support for a week now and they had me focus on the SEARCH TYPE of each
> OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
> my test environment is not having this issue and the SEARCH TYPE of these
> objects match in both environments thus eliminating IBM's theory.
>
> If I may explain a bit further, when populating data into the DESCRIPTION
> field and hitting enter no error is displayed....the screen just yields 0
> results. Out of curiousity, I attempted a search utilizing the ADVANCED
> SEARCH function and when I hit enter I received the following error:
> Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> (Microsoft Search) is not available. The system administrator must start
> this service. Now, when I received this error I was excited as I had hopes
> that this would point me in the direction of achieving a solution. I
> searched the forums and learned that this feature is handled within our SQL
> server and so I contacted our DBA and they confirmed that it had been
> "disabled" to improve server performance. I asked IBM how to proceed and
> they said to enable MS Search, stop the Maximo application, restart the
> Maximo application. We did this with 0 change in the DESCRIPTION fields
> behavior.
>
> I am reaching out to you in hopes that someone will have an idea as to what
> my issue is. I was almost positive that the MS Search was the issue, but
> am again discouraged. IBM, so far, is as confused as I am. One would
> think that these symptoms would easily identify the culprit given that they
> were presented to the right individual - which obviously is not me.
>
> My apologies for the lengthy e-mail, but I wanted to include as many
> details as possible. My system info is as follows:
>
> V6.2.6
> SERVER OS: WINDOWS 2003 5.2
> APP SERVER: IBM WEBSPHERE 6.0
>
> Thanks in advance for your time
>
>
>
>
>
>
> This message is for the named person's use only. It may contain confidential,
> proprietary or legally privileged information. No confidentiality or privilege
> is waived or lost by any mistransmission. If you receive this message in error,
> please immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part of this message if you are
> not the intended recipient.
>
>
>
>
>
>
Thanks for the info, Travis. I will make this suggestion and see if it helps. I had asked IBM if we needed to rebuild/deploy the .ear files or if we should reindex the tables and they said that was not necessary. Perhaps your suggestion will work
On Mar 9, 2012, at 9:15 AM, "Travis Herron" <therron@pcci.edu> wrote:
> You may also have to rebuild your Full-Text Index since it's been turned off for awhile.
>
> Travis Herron
>
> (Sorry if this shows up twice. . .I've typed this once already but it isn't showing up for some reason)
>
> --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@...> wrote:
> >
> > Did your DBA restart the services or a complete reboot of the sql server? I
> > have found in the past it required a complete reboot..
> >
> >
> >
> > Shannon Sutton
> > CMMS Specialist
> > EMCOR Government Services
> > Office: 571-403-8940
> > Cell: 571-970-7965
> >
> > (Embedded image moved to file: pic02600.gif)
> >
> >
> >
> > From: Zeroxpectations <zeroxpectations@...>
> > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > Date: 03/09/2012 12:52 AM
> > Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
> > ASSETS, COMPANIES ETC)
> > Sent by: MAXIMO@yahoogroups.com
> >
> >
> >
> >
> >
> >
> > Hello everyone. I have a bit of an issue that, quite frankly, is driving
> > me crazy. About a week ago I started noticing that when entering data into
> > the DESCRIPTIONÂ (in various apps) the system would NOT return any values.
> > All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
> > etc) as long as the DESCRIPTION field is left unpopulated - else the return
> > value is 0.  If, for another example, I go to the INVENTORY screen and hit
> > enter the data is populated for all fields; which tells me that the
> > TABLE.COLUMN relationship is sound. I have been going back and forth with
> > IBM support for a week now and they had me focus on the SEARCH TYPE of each
> > OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
> > my test environment is not having this issue and the SEARCH TYPE of these
> > objects match in both environments thus eliminating IBM's theory.
> >
> > If I may explain a bit further, when populating data into the DESCRIPTION
> > field and hitting enter no error is displayed....the screen just yields 0
> > results. Out of curiousity, I attempted a search utilizing the ADVANCED
> > SEARCH function and when I hit enter I received the following error:
> > Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> > (Microsoft Search) is not available. The system administrator must start
> > this service. Now, when I received this error I was excited as I had hopes
> > that this would point me in the direction of achieving a solution. I
> > searched the forums and learned that this feature is handled within our SQL
> > server and so I contacted our DBA and they confirmed that it had been
> > "disabled" to improve server performance. I asked IBM how to proceed and
> > they said to enable MS Search, stop the Maximo application, restart the
> > Maximo application. We did this with 0 change in the DESCRIPTION fields
> > behavior.
> >
> > I am reaching out to you in hopes that someone will have an idea as to what
> > my issue is. I was almost positive that the MS Search was the issue, but
> > am again discouraged. IBM, so far, is as confused as I am. One would
> > think that these symptoms would easily identify the culprit given that they
> > were presented to the right individual - which obviously is not me.
> >
> > My apologies for the lengthy e-mail, but I wanted to include as many
> > details as possible. My system info is as follows:
> >
> > V6.2.6
> > SERVER OS: WINDOWS 2003 5.2
> > APP SERVER: IBM WEBSPHERE 6.0
> >
> > Thanks in advance for your time
> >
> >
> >
> >
> >
> >
> > This message is for the named person's use only. It may contain confidential,
> > proprietary or legally privileged information. No confidentiality or privilege
> > is waived or lost by any mistransmission. If you receive this message in error,
> > please immediately delete it and all copies of it from your system, destroy any
> > hard copies of it and notify the sender. You must not, directly or indirectly,
> > use, disclose, distribute, print, or copy any part of this message if you are
> > not the intended recipient.
> >
> >
> >
> >
> >
> >
>
>
While I haven't had this issue before on SQL Server I have on Oracle and it can be difficult getting on the same page with a DBA who isn't familiar with Maximo. I would suggest activating the SQL logger and capturing a query example to share with your DBA. The query should return no rows when using full text searching but work with a traditional query. Once you can show the DBA what you expect via SQL you can ask them to troubleshoot it until the query works via a query tool.
This article contains some examples of full text queries for Maximo on SQl Server, if this is the issue then, assuming you have a WO with a description of "my work order" then this should work:
Select * from WORKORDER where description = 'my work order'
But this should fail:
Select * from WORKORDER
where contains(description , ' FORMSOF(INFLECTIONAL,my)
& FORMSOF(INFLECTIONAL,work)
& FORMSOF(INFLECTIONAL,order) ')
You'll need to fix the single quotes and modify the SQL to suit your data of course.
Chris.
On Mar 9, 2012, at 9:39 AM, zeroxpectations@yahoo.com wrote:
> Thanks for the info, Travis. I will make this suggestion and see if it helps. I had asked IBM if we needed to rebuild/deploy the .ear files or if we should reindex the tables and they said that was not necessary. Perhaps your suggestion will work
>
> On Mar 9, 2012, at 9:15 AM, "Travis Herron" <therron@pcci.edu> wrote:
>
>
> > You may also have to rebuild your Full-Text Index since it's been turned off for awhile.
> >
> > Travis Herron
> >
> > (Sorry if this shows up twice. . .I've typed this once already but it isn't showing up for some reason)
> >
> > --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@...> wrote:
> > >
> > > Did your DBA restart the services or a complete reboot of the sql server? I
> > > have found in the past it required a complete reboot..
> > >
> > >
> > >
> > > Shannon Sutton
> > > CMMS Specialist
> > > EMCOR Government Services
> > > Office: 571-403-8940
> > > Cell: 571-970-7965
> > >
> > > (Embedded image moved to file: pic02600.gif)
> > >
> > >
> > >
> > > From: Zeroxpectations <zeroxpectations@...>
> > > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > > Date: 03/09/2012 12:52 AM
> > > Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
> > > ASSETS, COMPANIES ETC)
> > > Sent by: MAXIMO@yahoogroups.com
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hello everyone. I have a bit of an issue that, quite frankly, is driving
> > > me crazy. About a week ago I started noticing that when entering data into
> > > the DESCRIPTIONÂ (in various apps) the system would NOT return any values.
> > > All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
> > > etc) as long as the DESCRIPTION field is left unpopulated - else the return
> > > value is 0.  If, for another example, I go to the INVENTORY screen and hit
> > > enter the data is populated for all fields; which tells me that the
> > > TABLE.COLUMN relationship is sound. I have been going back and forth with
> > > IBM support for a week now and they had me focus on the SEARCH TYPE of each
> > > OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
> > > my test environment is not having this issue and the SEARCH TYPE of these
> > > objects match in both environments thus eliminating IBM's theory.
> > >
> > > If I may explain a bit further, when populating data into the DESCRIPTION
> > > field and hitting enter no error is displayed....the screen just yields 0
> > > results. Out of curiousity, I attempted a search utilizing the ADVANCED
> > > SEARCH function and when I hit enter I received the following error:
> > > Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> > > (Microsoft Search) is not available. The system administrator must start
> > > this service. Now, when I received this error I was excited as I had hopes
> > > that this would point me in the direction of achieving a solution. I
> > > searched the forums and learned that this feature is handled within our SQL
> > > server and so I contacted our DBA and they confirmed that it had been
> > > "disabled" to improve server performance. I asked IBM how to proceed and
> > > they said to enable MS Search, stop the Maximo application, restart the
> > > Maximo application. We did this with 0 change in the DESCRIPTION fields
> > > behavior.
> > >
> > > I am reaching out to you in hopes that someone will have an idea as to what
> > > my issue is. I was almost positive that the MS Search was the issue, but
> > > am again discouraged. IBM, so far, is as confused as I am. One would
> > > think that these symptoms would easily identify the culprit given that they
> > > were presented to the right individual - which obviously is not me.
> > >
> > > My apologies for the lengthy e-mail, but I wanted to include as many
> > > details as possible. My system info is as follows:
> > >
> > > V6.2.6
> > > SERVER OS: WINDOWS 2003 5.2
> > > APP SERVER: IBM WEBSPHERE 6.0
> > >
> > > Thanks in advance for your time
> > >
> > >
> > >
> > >
> > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>
>
>
Hi,
A reboot of the SQL Server will not rebuild the full-text index. The DBA needs to rebuild the full-text index. The index is only built for data added while it is turned on. Since the data was added before it was on you need to rebuild.
Also, if you do any mass imports of data you should rebuild the DB indexes since those will not be optimized during the mass import.
Dave Bone
--- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
>
> My DBA is telling me that she rebooted the server, but the Database error is still rearing it's ugly head when using the ADVANCED SEARCH function.
>
> On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
>
> > Did your DBA restart the services or a complete reboot of the sql server? I
> > have found in the past it required a complete reboot..
> >
> >
> >
> > Shannon Sutton
> > CMMS Specialist
> > EMCOR Government Services
> > Office: 571-403-8940
> > Cell: 571-970-7965
> >
> > (Embedded image moved to file: pic02600.gif)
> >
> >
> >
> > From: Zeroxpectations <zeroxpectations@...>
> > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > Date: 03/09/2012 12:52 AM
> > Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
> > ASSETS, COMPANIES ETC)
> > Sent by: MAXIMO@yahoogroups.com
> >
> >
> >
> >
> >
> >
> > Hello everyone. I have a bit of an issue that, quite frankly, is driving
> > me crazy. About a week ago I started noticing that when entering data into
> > the DESCRIPTION (in various apps) the system would NOT return any values.
> > All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
> > etc) as long as the DESCRIPTION field is left unpopulated - else the return
> > value is 0. If, for another example, I go to the INVENTORY screen and hit
> > enter the data is populated for all fields; which tells me that the
> > TABLE.COLUMN relationship is sound. I have been going back and forth with
> > IBM support for a week now and they had me focus on the SEARCH TYPE of each
> > OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
> > my test environment is not having this issue and the SEARCH TYPE of these
> > objects match in both environments thus eliminating IBM's theory.
> >
> > If I may explain a bit further, when populating data into the DESCRIPTION
> > field and hitting enter no error is displayed....the screen just yields 0
> > results. Out of curiousity, I attempted a search utilizing the ADVANCED
> > SEARCH function and when I hit enter I received the following error:
> > Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> > (Microsoft Search) is not available. The system administrator must start
> > this service. Now, when I received this error I was excited as I had hopes
> > that this would point me in the direction of achieving a solution. I
> > searched the forums and learned that this feature is handled within our SQL
> > server and so I contacted our DBA and they confirmed that it had been
> > "disabled" to improve server performance. I asked IBM how to proceed and
> > they said to enable MS Search, stop the Maximo application, restart the
> > Maximo application. We did this with 0 change in the DESCRIPTION fields
> > behavior.
> >
> > I am reaching out to you in hopes that someone will have an idea as to what
> > my issue is. I was almost positive that the MS Search was the issue, but
> > am again discouraged. IBM, so far, is as confused as I am. One would
> > think that these symptoms would easily identify the culprit given that they
> > were presented to the right individual - which obviously is not me.
> >
> > My apologies for the lengthy e-mail, but I wanted to include as many
> > details as possible. My system info is as follows:
> >
> > V6.2.6
> > SERVER OS: WINDOWS 2003 5.2
> > APP SERVER: IBM WEBSPHERE 6.0
> >
> > Thanks in advance for your time
> >
> >
> >
> >
> >
> >
> > This message is for the named person's use only. It may contain confidential,
> > proprietary or legally privileged information. No confidentiality or privilege
> > is waived or lost by any mistransmission. If you receive this message in error,
> > please immediately delete it and all copies of it from your system, destroy any
> > hard copies of it and notify the sender. You must not, directly or indirectly,
> > use, disclose, distribute, print, or copy any part of this message if you are
> > not the intended recipient.
> >
> >
> >
> >
> >
> >
>
>
>
Hi. Thanks for your response. I am
Being told that MS Search was disabled just two weeks ago so would that cause a zero return when entering data into the description field? This search issue just started happening within the last couple of weeks so that is why I believe MS Search to be the issue. What I don't understand is why the other fields (item #, Asset #, Company #, commodity) still work. I guess they do not utilize the MS Search function?
On Mar 9, 2012, at 11:25 AM, "in2data" <in2data@yahoo.com> wrote:
> Hi,
>
> A reboot of the SQL Server will not rebuild the full-text index. The DBA needs to rebuild the full-text index. The index is only built for data added while it is turned on. Since the data was added before it was on you need to rebuild.
>
> Also, if you do any mass imports of data you should rebuild the DB indexes since those will not be optimized during the mass import.
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
> >
> > My DBA is telling me that she rebooted the server, but the Database error is still rearing it's ugly head when using the ADVANCED SEARCH function.
> >
> > On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
> >
> > > Did your DBA restart the services or a complete reboot of the sql server? I
> > > have found in the past it required a complete reboot..
> > >
> > >
> > >
> > > Shannon Sutton
> > > CMMS Specialist
> > > EMCOR Government Services
> > > Office: 571-403-8940
> > > Cell: 571-970-7965
> > >
> > > (Embedded image moved to file: pic02600.gif)
> > >
> > >
> > >
> > > From: Zeroxpectations <zeroxpectations@...>
> > > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > > Date: 03/09/2012 12:52 AM
> > > Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY,
> > > ASSETS, COMPANIES ETC)
> > > Sent by: MAXIMO@yahoogroups.com
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hello everyone. I have a bit of an issue that, quite frankly, is driving
> > > me crazy. About a week ago I started noticing that when entering data into
> > > the DESCRIPTION (in various apps) the system would NOT return any values.
> > > All other fields work (for example: vendor #'s, item #'s MFR #'s commodity
> > > etc) as long as the DESCRIPTION field is left unpopulated - else the return
> > > value is 0. If, for another example, I go to the INVENTORY screen and hit
> > > enter the data is populated for all fields; which tells me that the
> > > TABLE.COLUMN relationship is sound. I have been going back and forth with
> > > IBM support for a week now and they had me focus on the SEARCH TYPE of each
> > > OBJECT asking that I change it from TEXT to WILDCARD, but the issue is that
> > > my test environment is not having this issue and the SEARCH TYPE of these
> > > objects match in both environments thus eliminating IBM's theory.
> > >
> > > If I may explain a bit further, when populating data into the DESCRIPTION
> > > field and hitting enter no error is displayed....the screen just yields 0
> > > results. Out of curiousity, I attempted a search utilizing the ADVANCED
> > > SEARCH function and when I hit enter I received the following error:
> > > Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> > > (Microsoft Search) is not available. The system administrator must start
> > > this service. Now, when I received this error I was excited as I had hopes
> > > that this would point me in the direction of achieving a solution. I
> > > searched the forums and learned that this feature is handled within our SQL
> > > server and so I contacted our DBA and they confirmed that it had been
> > > "disabled" to improve server performance. I asked IBM how to proceed and
> > > they said to enable MS Search, stop the Maximo application, restart the
> > > Maximo application. We did this with 0 change in the DESCRIPTION fields
> > > behavior.
> > >
> > > I am reaching out to you in hopes that someone will have an idea as to what
> > > my issue is. I was almost positive that the MS Search was the issue, but
> > > am again discouraged. IBM, so far, is as confused as I am. One would
> > > think that these symptoms would easily identify the culprit given that they
> > > were presented to the right individual - which obviously is not me.
> > >
> > > My apologies for the lengthy e-mail, but I wanted to include as many
> > > details as possible. My system info is as follows:
> > >
> > > V6.2.6
> > > SERVER OS: WINDOWS 2003 5.2
> > > APP SERVER: IBM WEBSPHERE 6.0
> > >
> > > Thanks in advance for your time
> > >
> > >
> > >
> > >
> > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
> TODAY(Beta) • Powered by Yahoo!
> Actress makes biting dig at her ex
> Elisabeth Moss wasn’t wed to Fred Armisen a long time, but the marriage clearly didn't end well.
> Privacy Policy
The other fields do not use the text search capabilities.
On Fri, Mar 9, 2012 at 11:35 AM, <zeroxpectations@yahoo.com> wrote:
> **
>
>
> Hi. Thanks for your response. I am
> Being told that MS Search was disabled just two weeks ago so would that
> cause a zero return when entering data into the description field? This
> search issue just started happening within the last couple of weeks so that
> is why I believe MS Search to be the issue. What I don't understand is why
> the other fields (item #, Asset #, Company #, commodity) still work. I
> guess they do not utilize the MS Search function?
>
> On Mar 9, 2012, at 11:25 AM, "in2data" <in2data@yahoo.com> wrote:
>
> > Hi,
> >
> > A reboot of the SQL Server will not rebuild the full-text index. The DBA
> needs to rebuild the full-text index. The index is only built for data
> added while it is turned on. Since the data was added before it was on you
> need to rebuild.
> >
> > Also, if you do any mass imports of data you should rebuild the DB
> indexes since those will not be optimized during the mass import.
> >
> > Dave Bone
> >
> > --- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
> > >
> > > My DBA is telling me that she rebooted the server, but the Database
> error is still rearing it's ugly head when using the ADVANCED SEARCH
> function.
> > >
> > > On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
> > >
> > > > Did your DBA restart the services or a complete reboot of the sql
> server? I
> > > > have found in the past it required a complete reboot..
> > > >
> > > >
> > > >
> > > > Shannon Sutton
> > > > CMMS Specialist
> > > > EMCOR Government Services
> > > > Office: 571-403-8940
> > > > Cell: 571-970-7965
> > > >
> > > > (Embedded image moved to file: pic02600.gif)
> > > >
> > > >
> > > >
> > > > From: Zeroxpectations <zeroxpectations@...>
> > > > To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > > > Date: 03/09/2012 12:52 AM
> > > > Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING
> (INVENTORY,
> > > > ASSETS, COMPANIES ETC)
> > > > Sent by: MAXIMO@yahoogroups.com
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hello everyone. I have a bit of an issue that, quite frankly, is
> driving
> > > > me crazy. About a week ago I started noticing that when entering
> data into
> > > > the DESCRIPTION (in various apps) the system would NOT return any
> values.
> > > > All other fields work (for example: vendor #'s, item #'s MFR #'s
> commodity
> > > > etc) as long as the DESCRIPTION field is left unpopulated - else the
> return
> > > > value is 0. If, for another example, I go to the INVENTORY screen
> and hit
> > > > enter the data is populated for all fields; which tells me that the
> > > > TABLE.COLUMN relationship is sound. I have been going back and forth
> with
> > > > IBM support for a week now and they had me focus on the SEARCH TYPE
> of each
> > > > OBJECT asking that I change it from TEXT to WILDCARD, but the issue
> is that
> > > > my test environment is not having this issue and the SEARCH TYPE of
> these
> > > > objects match in both environments thus eliminating IBM's theory.
> > > >
> > > > If I may explain a bit further, when populating data into the
> DESCRIPTION
> > > > field and hitting enter no error is displayed....the screen just
> yields 0
> > > > results. Out of curiousity, I attempted a search utilizing the
> ADVANCED
> > > > SEARCH function and when I hit enter I received the following error:
> > > > Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> > > > (Microsoft Search) is not available. The system administrator must
> start
> > > > this service. Now, when I received this error I was excited as I had
> hopes
> > > > that this would point me in the direction of achieving a solution. I
> > > > searched the forums and learned that this feature is handled within
> our SQL
> > > > server and so I contacted our DBA and they confirmed that it had
> been
> > > > "disabled" to improve server performance. I asked IBM how to proceed
> and
> > > > they said to enable MS Search, stop the Maximo application, restart
> the
> > > > Maximo application. We did this with 0 change in the DESCRIPTION
> fields
> > > > behavior.
> > > >
> > > > I am reaching out to you in hopes that someone will have an idea as
> to what
> > > > my issue is. I was almost positive that the MS Search was the issue,
> but
> > > > am again discouraged. IBM, so far, is as confused as I am. One would
> > > > think that these symptoms would easily identify the culprit given
> that they
> > > > were presented to the right individual - which obviously is not me.
> > > >
> > > > My apologies for the lengthy e-mail, but I wanted to include as many
> > > > details as possible. My system info is as follows:
> > > >
> > > > V6.2.6
> > > > SERVER OS: WINDOWS 2003 5.2
> > > > APP SERVER: IBM WEBSPHERE 6.0
> > > >
> > > > Thanks in advance for your time
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > This message is for the named person's use only. It may contain
> confidential,
> > > > proprietary or legally privileged information. No confidentiality or
> privilege
> > > > is waived or lost by any mistransmission. If you receive this
> message in error,
> > > > please immediately delete it and all copies of it from your system,
> destroy any
> > > > hard copies of it and notify the sender. You must not, directly or
> indirectly,
> > > > use, disclose, distribute, print, or copy any part of this message
> if you are
> > > > not the intended recipient.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> >
> > TODAY(Beta) � Powered by Yahoo!
> > Actress makes biting dig at her ex
> > Elisabeth Moss wasn’t wed to Fred Armisen a long time, but the
> marriage clearly didn't end well.
> > Privacy Policy
>
>
>
>
>
>
Ok. Thanks again for everyone's help. I believe I have what I need to begin the correction process; though I may bother you again if an issue arises. Love this forum!
On Mar 9, 2012, at 12:26 PM, Chris Lawless <lawlessc@gmail.com> wrote:
> The other fields do not use the text search capabilities.
>
> On Fri, Mar 9, 2012 at 11:35 AM, <zeroxpectations@yahoo.com> wrote:
>
>> **
>>
>>
>> Hi. Thanks for your response. I am
>> Being told that MS Search was disabled just two weeks ago so would that
>> cause a zero return when entering data into the description field? This
>> search issue just started happening within the last couple of weeks so that
>> is why I believe MS Search to be the issue. What I don't understand is why
>> the other fields (item #, Asset #, Company #, commodity) still work. I
>> guess they do not utilize the MS Search function?
>>
>> On Mar 9, 2012, at 11:25 AM, "in2data" <in2data@yahoo.com> wrote:
>>
>>> Hi,
>>>
>>> A reboot of the SQL Server will not rebuild the full-text index. The DBA
>> needs to rebuild the full-text index. The index is only built for data
>> added while it is turned on. Since the data was added before it was on you
>> need to rebuild.
>>>
>>> Also, if you do any mass imports of data you should rebuild the DB
>> indexes since those will not be optimized during the mass import.
>>>
>>> Dave Bone
>>>
>>> --- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
>>>>
>>>> My DBA is telling me that she rebooted the server, but the Database
>> error is still rearing it's ugly head when using the ADVANCED SEARCH
>> function.
>>>>
>>>> On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
>>>>
>>>>> Did your DBA restart the services or a complete reboot of the sql
>> server? I
>>>>> have found in the past it required a complete reboot..
>>>>>
>>>>>
>>>>>
>>>>> Shannon Sutton
>>>>> CMMS Specialist
>>>>> EMCOR Government Services
>>>>> Office: 571-403-8940
>>>>> Cell: 571-970-7965
>>>>>
>>>>> (Embedded image moved to file: pic02600.gif)
>>>>>
>>>>>
>>>>>
>>>>> From: Zeroxpectations <zeroxpectations@...>
>>>>> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
>>>>> Date: 03/09/2012 12:52 AM
>>>>> Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING
>> (INVENTORY,
>>>>> ASSETS, COMPANIES ETC)
>>>>> Sent by: MAXIMO@yahoogroups.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Hello everyone. I have a bit of an issue that, quite frankly, is
>> driving
>>>>> me crazy. About a week ago I started noticing that when entering
>> data into
>>>>> the DESCRIPTION (in various apps) the system would NOT return any
>> values.
>>>>> All other fields work (for example: vendor #'s, item #'s MFR #'s
>> commodity
>>>>> etc) as long as the DESCRIPTION field is left unpopulated - else the
>> return
>>>>> value is 0. If, for another example, I go to the INVENTORY screen
>> and hit
>>>>> enter the data is populated for all fields; which tells me that the
>>>>> TABLE.COLUMN relationship is sound. I have been going back and forth
>> with
>>>>> IBM support for a week now and they had me focus on the SEARCH TYPE
>> of each
>>>>> OBJECT asking that I change it from TEXT to WILDCARD, but the issue
>> is that
>>>>> my test environment is not having this issue and the SEARCH TYPE of
>> these
>>>>> objects match in both environments thus eliminating IBM's theory.
>>>>>
>>>>> If I may explain a bit further, when populating data into the
>> DESCRIPTION
>>>>> field and hitting enter no error is displayed....the screen just
>> yields 0
>>>>> results. Out of curiousity, I attempted a search utilizing the
>> ADVANCED
>>>>> SEARCH function and when I hit enter I received the following error:
>>>>> Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
>>>>> (Microsoft Search) is not available. The system administrator must
>> start
>>>>> this service. Now, when I received this error I was excited as I had
>> hopes
>>>>> that this would point me in the direction of achieving a solution. I
>>>>> searched the forums and learned that this feature is handled within
>> our SQL
>>>>> server and so I contacted our DBA and they confirmed that it had
>> been
>>>>> "disabled" to improve server performance. I asked IBM how to proceed
>> and
>>>>> they said to enable MS Search, stop the Maximo application, restart
>> the
>>>>> Maximo application. We did this with 0 change in the DESCRIPTION
>> fields
>>>>> behavior.
>>>>>
>>>>> I am reaching out to you in hopes that someone will have an idea as
>> to what
>>>>> my issue is. I was almost positive that the MS Search was the issue,
>> but
>>>>> am again discouraged. IBM, so far, is as confused as I am. One would
>>>>> think that these symptoms would easily identify the culprit given
>> that they
>>>>> were presented to the right individual - which obviously is not me.
>>>>>
>>>>> My apologies for the lengthy e-mail, but I wanted to include as many
>>>>> details as possible. My system info is as follows:
>>>>>
>>>>> V6.2.6
>>>>> SERVER OS: WINDOWS 2003 5.2
>>>>> APP SERVER: IBM WEBSPHERE 6.0
>>>>>
>>>>> Thanks in advance for your time
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> This message is for the named person's use only. It may contain
>> confidential,
>>>>> proprietary or legally privileged information. No confidentiality or
>> privilege
>>>>> is waived or lost by any mistransmission. If you receive this
>> message in error,
>>>>> please immediately delete it and all copies of it from your system,
>> destroy any
>>>>> hard copies of it and notify the sender. You must not, directly or
>> indirectly,
>>>>> use, disclose, distribute, print, or copy any part of this message
>> if you are
>>>>> not the intended recipient.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> TODAY(Beta) � Powered by Yahoo!
>>> Actress makes biting dig at her ex
>>> Elisabeth Moss wasn’t wed to Fred Armisen a long time, but the
>> marriage clearly didn't end well.
>>> Privacy Policy
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
>
>
The best way to show your love for the forum is to post the solution, while
many of us are happy to advise there is no substitute for a "Here's how I
fixed this issue" post once it's all rectified. :-)
Chris.
On Fri, Mar 9, 2012 at 1:01 PM, <zeroxpectations@yahoo.com> wrote:
> **
>
>
> Ok. Thanks again for everyone's help. I believe I have what I need to
> begin the correction process; though I may bother you again if an issue
> arises. Love this forum!
>
> On Mar 9, 2012, at 12:26 PM, Chris Lawless <lawlessc@gmail.com> wrote:
>
> > The other fields do not use the text search capabilities.
> >
> > On Fri, Mar 9, 2012 at 11:35 AM, <zeroxpectations@yahoo.com> wrote:
> >
> >> **
>
> >>
> >>
> >> Hi. Thanks for your response. I am
> >> Being told that MS Search was disabled just two weeks ago so would that
> >> cause a zero return when entering data into the description field? This
> >> search issue just started happening within the last couple of weeks so
> that
> >> is why I believe MS Search to be the issue. What I don't understand is
> why
> >> the other fields (item #, Asset #, Company #, commodity) still work. I
> >> guess they do not utilize the MS Search function?
> >>
> >> On Mar 9, 2012, at 11:25 AM, "in2data" <in2data@yahoo.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> A reboot of the SQL Server will not rebuild the full-text index. The
> DBA
> >> needs to rebuild the full-text index. The index is only built for data
> >> added while it is turned on. Since the data was added before it was on
> you
> >> need to rebuild.
> >>>
> >>> Also, if you do any mass imports of data you should rebuild the DB
> >> indexes since those will not be optimized during the mass import.
> >>>
> >>> Dave Bone
> >>>
> >>> --- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
> >>>>
> >>>> My DBA is telling me that she rebooted the server, but the Database
> >> error is still rearing it's ugly head when using the ADVANCED SEARCH
> >> function.
> >>>>
> >>>> On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
> >>>>
> >>>>> Did your DBA restart the services or a complete reboot of the sql
> >> server? I
> >>>>> have found in the past it required a complete reboot..
> >>>>>
> >>>>>
> >>>>>
> >>>>> Shannon Sutton
> >>>>> CMMS Specialist
> >>>>> EMCOR Government Services
> >>>>> Office: 571-403-8940
> >>>>> Cell: 571-970-7965
> >>>>>
> >>>>> (Embedded image moved to file: pic02600.gif)
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Zeroxpectations <zeroxpectations@...>
> >>>>> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> >>>>> Date: 03/09/2012 12:52 AM
> >>>>> Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING
> >> (INVENTORY,
> >>>>> ASSETS, COMPANIES ETC)
> >>>>> Sent by: MAXIMO@yahoogroups.com
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hello everyone. I have a bit of an issue that, quite frankly, is
> >> driving
> >>>>> me crazy. About a week ago I started noticing that when entering
> >> data into
> >>>>> the DESCRIPTION (in various apps) the system would NOT return any
> >> values.
> >>>>> All other fields work (for example: vendor #'s, item #'s MFR #'s
> >> commodity
> >>>>> etc) as long as the DESCRIPTION field is left unpopulated - else the
> >> return
> >>>>> value is 0. If, for another example, I go to the INVENTORY screen
> >> and hit
> >>>>> enter the data is populated for all fields; which tells me that the
> >>>>> TABLE.COLUMN relationship is sound. I have been going back and forth
> >> with
> >>>>> IBM support for a week now and they had me focus on the SEARCH TYPE
> >> of each
> >>>>> OBJECT asking that I change it from TEXT to WILDCARD, but the issue
> >> is that
> >>>>> my test environment is not having this issue and the SEARCH TYPE of
> >> these
> >>>>> objects match in both environments thus eliminating IBM's theory.
> >>>>>
> >>>>> If I may explain a bit further, when populating data into the
> >> DESCRIPTION
> >>>>> field and hitting enter no error is displayed....the screen just
> >> yields 0
> >>>>> results. Out of curiousity, I attempted a search utilizing the
> >> ADVANCED
> >>>>> SEARCH function and when I hit enter I received the following error:
> >>>>> Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> >>>>> (Microsoft Search) is not available. The system administrator must
> >> start
> >>>>> this service. Now, when I received this error I was excited as I had
> >> hopes
> >>>>> that this would point me in the direction of achieving a solution. I
> >>>>> searched the forums and learned that this feature is handled within
> >> our SQL
> >>>>> server and so I contacted our DBA and they confirmed that it had
> >> been
> >>>>> "disabled" to improve server performance. I asked IBM how to proceed
> >> and
> >>>>> they said to enable MS Search, stop the Maximo application, restart
> >> the
> >>>>> Maximo application. We did this with 0 change in the DESCRIPTION
> >> fields
> >>>>> behavior.
> >>>>>
> >>>>> I am reaching out to you in hopes that someone will have an idea as
> >> to what
> >>>>> my issue is. I was almost positive that the MS Search was the issue,
> >> but
> >>>>> am again discouraged. IBM, so far, is as confused as I am. One would
> >>>>> think that these symptoms would easily identify the culprit given
> >> that they
> >>>>> were presented to the right individual - which obviously is not me.
> >>>>>
> >>>>> My apologies for the lengthy e-mail, but I wanted to include as many
> >>>>> details as possible. My system info is as follows:
> >>>>>
> >>>>> V6.2.6
> >>>>> SERVER OS: WINDOWS 2003 5.2
> >>>>> APP SERVER: IBM WEBSPHERE 6.0
> >>>>>
> >>>>> Thanks in advance for your time
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> This message is for the named person's use only. It may contain
> >> confidential,
> >>>>> proprietary or legally privileged information. No confidentiality or
> >> privilege
> >>>>> is waived or lost by any mistransmission. If you receive this
> >> message in error,
> >>>>> please immediately delete it and all copies of it from your system,
> >> destroy any
> >>>>> hard copies of it and notify the sender. You must not, directly or
> >> indirectly,
> >>>>> use, disclose, distribute, print, or copy any part of this message
> >> if you are
> >>>>> not the intended recipient.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> TODAY(Beta) � Powered by Yahoo!
> >>> Actress makes biting dig at her ex
> >>> Elisabeth Moss wasn’t wed to Fred Armisen a long time, but the
>
> >> marriage clearly didn't end well.
> >>> Privacy Policy
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
> >
> > ------------------------------------
>
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com
> > Leave : MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> >
> >
> >
>
>
>
You got it. Thanks again
On Mar 9, 2012, at 1:05 PM, Chris Lawless <lawlessc@gmail.com> wrote:
> The best way to show your love for the forum is to post the solution, while
> many of us are happy to advise there is no substitute for a "Here's how I
> fixed this issue" post once it's all rectified. :-)
>
> Chris.
>
> On Fri, Mar 9, 2012 at 1:01 PM, <zeroxpectations@yahoo.com> wrote:
>
> > **
> >
> >
> > Ok. Thanks again for everyone's help. I believe I have what I need to
> > begin the correction process; though I may bother you again if an issue
> > arises. Love this forum!
> >
> > On Mar 9, 2012, at 12:26 PM, Chris Lawless <lawlessc@gmail.com> wrote:
> >
> > > The other fields do not use the text search capabilities.
> > >
> > > On Fri, Mar 9, 2012 at 11:35 AM, <zeroxpectations@yahoo.com> wrote:
> > >
> > >> **
> >
> > >>
> > >>
> > >> Hi. Thanks for your response. I am
> > >> Being told that MS Search was disabled just two weeks ago so would that
> > >> cause a zero return when entering data into the description field? This
> > >> search issue just started happening within the last couple of weeks so
> > that
> > >> is why I believe MS Search to be the issue. What I don't understand is
> > why
> > >> the other fields (item #, Asset #, Company #, commodity) still work. I
> > >> guess they do not utilize the MS Search function?
> > >>
> > >> On Mar 9, 2012, at 11:25 AM, "in2data" <in2data@yahoo.com> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> A reboot of the SQL Server will not rebuild the full-text index. The
> > DBA
> > >> needs to rebuild the full-text index. The index is only built for data
> > >> added while it is turned on. Since the data was added before it was on
> > you
> > >> need to rebuild.
> > >>>
> > >>> Also, if you do any mass imports of data you should rebuild the DB
> > >> indexes since those will not be optimized during the mass import.
> > >>>
> > >>> Dave Bone
> > >>>
> > >>> --- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
> > >>>>
> > >>>> My DBA is telling me that she rebooted the server, but the Database
> > >> error is still rearing it's ugly head when using the ADVANCED SEARCH
> > >> function.
> > >>>>
> > >>>> On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
> > >>>>
> > >>>>> Did your DBA restart the services or a complete reboot of the sql
> > >> server? I
> > >>>>> have found in the past it required a complete reboot..
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Shannon Sutton
> > >>>>> CMMS Specialist
> > >>>>> EMCOR Government Services
> > >>>>> Office: 571-403-8940
> > >>>>> Cell: 571-970-7965
> > >>>>>
> > >>>>> (Embedded image moved to file: pic02600.gif)
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> From: Zeroxpectations <zeroxpectations@...>
> > >>>>> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> > >>>>> Date: 03/09/2012 12:52 AM
> > >>>>> Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING
> > >> (INVENTORY,
> > >>>>> ASSETS, COMPANIES ETC)
> > >>>>> Sent by: MAXIMO@yahoogroups.com
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Hello everyone. I have a bit of an issue that, quite frankly, is
> > >> driving
> > >>>>> me crazy. About a week ago I started noticing that when entering
> > >> data into
> > >>>>> the DESCRIPTION (in various apps) the system would NOT return any
> > >> values.
> > >>>>> All other fields work (for example: vendor #'s, item #'s MFR #'s
> > >> commodity
> > >>>>> etc) as long as the DESCRIPTION field is left unpopulated - else the
> > >> return
> > >>>>> value is 0. If, for another example, I go to the INVENTORY screen
> > >> and hit
> > >>>>> enter the data is populated for all fields; which tells me that the
> > >>>>> TABLE.COLUMN relationship is sound. I have been going back and forth
> > >> with
> > >>>>> IBM support for a week now and they had me focus on the SEARCH TYPE
> > >> of each
> > >>>>> OBJECT asking that I change it from TEXT to WILDCARD, but the issue
> > >> is that
> > >>>>> my test environment is not having this issue and the SEARCH TYPE of
> > >> these
> > >>>>> objects match in both environments thus eliminating IBM's theory.
> > >>>>>
> > >>>>> If I may explain a bit further, when populating data into the
> > >> DESCRIPTION
> > >>>>> field and hitting enter no error is displayed....the screen just
> > >> yields 0
> > >>>>> results. Out of curiousity, I attempted a search utilizing the
> > >> ADVANCED
> > >>>>> SEARCH function and when I hit enter I received the following error:
> > >>>>> Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> > >>>>> (Microsoft Search) is not available. The system administrator must
> > >> start
> > >>>>> this service. Now, when I received this error I was excited as I had
> > >> hopes
> > >>>>> that this would point me in the direction of achieving a solution. I
> > >>>>> searched the forums and learned that this feature is handled within
> > >> our SQL
> > >>>>> server and so I contacted our DBA and they confirmed that it had
> > >> been
> > >>>>> "disabled" to improve server performance. I asked IBM how to proceed
> > >> and
> > >>>>> they said to enable MS Search, stop the Maximo application, restart
> > >> the
> > >>>>> Maximo application. We did this with 0 change in the DESCRIPTION
> > >> fields
> > >>>>> behavior.
> > >>>>>
> > >>>>> I am reaching out to you in hopes that someone will have an idea as
> > >> to what
> > >>>>> my issue is. I was almost positive that the MS Search was the issue,
> > >> but
> > >>>>> am again discouraged. IBM, so far, is as confused as I am. One would
> > >>>>> think that these symptoms would easily identify the culprit given
> > >> that they
> > >>>>> were presented to the right individual - which obviously is not me.
> > >>>>>
> > >>>>> My apologies for the lengthy e-mail, but I wanted to include as many
> > >>>>> details as possible. My system info is as follows:
> > >>>>>
> > >>>>> V6.2.6
> > >>>>> SERVER OS: WINDOWS 2003 5.2
> > >>>>> APP SERVER: IBM WEBSPHERE 6.0
> > >>>>>
> > >>>>> Thanks in advance for your time
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> This message is for the named person's use only. It may contain
> > >> confidential,
> > >>>>> proprietary or legally privileged information. No confidentiality or
> > >> privilege
> > >>>>> is waived or lost by any mistransmission. If you receive this
> > >> message in error,
> > >>>>> please immediately delete it and all copies of it from your system,
> > >> destroy any
> > >>>>> hard copies of it and notify the sender. You must not, directly or
> > >> indirectly,
> > >>>>> use, disclose, distribute, print, or copy any part of this message
> > >> if you are
> > >>>>> not the intended recipient.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> TODAY(Beta) � Powered by Yahoo!
> > >>> Actress makes biting dig at her ex
> > >>> Elisabeth Moss wasn’t wed to Fred Armisen a long time, but the
> >
> > >> marriage clearly didn't end well.
> > >>> Privacy Policy
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> >
> > >
> > > Email addresses you might need:
> > > Posting: MAXIMO@yahoogroups.com
> > > Join : MAXIMO-subscribe@yahoogroups.com
> > > Leave : MAXIMO-unsubscribe@yahoogroups.com
> > > Cry : MAXIMO-owner@yahoogroups.com
> > > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
It is with great joy that I type this e-mail as my issue with the search fields has been resolved. It turns out that the MS Search function was indeed disabled on our SQL server. Our DB thought that they had enabled the function, but had been mistaken. After additional testing I requested that they check again to confirm and this is when they realized that they were doing something wrong as they were not able to enable the program. After we got it figured out I asked them what steps were involved because I wanted to post it here and this is what they gave me:
1. Open the services.mmc console
2. Enable the Windows Search service
3. Configure the Windows Search service to start automatically at Windows start up
4. Start service
We were able to make this change without interrupting Maximo access. I hope this helps someone down the road as this really had me (and IBM) stumped. I think our DB learned something as well because in hindsight this doesnt appear to be a complicated process (enabling the MS Search function), but when doing something for the first time it always seems more complicated.
Thanks again to all who responded to my issue. You guys (and gals) really helped me stay focused in the right area.
________________________________
From: Chris Lawless <lawlessc@gmail.com>
To: MAXIMO@yahoogroups.com
Sent: Friday, March 9, 2012 1:05 PM
Subject: Re: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING (INVENTORY, ASSETS, COMPANIES ETC)
The best way to show your love for the forum is to post the solution, while
many of us are happy to advise there is no substitute for a "Here's how I
fixed this issue" post once it's all rectified. :-)
Chris.
On Fri, Mar 9, 2012 at 1:01 PM, <zeroxpectations@yahoo.com> wrote:
> **
>
>
> Ok. Thanks again for everyone's help. I believe I have what I need to
> begin the correction process; though I may bother you again if an issue
> arises. Love this forum!
>
> On Mar 9, 2012, at 12:26 PM, Chris Lawless <lawlessc@gmail.com> wrote:
>
> > The other fields do not use the text search capabilities.
> >
> > On Fri, Mar 9, 2012 at 11:35 AM, <zeroxpectations@yahoo.com> wrote:
> >
> >> **
>
> >>
> >>
> >> Hi. Thanks for your response. I am
> >> Being told that MS Search was disabled just two weeks ago so would that
> >> cause a zero return when entering data into the description field? This
> >> search issue just started happening within the last couple of weeks so
> that
> >> is why I believe MS Search to be the issue. What I don't understand is
> why
> >> the other fields (item #, Asset #, Company #, commodity) still work. I
> >> guess they do not utilize the MS Search function?
> >>
> >> On Mar 9, 2012, at 11:25 AM, "in2data" <in2data@yahoo.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> A reboot of the SQL Server will not rebuild the full-text index. The
> DBA
> >> needs to rebuild the full-text index. The index is only built for data
> >> added while it is turned on. Since the data was added before it was on
> you
> >> need to rebuild.
> >>>
> >>> Also, if you do any mass imports of data you should rebuild the DB
> >> indexes since those will not be optimized during the mass import.
> >>>
> >>> Dave Bone
> >>>
> >>> --- In MAXIMO@yahoogroups.com, zeroxpectations@... wrote:
> >>>>
> >>>> My DBA is telling me that she rebooted the server, but the Database
> >> error is still rearing it's ugly head when using the ADVANCED SEARCH
> >> function.
> >>>>
> >>>> On Mar 9, 2012, at 5:53 AM, Shannon Sutton <ssutton@...> wrote:
> >>>>
> >>>>> Did your DBA restart the services or a complete reboot of the sql
> >> server? I
> >>>>> have found in the past it required a complete reboot..
> >>>>>
> >>>>>
> >>>>>
> >>>>> Shannon Sutton
> >>>>> CMMS Specialist
> >>>>> EMCOR Government Services
> >>>>> Office: 571-403-8940
> >>>>> Cell: 571-970-7965
> >>>>>
> >>>>> (Embedded image moved to file: pic02600.gif)
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Zeroxpectations <zeroxpectations@...>
> >>>>> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> >>>>> Date: 03/09/2012 12:52 AM
> >>>>> Subject: [MAXIMO List] DESCRIPTION SEARCH FIELDS NOT WORKING
> >> (INVENTORY,
> >>>>> ASSETS, COMPANIES ETC)
> >>>>> Sent by: MAXIMO@yahoogroups.com
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Hello everyone. I have a bit of an issue that, quite frankly, is
> >> driving
> >>>>> me crazy. About a week ago I started noticing that when entering
> >> data into
> >>>>> the DESCRIPTION (in various apps) the system would NOT return any
> >> values.
> >>>>> All other fields work (for example: vendor #'s, item #'s MFR #'s
> >> commodity
> >>>>> etc) as long as the DESCRIPTION field is left unpopulated - else the
> >> return
> >>>>> value is 0. If, for another example, I go to the INVENTORY screen
> >> and hit
> >>>>> enter the data is populated for all fields; which tells me that the
> >>>>> TABLE.COLUMN relationship is sound. I have been going back and forth
> >> with
> >>>>> IBM support for a week now and they had me focus on the SEARCH TYPE
> >> of each
> >>>>> OBJECT asking that I change it from TEXT to WILDCARD, but the issue
> >> is that
> >>>>> my test environment is not having this issue and the SEARCH TYPE of
> >> these
> >>>>> objects match in both environments thus eliminating IBM's theory.
> >>>>>
> >>>>> If I may explain a bit further, when populating data into the
> >> DESCRIPTION
> >>>>> field and hitting enter no error is displayed....the screen just
> >> yields 0
> >>>>> results. Out of curiousity, I attempted a search utilizing the
> >> ADVANCED
> >>>>> SEARCH function and when I hit enter I received the following error:
> >>>>> Database Error # 7602 has occurred. [MAXIMO]The Full-Text Service
> >>>>> (Microsoft Search) is not available. The system administrator must
> >> start
> >>>>> this service. Now, when I received this error I was excited as I had
> >> hopes
> >>>>> that this would point me in the direction of achieving a solution. I
> >>>>> searched the forums and learned that this feature is handled within
> >> our SQL
> >>>>> server and so I contacted our DBA and they confirmed that it had
> >> been
> >>>>> "disabled" to improve server performance. I asked IBM how to proceed
> >> and
> >>>>> they said to enable MS Search, stop the Maximo application, restart
> >> the
> >>>>> Maximo application. We did this with 0 change in the DESCRIPTION
> >> fields
> >>>>> behavior.
> >>>>>
> >>>>> I am reaching out to you in hopes that someone will have an idea as
> >> to what
> >>>>> my issue is. I was almost positive that the MS Search was the issue,
> >> but
> >>>>> am again discouraged. IBM, so far, is as confused as I am. One would
> >>>>> think that these symptoms would easily identify the culprit given
> >> that they
> >>>>> were presented to the right individual - which obviously is not me.
> >>>>>
> >>>>> My apologies for the lengthy e-mail, but I wanted to include as many
> >>>>> details as possible. My system info is as follows:
> >>>>>
> >>>>> V6.2.6
> >>>>> SERVER OS: WINDOWS 2003 5.2
> >>>>> APP SERVER: IBM WEBSPHERE 6.0
> >>>>>
> >>>>> Thanks in advance for your time
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> This message is for the named person's use only. It may contain
> >> confidential,
> >>>>> proprietary or legally privileged information. No confidentiality or
> >> privilege
> >>>>> is waived or lost by any mistransmission. If you receive this
> >> message in error,
> >>>>> please immediately delete it and all copies of it from your system,
> >> destroy any
> >>>>> hard copies of it and notify the sender. You must not, directly or
> >> indirectly,
> >>>>> use, disclose, distribute, print, or copy any part of this message
> >> if you are
> >>>>> not the intended recipient.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> TODAY(Beta) � Powered by Yahoo!
> >>> Actress makes biting dig at her ex
> >>> Elisabeth Moss wasn’t wed to Fred Armisen a long time, but the
>
> >> marriage clearly didn't end well.
> >>> Privacy Policy
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
> >
> > ------------------------------------
>
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com
> > Leave : MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> >
> >
> >
>
>
>