We just finished upgrading IPAM to 3.1.0 and now the search function appears to be broken.
It doesn't seem to matter if we wildcard search or search for a specific node that IS in the database.
Anyone else finding this?
Thanks
FWIW, I just freshly installed IPAM 3.1 into an existing SAM environment and got the same results.
Thanks, good to know.
I have an open support ticket now so we'll see what comes of that.
If I can, I'll post the results back here.
Support seems to indicate it is due to the DB being heavily fragmented and the query timing out. I do notice that if I run the search on specific fields rather than the default "All Fields" it does work. The default query also (to my mind) seems to be quite long. Not sure if it changed in the 3.1 upgrade or not.
I am also working with one of our DBA's to see what we can do about setting up more regular automated DB maintenance.
-Rob-
Some further information on this that we have found.
Our DBA has found that an odd select statement is appended to the SQL query if "All Fields" (default) is left selected. If even one entry is removed, this addition is not added and the query runs fine.
Will pass this on to support asap.
