Skip to main content

New cool Quest Tools

Yesterday evening guys from Quest presented their latest cool new tools at one of our company locations. They started with Foglight, a tool for Application Management. Using that tool you can see on one page the status of the applications that are running, where users experience some problems (based on thresholds), the number of users affected and where in the application stack the problem occurs. With a few clicks you can drill down to the actual origin of the problem. Foglight supports a number of application types (like Java, .Net, Siebel, SAP), different types of access (o.a. Apache, Citrix, Rich Clients), multiple infrastructures (Windows, Solaris, HP/UX, VMWare) and different databases (SQL Server and - of course - Oracle).
Foglight uses so called "Quest Collectors" on the web-, application- and databaseservers to sample data. That data is collected in the Foglight Management Server. Apart from that you can use an Experience Monitor and Viewer as a network sniffer.
Quest claims it is an end-to-end performance management tool, but actually the scope is somewhat limited to "just" the servers: storage is not included and for network management there is only a diagnosis and no suggested solution.
Foglight is complementary to Spotlight that has been around much longer. Spotlight is also a very nice graphical tool, but is - much more - limited to only one database instance.
Of course everything has it's price. This cool tool costs around 500 euro per CPU socket. A 'normal' implementation will cost you 20 - 200 kEuro (+ 18% support fee a year).
Also some new features of good old TOAD (v10) where addressed, like the enhanced ER Diagrammer, a new sort of Data Grid (with grouping, colors, hide/display columns etc.), an enhanced Data Generator - that can generate sample data with taking care of referential integrity and Unicode support. All the details are on www.toadworld.com.
The last product they showed was Foglight Performance Analyzer, a tool that has overlapping functionality with AWR, ASH and ADDM (but then without the Oracle Diagnostic and Tuning Packs license). The analyzer uses a StealthCollect memory tool to detect changes to the Oracle memory stack (without having an Oracle connection!) and offloads these changes to a data warehouse. So you can analyze and query the use and changes of your Oracle DB, without actually using the DB itself. Also tracking errors or dumps when the database itself is down is a nice functionality.
All in all a nice informative evening, with lots of tools that I definitely would like to try in a real environment (now I have to find a customer who uses or needs this sort of stuff).
Post a Comment

Popular posts from this blog

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…