• Blog
  • Get Help Now!
  • Customer Portal

BlueGecko Denmark

  • Why you need us
    • Why act now
    • Why are we unique
  • What we do
    • Products Supported 24/7
      • MySQL
      • Postgres
      • SQL Server
      • Open Source
      • OS & Storage
  • How we do it
    • Consulting
    • System Monitoring
    • Security
  • Support
    • Blog
      • Oracle
      • MySQL
      • News & Events
      • Oracle Applications
      • Amazon Web Services
      • Jeremiah Wilton’s Oradeblog
      • OurSQL Community Podcast
      • Remote DBA
    • Team viewer
    • Whitepapers
  • About Us
    • Philosophy
    • The Blue Gecko Teams
    • Employment Opportunities
    • Partners
    • News
    • Press
  • Contact Us

February 29, 2008 by Theis Riiber

Monocle – Can’t Sit Still

Well, it’s been a little over a week since we’ve made our monitoring tools available to the open source community.  It’s always a bit interesting to take something used internally and try to package it in such a way that it will be useful to others.   I hope those of you who have downloaded Monocle have had an opportunity to install it and perhaps even give it a run!  If you have questions, please don’t be shy!

Great news!

In a week or two we’ll be releasing version 1.1 of Monocle, (we’d hate to be accused of possessing “idle hands”.)  We’re particularly excited about this release as it integrates Oracle’s dbms_server_alert technology with Monocle, (dbms_server_alert technology is the same technology used by Oracle’s Grid product.)  The good news is you’ll have over 100 new things you can monitor using Monocle/Nagios. The bad news is…  you’ll have over 100 new things you can monitor using Monocle/Nagios!  In all seriousness, depending on your situation there are probably a dozen or so of these new dbms_server_alert things you’ll want to pay attention to.  Examples of some things you might choose to monitor are:

  • Library Cache Hit Ratio – If this is low, you may need to bump up the library cache.
  • Avg. No. Users Waiting On Concurrency – If this is high you may be experiencing latching and/or locking issues.
  • Shared Pool Free Pct. – If this is low, you may be headed for the dreaded 4031 – unable to allocate memory error!
  • Process Limit Pct – If you’re close to 100% you’ll need to increase “processes” in the init.ora.
  • Long Table Scans – Doing a lot of these?  You may have some sql to tune!
  • Hard Parses Per Second – If this is high, you may have an issue with bind variables.

… and so I’m sure, you get the picture.

Whoops!!!

If you’re running a version of Oracle 10.1 there’s a small bug you should know about:

The job monitor won’t compile in Oracle 10.1  You can fix this by editing the package bg_job_monitor.pkg.

Replace:

, dsj.schedule_type

With:

, NULL as dsj.schedule_type

Of course the above will be fixed in version 1.1.

Cheers!

-Ed

Related posts:

  1. Monocle – Open Source Oracle Monitoring
  2. System Monitoring
  3. Community

Filed Under: Monocle, Oracle Tagged With: database monitoring, monitoring, system monitoring

Categories

  • Amazon Web Services
  • Configuration Management
  • downtime
  • Drizzle
  • ebs
  • Education
  • elastic block store
  • elastic compute cloud
  • hosting
  • hot backup
  • ignorance
  • Infrastructure
  • IOUG
  • Jeremiah Wilton's Oradeblog
  • misconception
  • misconceptions
  • Monocle
  • MySQL
  • MySQL Council
  • News
  • News & Events
  • Oracle
  • Oracle APEX
  • Oracle Applications
  • Oracle Data Guard
  • Oracle Database
  • Oracle Database Appliance
  • Oracle Linux
  • Our People
  • OurSQL Community Podcast
  • outage
  • parallel
  • performance
  • podcast
  • proof
  • Remote DBA
  • replication
  • S3
  • Security
  • SQL Server
  • System monitoring
  • Tomcat
  • Uncategorized

Contact Blue Gecko

  • This field is for validation purposes and should be left unchanged.

Get Our Newsletter

  • This field is for validation purposes and should be left unchanged.

The Fine Print

  • Privacy Policy
  • Terms of Use
  • When is remote DBA the right solution
  • What are remote DBA services
  • Get Help

Virtual runs

Blog Categories

  • 24/7 support
  • Blue Gecko 360° Services
  • Products Supported 24/7

Contact Blue Gecko

Blue Gecko A/S
Slotsgade 21
DK – 4200 Slagelse
Denmark
Phone: (DK) +45 70 60 51 20

Networks

  • Email
  • Twitter

© Blue Gecko Group