We are using Remedy 5.1 version. We have Some view forms on Remedy Arsystem. It just hangs up when i try to search "even gives timeout error sometimes".

When i login into the Toad and search the Same view its retrieving the results with in no time. Strange problem could not able to figure out wass going on in between.

Please help ASAP as i have so many search menus pointing to this form which are not retrieivng the results.

Can anybody help me in this issue.

How much data is in the view forms?
If you do an unqualified search on this data, you could be hanging the system due to the large number of entries.
Try limiting the results in the user to 1000 records or so and see if you get a result.
If so, check how many records (in the back end) there are and try not to perform unqualified searches.
May also pay to index a field and use that in the search.

This is having around 125000 records and i am limiting the search to 1000 records only. We have some search menus written on this form. They were working fine before couple of weeks back but now dont know whats the trouble. Please help.

-- Thank you

Can anybody help in this issue?

Are your databases statistics up to date?

Did you checked the SQL which is produced by Remedy? Is it possible that you have QBE match Anywhere on the View Form which results in a like search and not in equal what you might do in toad.

Hi - we've had some major issues with this sort of thing in the past, but have since sorted these. Our company uses a single SQL server that hosts around 40 - odd databases stored on a SAN.

Major performance issues with Remedy - timeouts - ARERR 92 etc -quite often (but not always) cropped up during times of peak business usage on some of the larger dbs.

We found that Remedy is particularly sensitive to how much tempdb resource is currently being utilised/available for processing. When the tempdb on the SQL server is being hammered by other resource-hungry dbs, Remedy won't be happy.

In the end we reallocated some of the other DBs (some of the resource-hungry, non-production dbs onto another SQL server) and haven't had any further issues with this.

Rgds,
Karl

Thanks for the responses. Here is the update.

Vincent,
I asked my DB Admin and he said that the statistics are upto date.

Thwe,
Do you want me to change the particular field to QBE match anywhere and re-do the search. I really did not understand it clearly.

karlj,
I understood that you increased the tempdb and it started working fine. Let me know the process so that i can ask my DBA to do that.

Thanks again for your time.

No Thwe ment that you might be searching a field wuth QBE = anywhere
Meaning your queries would like like this on the backend
Select name from view_vorm where id like '%4%'
which does a full table scan
SO what he was suggesting is, make sure the fields you search on is set to QBE Leading (at least)

Also check to see if the fields you are searching on is indexed on the foreign DB/Table

Make sure your workflow and/or menus qualification looks like this
'FIELD' = $FIELD$
and NOT
$FIELD$ = 'FIELD'

I had a similar case once where i mapped the field incorrectly so my Request ID was not unique and slowed down everything until it timed out. So make sure the field you've selected for your request id is UNIQUE !!!