Oracle crash
Due to "out of shared pool space". Shared pool is used, among other things, to cache recent queries so that they can be reused. Non optimal queries in the DataQualityMonitoring application seem to have been responsible for this. The queries were fixed immediately.
We learned that we have to e-mail db-admin.
- Learn to use GRIDControl, an insanely complicated tool to monitor Oracle. We can use it to find out what queries are heavier on the system and ways to optimize them.
- RAC system: Real Application Clusters. For load balancing and fail over.
Web Server Crashes
There were a few (5?) crashes of the web server on which the DataQualityMonitoring application is deployed. All due to the server running out of memory.
Things we need to fix afterwards
- Stop using SLACDEV database
- Rationalize use of Dev/prod etc, decide if we need other configuration options
- Remove duplication between data processing page and other apps
- Improve data catalog interface especially for real data
- Get Warren to create groups rather than folders
- Look at GUI for data catalog
- Get Data Server tied into L1Proc
- Get portal working, at least for items like data processing page, grb summary etc
- Generate RSS feeds from LogWatcher, Ops Log, etc to display on portal page
- Look into tomcat clustering
- Ability to monitor all tomcat servers/applications from one page (and maybe restart them)
- Figure out why automatic generation of tomcat configuration on glast-win01,02 did not work
- Integration between monitoring tools and Ops Log
- Ability to move plots to ops log and comment on them
- Ability to find all recent comments on a plot
- Make Ops Log use same login system as everything else
- Cross App trending
Overview
Content Tools