Search issue with 8.5.0.6

Previous topic - Next topic

jeffs42885

Hello all,

I am wondering if anyone has seen this issue before. This issue is occuring when trynig to search on a folder when using a default/fixed field. This doesnt happen in our 8.4 environment, only 8.5.0.6 (aix6.1/was6.1/db2 9.7/cmod 8.5.0.6)

A error occurred in performSearch: A value must be specified for 'Msg Num (87 and/or 88)'2115 

Does anyone have any feedback? This does not happen when I use the OnDemand thick client, only the web interface that uses odwek.

Justin Derrick

That's a really weird error message.

There are differences in search between 8.4 and 8.5, but this looks like an error message from the System Log, not an Application Group/Folder.

Are you searching the System Log, or does your AG have a field called 'msg_num'?

-JD.
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Webinars:  https://CMOD.Training/
IBM CMOD Professional Services: https://CMOD.cloud

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

jeffs42885

Yes it is the system log. We gave one of our partners with very tight SLA's access to the folder and set the message to a fixed field that would bring up their reports as long as they typed 87 or 88 for message number.

jeffs42885

I had posted the wrong message, sorry about that. Here is what happens:

A error occurred in setSearchCriteria: Criteria 'Message' has a fixed value and cannot be overridden 

This didnt happen when we were pointing to our one environment that runs 8.4

jeffs42885

Came across this, but we dont use webi, and we are on 8.5.0.6 for odwek and cmod..

http://www-304.ibm.com/support/docview.wss?uid=swg21596070

kbsiva

Hello Jeff,
  It is an known issue in WEBi and there is an fix for that issue in WEBi , if you open an PMR and ask for it they give you a hotfix for it. We got one for 8.5.0.5. So try opening a PMR for the same you might be able to get something from support.

Thanks
Siva

jeffs42885

The fix that IBM suggested at this point was to downgrade odwek to 8.5.0.4..

??? ??? ???

still waiting on their dev team.

jeffs42885

Turned out that the issue was with ODWEK on our front end passing a hard coded value, quick fix :)