A customer was experiencing frequent instances where the database would not accept any new logons and existing logons were unable to do anything. I would remote into the server and also could not log into the db using sc. Nothing in event logs. I had not yet tried an -o option startup. If I think (with wishful thinking) that this problem may have been solved in a later build, how do I search for that possibility? Like most supporting sqla, I have a dozen other issues in the queue and can take very long on the search. Do I take a shot in the dark and just apply the latest ebf? In fact, I did just that: applied 2331. But the question remains... How does one quickly and throughly search for a corrected problem?
asked 25 Mar '10, 14:18
What I did in a similar case is: download the readme file for the latest EBF, e.g rdme_1101_ebf_2376.html. Set the filter to show all changes since the version in use (11.0.1578 in one case), and than scan it for topics with keywords describing the problem area.
answered 25 Mar '10, 15:54
I find just text searching the latest readme from the top reasonably easy. Maybe we should persuade iAnywhere to put the EBF change log in a database?
What would be really nice would be decent filters on the EBF list (eg by OS and major version number) and some sensible ordering with the most recent and widely used combinations at the top rather than the bottom where they are now.
answered 25 Mar '10, 16:47