DBAmon
Change History

Home | Index/DBAmon Doc. | DBAmon Version/Change History | DBAmon Event/Error Doc. | What DBAmon Monitors | DBAmon Download | Free Oracle Tool: orastat | Request Support

DBAmon - Change/Enhancement/Bug Fix History - In Reverse Chronological Order

Version Release Pgmr. Date Description of Changes
5.57
5.57 E   21Jul17 Enhancements:
  • (MSSQL) New event DBA808 for CheckDB Age is now completely enabled.
    Fixes:
  • (MSSQL) There was an issue where after an inhibit period, we would always get a DBA801 event. This was because readDBCFile was using the wrong probe file name which meant that DownloadSWWin was being depended on to correct that file name. Fixed.

  • 5.57
    5.57 C   17Jul17 Enhancements:
  • (MSSQL) New monitor for CheckDB Age and new DBA808 Event. For now the threshold of 8 days is hard-coded - someday I will create a new DBC parameter for this.
  • (MSSQL) The DBAmon.Instances metadata table now has 2 new columns: Title1 and Title2. These are populated from the DBC values that you specify

  • 5.57
    5.57 B   14Jul17 Enhancements:
  • (MSSQL) New T_Disk_Full_Override parameter which allows you to specify a different Drive Full threshold for select disk drive(s).

  • 5.57 A   11Jul17 Enhancements:
  • (All) Some formatting changes to the Instance Summary page - to reduce the height of each row.
  • (All) A read-only copy of the Notepad is now displayed on each Instance Drill-down page.
  • (MSSQL) Rewrite of how we connect to MSSQL on the local (target) server. Now, we find the best ODBC driver (preferring ODBC SQL Server* drivers) and connect with Trusted_Connection=Yes. This solves some problems where the old, unintelligent SQL Server driver could not live without TLS 1.0.

  • 5.56
    5.56 G   31May17 Enhancements:
     


    Fixes:

  • (MSSQL) The new probe query to count tables and rows in 5.56.F used sysindexes, which was a mistake (it can block despite NOLOCK). We now use sys.dm_db_partition_stats.
  • 5.56 F   21May17 Enhancements:
     
  • (MSSQL) New performance metrics for the total number of user tables, their total row count and total size (GB). This will allow you to track the historical values of these metrics for your instances. These values are displayed on the Instance Summary page near the MSSQL version information.
  • (All) Some minor Instance Summary WWW page aesthetic improvements.


    Fixes:

  • (MSSQL) On the Instance Summary WWW page, the color in Current Readings was incorrect for Disk I/O response time.
  • 5.56 E   02May17

    Enhancements:

  • (MSSQL) (Event DBA850) How shows, in the event short text, details such as TotSizeMB TotMaxSizeMB, etc..
     
      Fixes:
  • (MSSQL) For MSSQL DB files that are >2TB (size or maximum size), the MSSQL system stored procedure (sp_helpfilegroup) that we were using would fail (arithmetic overflow). So I now query SYS.Database_Files instead of using sp_helpfilegroup.
  • 5.56 D   19Apr17

    Enhancements:

  • (MSSQL) Previously, DBAmon performed a drive space check (the T_Disk_Full: DBC parameter) for all server drives which contain at least one DB file + the C: drive. Now DBAmon will additionally check the drive which contains the BackupFolder MSSQL install option.
  • (MSSQL) All TLog Full DBAmon events (Event DBA657) will now display the current Log_Reuse_Wait_Desc value from Sys.Databases. This should help in the diagnosis of TLog full events.
     
      Fixes:
     
  • 5.56 C   14Mar17

    Enhancements:

  • (MSSQL) A new local event: DBA902.
     
      Fixes:
  • (MSSQL) The Full DB Backup Age event has been fixed to not occur on an AlwaysOn Async replica.
  • 5.56 A   03Mar17

    Enhancements:

  • (All) The font size for the WWW page headers has been reduced. It was annoyingly large previously.
  • (All) The Outstanding Events page now is set to 120 second auto-refresh. We use this on a publically placed TV monitor to show the details of our instances' current events.
  • (MSSQL) Trying this as an experiment: We have some restored DBs that will never be changed again. We want to shrink them down before placing them in read-only mode to conserve space. Well, annoying DBAmon was giving us Space events for these DBs. So, starting with this version we won't monitor space vs. thresholds for RO DBs. I'll see if this causes any intolerable new problems.
     
      Fixes:
  • (MSSQL) This is a difficult changed, but added logic to better tolerate DBs that in restore/recovery mode. More to come on this.
  • 5.55
    5.55 F   18Feb17

    Enhancements:

  • (MSSQL) The DBAmon probe now sets LOCK_TIMEOUT=10000.
     
      Fixes:
     
  • 5.55 E   06Dec16

    Enhancements:

  • (MSSQL) We now expose a new variable $copssh_version[$thishost] to user exits.
     
      Fixes:
     
  • (MSSQL) The Full Backup Age event should have been suppressed for AO Replicas in Async mode. Fixed.
     
  • 5.55 D   04Dec16

    Enhancements:

  • (All (Windows)) We were required by our Security people to upgrade our SSH Server software on all DBAmon targets. Previously we were using CopSSH version 3.1.4. The CopSSH people (who offer a very good product at a good price) do still offer a free version of CopSSH - currently version 5.4.21. After my initial testing, it still works well with DBAmon, but their free offering currently does not offer multi-threading (I don't blame them for that at all). So, this version of DBAmon does include some code work-arounds if you're using this new version of CopSSH. Simply put, we do have to now do a few "sleep 2"'s in DBAmon to allow CopSSH to go back into listen mode, before issuing another probe (SSH command) against the same target. If this delay becomes problematic, I can make this more sophicticated as some future date.
  • (All) The default value for the Remsh_Sleep: DBAMONRC value has been changed from 60 to 5.
  • (MSSQL) New TempDB Space Monitoring. We now query tempdb.sys.dm_db_file_space_usage to instantiate the new DBAmon Performance Metrics:
    PERF_SQL_TEMPDB_SPC_ALLOC_MB 
    PERF_SQL_TEMPDB_SPC_INTOBJ_MB 	
    PERF_SQL_TEMPDB_SPC_MIXEDEXT_MB 	
    PERF_SQL_TEMPDB_SPC_TOTSIZE_MB 	
    PERF_SQL_TEMPDB_SPC_UNALLOC_MB 
    PERF_SQL_TEMPDB_SPC_USEROBJ_MB 	
    PERF_SQL_TEMPDB_SPC_VERSTORE_MB

      Fixes:
     
  • 5.55 C   15Nov16

    Enhancements:

  • (MSSQL) Preliminary support for MSSQL 2016. Just a few label and test changes for now. More to come ...
  • (MSSQL) There is now a quick URL on the Summary page for Reserved space.
     
      Fixes:
     
  • 5.55 B   01Nov16

    Enhancements:

  • (MSSQL) We recently had some Performance / Connectivity challenges with a very busy MSSQL instance. The problem turned out to be Worker Thread Exhaustion, so we how have some new MSSQL AlwaysOn DBAmon Performance Metrics:
    PERF_SQL_WORKERTHREADS_CONFIG_MAX 
    PERF_SQL_WORKERTHREADS_INIT_CNT 
    PERF_SQL_WORKERTHREADS_RUNNABLE_CNT 	
    PERF_SQL_WORKERTHREADS_RUNNING_CNT 
    PERF_SQL_WORKERTHREADS_SICK_CNT 
    PERF_SQL_WORKERTHREADS_SUSP_CNT
    PERF_SQL_WORKERTHREADS_TOTAL_CNT 	
    PERF_SQL_WORKERTHREADS_TOTAL_PCT 
    The bottom line: If the total number of worker threads (PERF_SQL_WORKERTHREADS) ever reaches the maximum number of worker threads, you will have problems, which would also be indicated by THREADPOOL waits. If this happens, you can either increase "max worker threads" in the MSSQL engine, or increase CPUs which would allocate more worker threads (this happens for the default which is 0).
     
      Fixes:
     
  • 5.55 A   14Oct16

    Enhancements:

  • (MSSQL) New checking of the MSSQL Error log for this error (the total count is stored in new DBAmon Performance Metric: PERF_SQL_DTC_FAILED_NOTRANS_EVENTS):
    Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: 0x8004d00e(XACT_E_NOTRANSACTION).  
  • New MSSQL AlwaysOn DBAmon Performance Metrics:
    PERF_SQL_AO_MIN_LASTREDONELAG_SEC 	
    PERF_SQL_AO_TOT_REDOQUEUERATE_KBSEC 
    PERF_SQL_AO_TOT_REDOQUEUESIZE_KB 
    PERF_SQL_AO_TOT_SENDQUEUERATE_KBSEC 
    PERF_SQL_AO_TOT_SENDQUEUESIZE_KB 

      Fixes:

  • (MSSQL) When counting Remote NTLM sessions, I was not properly excluding local SSMS sessions. Fixed.
  • (MSSQL) On some servers, the WMINetPerf routine runs for around 2 minutes. For now, this routine will only run between the hours of 00 and 02. I want to find a better way to address this, but this will help.

  • 5.54
    5.54 C   30May16

    Enhancements:

  • (All) Increased the width of the CATEGORY column of the Metrics tables from 64 to 255.
  • 5.54 B   03Apr16

    Enhancements:

  • (MSSQL) If I may say so, this is really Cool! (and I rarely use exclamation points). A new Snapshot report of the top 5 MSSQL Waits, where the Wait Type is clickable to a Google Search for that wait type.

  • (MSSQL) Thanks to our brilliant friends at SQLSkills, I updated the SQL Idle Waits list (this was long overdue).

    Fixes:

  • (All) On the WWW Summary page, the URL test for the Per, Snap, etc. pages was unreadably microscopic. Font size increased 1 point.

  • 5.54 A   20Mar16

    Enhancements:

  • (MSSQL) Better AlwaysOn cluster monitoring. If the cluster's Sync Health is other than HEALTHY, then the new Event DBA710 will occur.

    Fixes:

  •  

  • 5.53
    5.53 L   26Dec15

    Enhancements:

  • (MSSQL) SQL Error 35262 was added to the "Exclude List" (AlwaysOn Failover - Non-Actionable).

    Fixes:

  •  

  • 5.53 K   28Nov15

    Enhancements:

  • (All) Some aesthetic improvements to the WWW Summary page.

    Fixes:

  • (MSSQL) The WWW Summary page had 2 URLs too close together. Fixed.

  • 5.53 J   07Nov15

    Enhancements:

  • (MSSQL) New checkCDNS and checkCDRJ routines were added to the probe.

    Fixes:

  •  

  • 5.53 I   07Nov15

    Enhancements:

  •  

    Fixes:

  • MSSQL: Wording change for Event DBA200 (FG with NoGrow Files).
  • MSSQL: Logic error in probe for DBs with files set to nogrow.

  • 5.53 G   13Sep15

    Enhancements:

  • OSWIn: Disk drives with a VolumeName maching /pag/i are now excluded.

    Fixes:

  •  

  • 5.53 F   23Aug15

    Enhancements:

  • MSSQL: New Performance metrics for each Disk Drive: Size, Used, Free, PctFull. The metrics are named: SPC_Disk_FreeGB, SPC_Disk_UsedGB, SPC_Disk_FreeGB, SPC_Disk_PctFull.

    Fixes:

  •  

  • 5.53 D   15Aug15

    Enhancements:

  • All: New DBAmon Genesis date is displayed on summary page. This is the date of the old history row for this instance.
  • All: Some minor aesthetic changes to the Summary WWW page to improve readability.

    Fixes:

  •  

  • 5.53 C   06Aug15

    Enhancements:

  • MSSQL: When reading the MSSQL Error Log, we will now skip over all messages that contain the string "No user action is required". These are common for AlwaysOn clusters.

    Fixes:

  •  

  • 5.53 A   05Jul15

    Enhancements:

  • All: There is now an Event Snooze capability. For Any DBAmon event, if you click on the Event Log page, below the details for every event, you will see a URL which allows you to snooze an event. You will be prompted for the beginning and end of the snooze period. During the snooze period, there will be no event notifications performed for this event on this instance.
  • MSSQL: New SA Login monitoring. We now monitor the number of concurrent SA Logins over the last 24 hours. If the value exceeds the new The T_SA_Logins_Max: DBC Parameter then an Event DBA961 will occur.
  • All: The WWW_Event_Isolate: parameter is now obsolete. Now, all event are included in the Event Isolation report (at the bottom of the WWW Instance Summary page).

    Fixes:

  • All: The DBI LongReadLen parameter was changed from 16000 to 40000 due to a problem with dbamon_mssql_sumread.pl.

  • 5.52
    5.52 A   18May15

    Enhancements:

  • MSSQL: New detection and warning event for the presence of any MSSQL DBs in SINGLE_USER mode.
  • (MSSQL) New inc_event DBAmon User Exit. For more information see: DBAmon Userexits .

    Fixes:

  • MSSQL: A DB in SINGLE_USER mode used to cause the probe to fail. Fixed.

  • 5.51
    5.51 J   29Apr15

    Enhancements:

  • MSSQL: More laying of tracks for some upcoming RJ monitoring.

    Fixes:

  •  

  • 5.51 I   16Apr15

    Enhancements:

  • MSSQL: Laying the tracks for some upcoming RJ monitoring.

    Fixes:

  •  

  • 5.51 H   09Mar15

    Enhancements:

  •  

    Fixes:

  • MSSQL: The Signal Wait var was not being cleared which caused some erroreous events when a new DBC is dynamically added.
  • MSSQL: Improved the RJ Performance Metrics.

  • 5.51 G   04Feb15

    Enhancements:

  •  

    Fixes:

  • MSSQL: Added QDS_CLEANUP_STALE_QUERIES_TASK_MAIN_LOOP_SLEEP to ignorable waits.

  • 5.51 F   01Feb15

    Enhancements:

  •  

    Fixes:

  • MSSQL: Some minor changes were made to the SQLPERF_RJ* Performance Metrics.

  • 5.51 E   28Jan15

    Enhancements:

  •  

    Fixes:

  • MSSQL: The Auto-Reorg check now correctly excludes REPORTSERVERTEMPDB for named instances.

  • 5.51 C   09Jan15

    Enhancements:

  •  

    Fixes:

  • The extraction of a servers IP address (MSSQL) was incorrect. It has now been corrected to use the first IP address that it finds when running ipconfig .

  • 5.51 B   01Jan15

    Enhancements:

  •  

    Fixes:

  • This release will alter the MODEL column of the INSTANCES table from CHAR(16) to VARCHAR(64).

  • 5.51 A   27Dec14

    Enhancements:

  • (MSSQL) New Backup Age checking improvements for MSSQL instances running AlwaysOn.
    Here is how this will work to begin with (this will evolve over time): If the AlwaysOn Backup preference "Prefer Secondary" is ON, then DBAmon will only perform Backup Age checking on the Secondary instance.
     
  • (Sesame Software Relational Junction (RJ) Monitoring)
    DBAmon now monitors for successful execution of RJ replication. See: DBAmon Monitoring of RJ for additional information.

    Fixes:

  •  

  • 5.50
    5.50 J   04Dec14

    Enhancements:

  • (MSSQL) The performance metric PERF_SQL_TEMPDB_IOBALANCE_PCT gives some wild values at times. The logic was changed to cap this value at 250.
  • (MSSQL) Event DBA862 which checks to ensure that you're not running with a non-default Replication Distribution Profile now only looks for the name of the profile staring with the string default. This is a slightly mickey-mouse, but you cannot change the values in the default profile - so a customer needs to have a much higher login timeout value, so they are forced to not use the default profile. So, they can now create a new profile, whose name begins with default and this event will still be in effect.

    Fixes:

  •  

  • 5.50 I   27Oct14

    Enhancements:

  • (MSSQL) New sqlUp.pl variable $windows_domain[$thishost] . This will allow the sqlup user exit to set IDn variables from the target's Windows domain.

    Fixes:

  •  

  • 5.50 H   22Oct14

    Enhancements:

  • (MSSQL) SQL Error Log event 8510 is now excluded.
  • (MSSQL) New Event DBA951 event which measures the number of days since the last Auto-Reorg/Reindex for each MSSQL database.

    Fixes:

  •  

  • 5.50 G   16Sep14

    Enhancements:

  • (MSSQL) In addtion to existing performance metric PERF_SQL_SESSIONS_NTLM_REMOTE, there is now a metric for KERBEROS and SQL connections.
  • (MSSQL) A new Snapshot report of the top 5 OS memory consuming processes.
  • (MSSQL)  

    Fixes:

  •  

  • 5.50 F   03Sep14

    Enhancements:

  • (MSSQL) Support for MSSQL 2014, as a target or the home of the DBAmon Repository.

    Fixes:

  •  

  • 5.50 E   30Aug14

    Enhancements:

  • (MSSQL) The DBA813 event (DB Full Backup Age) has been changed to issue just one event per instance (previously there was one event for each database).
  • (All) The Backup Age Inhibit WWW transaction has been enabled. It allows you to inhibit backup age checking just as Inhibit prevents all DBAmon monitoring.

    Fixes:

  •  

  • 5.50 D   16Aug14

    Enhancements:

  • (MSSQL) For instances with Pager enabled or High or Low Priority specified, there is now a new (improved) icon immediately below the instance name on the WWW Summary page. This will make it easier to see that an instance has paging enabled.

    Fixes:

  • (MSSQL) Changed the text of DBA657 event to show only the integer value (no decimal places). This will result in fewer events (and event notifications) for an instance where a TLOG is gradually filling.

  • 5.50 C   03Aug14

    Enhancements:

  • (MSSQL) New Security Event: PERF_SQL_SESSIONS_SA. This is the number of sessions where the login is SA and the SPID is > 50. We should routinely be using the SA login, so this metric will give us visibility to the extent to which this is occuring.

    Fixes:

  • (MSSQL) The PVSCSI Controller metric was showing as null. Fixed.

  • 5.50 B   26Jul14

    Enhancements:

  • (MSSQL) The SaveConfig capability now captures information on all MSSQL backups taken during the last 10 days.
  • (MSSQL) Changed the Last 30 Days Average IO/Sec rate for event DBA960 (VMware PCSCSI Controllers) from 100 to 200 IO/Sec.
  • (MSSQL) A new check for MSSQL Services. With this new Event DBA817 DBAmon check for all Windows services whose name contains the string SQL. If any are found to be set to AUTOSTART but are not current running, this event will occur. This closes a hole in DBAmon where it did not previously check for SSRS, SSAS, SSIS, etc. not executing (if the service is set to AUTOSTART).
  • (MSSQL) New Performance Counters (this is from dbamon_mssql.cfg):
    PERFCOUNTER |SQLSERVERPREFIX:Databases(_total)\Log Growths|SQL_TLog_Growths_SIS|
    PERFCOUNTER |SQLSERVERPREFIX:Databases(_total)\Log Shrinks|SQL_TLog_Shrinks_SIS|
    PERFCOUNTER |SQLSERVERPREFIX:Databases(_total)\Log Flushes/sec|SQL_TLog_Flushes_PS|
    PERFCOUNTER |SQLSERVERPREFIX:Databases(_total)\Log Flush Waits/sec|SQL_Tlog_FlushWaits_PS|
    

    Fixes:

  • On the Performance page, metrics were not sorted properly. I now do a case-insensitive sort.

  • 5.50 A   24Jun14

    Enhancements:

  • (MSSQL) New Projected MSSQL Instance Growth Report . To run this report, choose the Pro report from the WWW Summary Page. It projects the size of the DB Instance 10 years into the future, using the current growth rate.
  • (Windows) New Windows OS monitoring. You can now specify DBMS: OSWin in a DBC file. It is just the MSSQL probe minus all DBMS logic. More to come.... It is useful to us to capture the Windows Performance Counters and WMI Metrics.
  • (MSSQL) Some aesthetic improvements to the WWW Summary Page. The transactions are now grouped by category:
  • (MSSQL) DBAmon now captures Row Versioning metrics from the SQLServer:Transations Performance Counter class:

    Fixes:

  • (None)

  • 5.49
    5.49 E   10Jun14

    Enhancements:

  • (All) A significant enhancement was made in how UX (Cygwin in this case) task serialization occurs. Previously, a task would check for a previously executing iteration of itself by running "ps". This was inefficient and caused problems when Cygwin was having internal task problems (hung processes). Now, all task serialization is done with file locks using a new routine &serializeMe. While this is not rocket science, it cleans up this area of DBAmon, which was always messy.

    Fixes:

  • (All) DBAmon was not handling long-running non-DBAmon UX tasks correctly. Fixed.
  • (All) The alert threshold for dbamon_watchdog was changed from 120 minutes to 180. This will eliminate some false alarms.
  • (All) All reading of the dbamonrc is done with Perl file access and not grep!.

  • 5.49 D   01Jun14

    This was an internal-only testing release.

    5.49 C   14May14

    Enhancements:

  • (MSSQL) Improvements were made to SSRS monitoring, including a check for failed reports (since the last DBAmon iteration). The new DBAmon Event DBA933 has details of which reports have failed.

    Fixes:

  •  

  • 5.49 B   09May14

    Enhancements:

  • (MSSQL) New MSSQL on VMware monitoring to track which instances (1) Would benefit from multiple PVSCSI Controllers and (2) Have less than 2 PVSCI Controllers. The new DBAmon Event DBA960 has details of what is monitored and some helpful URLs.

    Fixes:

  •  

  • 5.49 A   14Apr14

    Enhancements:

  • (MSSQL) New SSRS (Reporting Services) Monitoring. See DBAmon SSRS Monitoring for details. We now collect metrics on these MSSQL/SSRS Windows Performance Counters:
    
    PERFCOUNTER |\ReportServer:Service\Memory Pressure State|SSRS_Mem_Pressure_State|
    PERFCOUNTER |\ReportServer:Service\Memory Shrink Amount|SSRS_Mem_Shrink_Bytes|
    PERFCOUNTER |\ReportServer:Service\Tasks Queued|SSRS_Tasks_Queued|
    PERFCOUNTER |\ReportServer:Service\Active Connections|SSRS_Active_Connections|
    PERFCOUNTER |\ReportServer:Service\Bytes Received/Sec|SSRS_Bytes_Rcvd_PS|
    PERFCOUNTER |\ReportServer:Service\Bytes Sent/Sec|SSRS_Bytes_Sent_PS|
    PERFCOUNTER |\ReportServer:Service\Errors/Sec|SSRS_Errors_PS|
    PERFCOUNTER |\ReportServer:Service\Errors Total|SSRS_Errors_Tot|
    PERFCOUNTER |\ReportServer:Service\Requests Executing|SSRS_Reqs_Executing|
    PERFCOUNTER |\ReportServer:Service\Requests Not Authorized|SSRS_Reqs_AuthFail|
    PERFCOUNTER |\ReportServer:Service\Requests/Sec|SSRS_Reqs_PS|
    PERFCOUNTER |\ReportServer:Service\Requests Total|SSRS_Reqs_Total|
    PERFCOUNTER |\ReportServer:Service\Requests Rejected|SSRS_Reqs_Rejected_503|
    
    (This is an excerpt from the "dbamon_mssql.cfg" DBAmon Configuration file.)
     
  • (MSSQL) New SSRS ExecutionLog2 retrieval. In the drilldown WWW section for each instance that is running SSRS (has the ReportServer..ExecutionLog2 table) DBAmon now displays the most recent 100 rows.
  • (MSSQL) We now display Plan Cache statistics as MSSQL Metrics:
     
  • (MSSQL) New MSSQL_Addtl_Drives: DBC Parameters which allows you to specify additional disk drive letters to monitor.

    Fixes:

  •  

  • 5.48
    5.48 G   29Mar14

    Enhancements:

  • (MSSQL) DBAmon now collects detailed statistics on the MSSQL Buffer Cache. These are instantiated as DBAmon Performance Metrics: PERF_SQL_BUFFERCACHE_MOD_PAGES PERF_SQL_BUFFERCACHE_PAGES PERF_SQL_BUFFERCACHE_ROWS PERF_SQL_BUFFERCACHE_SPACE_MB .

    Fixes:

  • Added retry logic to a problem with dbamon_mssql_sumread.pl where it was failing with open error on detpath.

  • 5.48 F   28Feb14

    Enhancements:

  • (MSSQL) New diagnostic messages in the Instance Log files to diagnose a possible performance... opportunity.
  • (MSSQL) The MSSQL_Repl_Lag_Excl_String: DBC Parameters has been changed to allow the specification of multiple comma-delimited strings.

    Fixes:

  • (MSSQL) Databases in an OFFLINE or RESTORING state were not being handled properly. Fixed.

  • 5.48 E   09Feb14

    Enhancements:

  • (All) New Notation Event DBA980 . This occurs when the DBAmon monitor duration exceeds whatever you set in the DBAMONRC Default_Instance_Dur_Max_Secs: parameter. For instance, if you set Default_Instance_Dur_Max_Secs: to 30 and the amount of time that it take DBAmon to monitor an instance is >= 30 seconds, then the DBA980 Notation Event will occur. This was done so that we could improve monitoring for instances that are taking too long to monitor. Additonal instrumentation was also added to the engine, to better diagnose these issues.

    Fixes:

  •  

  • 5.48 D   09Feb14

    Enhancements:

  • (MSSQL) New Space metrics:

    Performance:
      PERF_SQL_TOT_SPACE_ALLOC_MB
      PERF_SQL_TOT_SPACE_INDEXES_MB
      PERF_SQL_TOT_SPACE_OBJECTS_MB
      PERF_SQL_TOT_SPACE_RESERVED_MB
      PERF_SQL_TOT_SPACE_TABLES_MB
      PERF_SQL_TOT_SPACE_UNUSED_MB
      PERF_SQL_TOT_SPACE_USED_MB

    Space:
      SPC_TOT_INDEXES_MB (All databases)
      SPC_TOT_OBJECTS_MB (All databases)
      SPC_TOT_RESERVED_MB (All databases)
      SPC_TOT_TABLES_MB (All databases)
      SPC_TOT_UNUSED_MB (All databases)

    Fixes:

  • (MSSQL) Snapshot database space metrics were published along with non-Snapshot databases. Fixed.

  • 5.48 C Bill Border 05Feb14

    Enhancements:

  •  

    Fixes:

  • (All) Fixed problem caused by increased length of Title1:.
  • (MSSQL) There was a problem in the logic to check MSSQL Filegroups when there is a Snapshot DB. Now Snapshot DBs are excluded from the Filegroup full check.

  • 5.48 A, B Bill Border 19Jan14

    Enhancements:

  • (All) No impact - Some logic was added that will pave the way for DBAmon to be able to use different probe frequencies for different instance priorities. More to come on this in the future.
  • (All) The Title1: DBC Parameter may now be up to 20 characters in length. This is an improvement over the previous limit of 16. Having said that, we need to eliminate limitations in general.

    Fixes:

  •  

  • 5.47
    5.47 H Bill Border 04Jan14

    Enhancements:

  • (MSSQL) There is a new Metrics report: Spc available for every instance. This report will create a menu of all Space-related metrics (detail and summary).
  • (MSSQL) New performance metrics for all drives that contain SQL DB files. Previously, only summary disk metrics were created. Now, these same metrics are reported at the drive level.

    Fixes:

  •  

  • 5.47 G Bill Border 16Dec13

    Enhancements:

  • (MSSQL) The DBAmon Lightbulb transaction has been cleaned up (which was long overdue). It now runs more quickly and the output is shorter.

    Fixes:

  •  

  • 5.47 F Bill Border 08Dec13

    Enhancements:

  • (MSSQL) Three new Performance Metrics: SQL_Jobs, SQL_Jobs_Enabled, SQL_Jobs_Disabled. This was done because we have an instance where the Maintenance Plan jobs tend to disable themselves during editing.

    Fixes:

  • (MSSQL) The Event History report had an inconsistent border setting. Fixed.

  • 5.47 E Bill Border 30Nov13

    Enhancements:

  • (All) DBAmon Event Notification EMail messages now contain a descriptive paragraph near the top of the email. The hope is that these will help to eliminate some confusion regarding DBAmon Event Severity.

    Fixes:

  • (MSSQL) There were some aesthetic spacing errors in the WWW Summary page. Fixed.

  • 5.47 D Bill Border 22Nov13

    Enhancements:

  • (MSSQL) For the LRC (Long Running Command) during Prime Shift check, the DBAmon logic has been changed to define Prime Shift as 8:00 - 5:00 on weekdays. It was defined at 07:00 - 5:00 previously.
  • (MSSQL) The probe now collects the "Work Shift" at the target server. This is displayed on the WWW Summary page.
  • (MSSQL) New Perf_Events_During_Shifts: DBC parameter which allows you to specify shifts ((P)rime, (W)eekend and (N)ight) during which Performance events are created. This is needed because there are often performance events that occur during nights and weekends, that only cause confusion - false positives. By default, this parameter is NULL, so Performance Events are created during all shifts. For example, if you specify this parameter as P, then Performance Events will only be sent during Prime shift.

    Fixes:

  • (MSSQL) The PERF_SQL_TOP_WAITS_RANKn performance metrics were not being saved in the DB (current or historical).

  • 5.47 B Bill Border 18Nov13

    Enhancements:

  • (MSSQL) Better support for SQL instances where the connection to LOCALHOST doesn't work.
  • (MSSQL) Initial support for Windows Server 2012 and 2012R2.

    Fixes:

  •  
  • 5.47 A Bill Border 28Oct13

    Enhancements:

  • (All) The Instance Summary WWW page has been cleaned up. No more tables with border=1, etc.
  • (MSSQL) We now capture the number of days that the Server has been up. The performance metric is PERF_SYS_SERVER_UPFOR_DAYS .

    Fixes:

  • (MSSQL) The Performance Metric PERF_SQL_SIGNAL_WAIT_PCT did not appear with the other instance performance metrics. Fixed.

  • 5.46
    5.46 I Bill Border 09Oct13

    Enhancements:

  • (MSSQL) New inc_sqlup_pre DBAmon User Exit. For more information see: DBAmon Userexits .
  • (MSSQL) The Signal Wait % is now also the performance metric: PERF_SQL_SIGNALWAIT_PCT .

    Fixes:

  •  

  • 5.46 H Bill Border 04Oct13

    Enhancements:

  • (MSSQL) New Performance Counters (this is from dbamon_mssql.cfg):
    PERFCOUNTER |SQLSERVERPREFIX:Memory Manager\Database Cache Memory (KB)|SQL_MemDBCacheKB|
    PERFCOUNTER |SQLSERVERPREFIX:Memory Manager\Free Memory (KB)|SQL_MemFreeKB|
    PERFCOUNTER |SQLSERVERPREFIX:Memory Manager\SQL Cache Memory (KB)|SQL_MemSQLCacheKB|
    PERFCOUNTER |SQLSERVERPREFIX:Memory Manager\Stolen Server Memory (KB)|SQL_MemStolenServerKB|
    

    Fixes:

  •  

  • 5.46 G Bill Border 28Sep13

    Enhancements:

  • (MSSQL) New SNAPSHOT reports for CPU consumers. If any Windows process is consuming at least 10% of a CPU, then a new CPU Consumers Snapshot report will occur. This will help to find who was using CPU during times of peak usage.

    Fixes:

  • (MSSQL) For performance events, only the critical threshold was being displayed, even if the warning threshold was exceeded. Fixed.
  • (MSSQL) checkTempDBContention was reinstated. The problem was a missing USE MASTER.

  • 5.46 F Bill Border 27Sep13

    Enhancements:

  •  

    Fixes:

  • A problem was discovered where the TYPEPERF command sometimes returns a different number of fields from the label line and the value line. Now, DBAmon will discard all performance counter values if the number of fields returned by TYPEPERF in the two lines differ.

  • 5.46 E Bill Border 08Sep13

    Enhancements:

  • (MSSQL) New Mutiple TLOG Files check. If a database is found to have more than 1 TLOG file, then the new User Event DBA946 event will occur. The reason for this check: if a DB is replicated, the LOG READER scans every TLOG file for changes. We were told by MS that having an unneeded 2nd TLOG file can slow down the LOG READER.

    Fixes:

  •  

  • 5.46 D Bill Border 04Sep13

    Enhancements:

  • (MSSQL) DBAmon now reads the number of processors from WMI, so an expensive and slow call to SRVINFO is eliminated.

    Fixes:

  •  

  • 5.46 C Bill Border 28Aug13

    Enhancements:

  • (MSSQL) DBAmon is now able to detect a new Backup Method of Red Gate SQL Backup Pro .
  • (MSSQL) Several new SQL and OS Performance Counters have been added.

    Fixes:

  • (MSSQL) The DMO query behind the new metric PERF_SQL_TEMPDBCONTENTION was giving a syntax error on some SQL2008R2 instances. The sub which runs this query has been disabled until I can resolve the issue.

  • 5.46 B Bill Border 21Aug13

    Enhancements:

  •  

    Fixes:

  • The metric PERF_SQL_TEMPDB_IOBALANCE_PCT metric has been altered to only produce a value if there at least 5000 TEMPDB writes since the instance was started. This will eliminate some bogus exceptions.

  • 5.46 A Bill Border 17Aug13

    Enhancements:

  • (All) New SLA: DBC parameter. It is also possible now to specify the new DBAMONRC T_SLA: parameter. The SLA value for an instance will be passed to the Ticket and Pager userexits. If this is specified, it is displayed prominently way on the Instance Summary WWW page.

  • (MSSQL and eventually ALL) Most Events now will contain a new string "EvCat" to show the "Event Category". This will help us to properly classify events and specifically, it will allow us to decide whether to PAGE or TICKET for a category of events. For example, we may want to PAGE (in the pager userexit) for EvCat=Repl events, but not for EvCat=Space events. Now, the email subject line will look like:
    DBAmon | localhost_MSSQL2 (EvCat=Perf) | DBA852P: === sqlPerf() MSSQL_Perf_Metric SYS_MemUsedPct=49 - GE CriticalThreshold=41 === [AUTO]
  • (MSSQL) New TempDB I/O Balance performance metrics. These (3) metrics show the degree of I/O imbalance with your TempDB DB files. If you size your TempDB DB files so that the sizes are not equal, there will be an I/O imbalance.
  • (All) 10 new IDn fields have been added to the DBC file, so now you can specify ID11: through ID20:. Note that you must DROP the DBAmon tables:
    • DBAMON.EMAIL
    • DBAMON.INSTANCES
    • DBAMON.SUMMARY_DETAIL
    DBAmon will automatically recreate them the next time that DBAmon is started, with the new columns.

    Fixes:

  •  

  • 5.45
    5.45 G Bill Border 11Aug13

    Enhancements:

  • (MSSQL) New Performance Metric PERF_SQL_TEMPDBCONTENTION_(pagetype). This metric counts the number of sessions (if any) waiting on TEMPDB allocation pages (PFS, GAM or SGAM).

    Fixes:

  •  

  • 5.45 F Bill Border 05Aug13

    Enhancements:

  • (All) A feature of event logic called suppress_dups_from_db has been activated. This will better and more efficiently suppress consecutive duplicate events using DB tables instead of files.
  • (MSSQL) The DBA852 Performance Metric Exception Event now will only display the INTEGER value of the counter, with zero decimal places. This will allow similar consecutive iteration events to be better suppressed.

    Fixes:

  • There was a problem in remsh.pl where it was not correctly substringing the error text during failed connections. As a result, consecutive iteration failures were not being properly suppressed. This was fixed and the HASH hex string is now removed from the error message.

  • 5.45 E Bill Border 31Jul13

    Enhancements:

  • (MSSQL) New Event DBA862 which checks the "Agent Profile" for each Distribution Agent on an MSSQL Replication Distribution server. This event will occur if the Agent Profile is not "Default Agent Profile". The reason for this is that we want to prevent the situation where we, after using a non-default profile to solve a problem, forget to switch back to the default (non-error-skipping) profile.

    Fixes:

     

  • 5.45 D Bill Border 21Jul13

    Enhancements:

  • (All) New All Charts reporting. It is now possible to run one WWW Report which will create 1 chart for each metric, based on your selection. Click on the AD URL next to the instance for a menu of Graph Sets.
  • (MSSQL) New Metric: SQL_Untrusted_Domain_Events . This metric measures the number of "Untrusted Domain" messages found in the SQL Error Log during the most recent iteration.

    Fixes:

  • (All) I'm cleaning up the metric names, so the metric PERF_TEMPDB_FILE_COUNT was renamed to PERF_SQL_TEMPDB_FILE_COUNT.

  • 5.45 C Bill Border 19Jul13

    Enhancements:

  • (MSSQL) New Metric: SQL_Sessions_Week_Old . This metric measures the number of SQL sessions (user sessions) that have been connected at least 7 days. As with any other performance metric, a threshold can be placed on this for Perf Event notification.
  • (MSSQL) New Metric: SQL_Untrusted_Domain_Events . This metric measures the number of "Untrusted Domain" messages found in the SQL Error Log during the most recent iteration.

    Fixes:

  • (All) There was an issue where a event perf chart from a previous event would be attached to the next non-suppressed event incorrectly. Fixed.

  • 5.45 B Bill Border 16Jul13

    Enhancements:

  • (MSSQL) The SQLTrend monitoring of DB Size vs. Historical Size is now active with an initial threshold of 150%. In addition, the percent was removed from the event short text to reduce duplicates. And, this event will only occur if the size of the instance currently is > 1GB.

    Fixes:

  • (All) The date format for the chart sent with Metric Event Email messages was wrong. Fixed.

  • 5.45 A (Major) Bill Border 14Jul13

    Enhancements:

  • (MSSQL) First attempt at attaching a Last 30 Days Detail Chart to MSSQL Performance Metric Event Notification email messages. So, now for all Performance Metric (Sev=P) events, there will be an attached chart for the last 30 days (raw data). More to come on this in the future.
  • (MSSQL) New eventPerfGraph.pl routine. This will be used to attach charts to Performance Event notification email messages.
  • (MSSQL) The "probeout" logic has been improved to eliminate some file copies and to clean up the logic. The result is another good performance increase. We now monitor 72 worldwide SQL Instances in about 13-15 minutes per iteration (from a small Windows server). The /opt/dbamon/tmp/MODE_n/debug directory is not used; all probeout data is stored in /opt/dbamon/tmp/MODE_n/probeout.
  • (MSSQL) The SQL MAIL SERVER notation has been removed from the Summary Page. This causes the page to be more compact (a good thing). A few other items were rearranged as well.
  • (MSSQL) New Event DBA809 logic has been changed to run this check for all instances unless DBC parameter "Prime_Time_LRC_Check:" is set to N.
  • (MSSQL) New sqlTrends.pl routine to analyze current versus historical readings. Initially, there will be one trend check: DB Reserved Space (All DBs) Growth. This check will compare the average size of the instance during the last 3 days to the average size during the last 180 days. If the current size is >= 200% of the historical size, then a new DBA950 Trend Event will occur (the event will be added in a future release). This is just notification, and may be entirely normal in some case. The reason for this metric is that we have seen cases where DBs are growing at an alarming rate, and we don't detect this until is has been happening for a long period of time.
  • (All) The DBAmon version/release is now placed into all log files.
  • (All) New DBAMON.INSTANCES_PERM repository table. This table is recreated at the end of each iteration from the INSTANCES table. This will allow you to run reports even while Iteration #1 is in progress.
  • (All) WWW Instance Summary Page has been cleaned up (small columns on the right side of the page have been consolidated into one column).
  • (MSSQL) New Windows Network WMI Performance Metrics (totals for all Network Adapters) are being collected and displayed in the same way as the other (SQL, Windows) performance metrics:
        NET_BytesReceivedPersec
        NET_BytesSentPersec
        NET_BytesTotalPersec
        NET_CurrentBandwidth
        NET_OutputQueueLength
        NET_PacketsOutboundErrors
        NET_PacketsReceivedErrors
  • (MSSQL) New DBAMONRC T_PerfCounter: parameter which allows you to specify defaults for the DBC parameter T_PerfCounter:. Any parameter specified here will be automatically propigated to any DBC file which does not specify this T_PerfCounter counter-name specified.

    Fixes:

  • (MSSQL) Service Account Names were being displayed with 2 back-slashes. Fixed.
  • (All) The 'EMAIL-4' logged message was incorrectly display the recipient. Fixed.

  • 5.44
    5.44 A (Major) Bill Border 27Jun13

    Enhancements:

  • (MSSQL) The three previous "probe calls" have been combined into one. The "sqlUp" probe now collects all data for all subsequent calls. This will drastically improve DBAmon performance (the time and number of network calls required to complete one iteration).
  • (MSSQL) New Event DBA809 (Sev=User) will occur if if any CHECKDBs, Full or Differential backups are found to be running for at least 30 minutes on weekdays and during prime shift (that was a mouthful). In my case, these do sometimes cause performance problems, so we do want to know when they're running (during the day).

    Fixes:


  • 5.43
    5.43 B Bill Border 22Jun13

    Enhancements:

  • (MSSQL) For I/O delay messages in the SQL Error Log, the count of occurrences is now saved as a new Perf Metric.
  • (MSSQL) The METRIC_DAILY table now has a SUM column, for the sum of all values, by date. The same is true for METRICS_HOURLY. In the future, all graphs will be enhanced to take advantage of this new column.

    Fixes:

  • (All) This is partly fix and partly enhancement. Since the PERF stats are inserted a few minutes later than they are collected, this can be misleading. Now, the timestamp that the stats are captured is the timestamp that is used for newly inserted PERF rows.

  • 5.43 A Bill Border 08Jun13

    Enhancements:

  • (MSSQL) The first preliminary logic enhancements have been made to enable DBAmon to not require the MSSQL SYSADMIN server role. More to come on this in subsequent releases.
  • (MSSQL) SQL Error Log message 4014 (invalid client network stream) is now excluded (it is non-actionable for a DBA).

    Fixes:

  • (MSSQL) On the Instance Summary WWW page, the OS SP-level was not being displayed correctly. Fixed.

  • 5.42 C Bill Border 20May13

    Enhancements:

  • (MSSQL) New Critical Event DBA948 will occur if any STACK DUMPs are found in the SQL Log. It is interesting that these were not previously detected by DBAmon, but this is because STACK DUMP messages do not follow the normal MSSQL rules for messages, which would include a message severity. Anywho, we do now detect STACK DUMPs.
  • (MSSQL) New Performance Metric for the number of NTLM Authenticated Remote MSSQL Sessions. This is useful to see if Kerberos or NTLM authentication is being used for Windows-authenticated MSSQL sessions. See MSSQL What DBAmon Monitors (MSSQL) for details.

    Fixes:

  • (MSSQL) The nounFromString function was not properly handing the needle at the end of haystack. Fixed.

  • 5.42 B Bill Border 08May13

    Enhancements:

  • (MSSQL) Deadlocks Snapshot Reports have been improved. How the Primary Object is display in the report menu. as a DBAmon Snapshot. There is also a new Summary section at the top of the list of reports for one instance.
  • (MSSQL) The MSSQL Active Sessions Snapshot has been improved to show row colors based on whether the Session is waiting or not.
  • (MSSQL) The DBA945 Event (MSSQL Service Account Expiration) has been improved to include less information in the short text. This improves event uniqueness and reduces duplicate events.

    Fixes:

  • (MSSQL) Deadlock Snapshot Reports were sometime incomplete. The way that the data is gathered from xp_readerrorlog has been improved.

  • 5.42 A (Major) Bill Border 04May13

    Enhancements:

  • (MSSQL) New DBAmon Snapshot concept. For certain events and performance metrics, DBAmon now stores (in a repository table - of course) detailed information. These are kept in the DBAmon Repository for 15 days. On the DBAmon Instance Summary (WWW) Page, there is a new SNA transaction where you can view this data. For this release, only ACTIVE TRANSACTIONS are captured, but much more will be added in the future, such as: Blocked Sessions, Active Sessions, etc..
  • (MSSQL) New Long Running Transaction checks and associated metrics. New MSSQL_Trans_Duration_Hrs: and MSSQL_Trans_TLOG_GB: DBC Parameters . If a SQL Active Transaction has been running too long or is consuming too much TLOG space (according to these new DBC parameters), then the new DBA944 event will occur.
  • (MSSQL) 3 New SQL Error Log errors are now excluded: 17836, 18210 and 3041. They have to do with intermittent network errors and failed backups (which we are already tracking with Backup Age monitoring).
  • (MSSQL) We now gather the number of MSSQL Outstanding I/O Requests as the performance metric SQL_Pending_IO_Requests. This would be a good metric to gather and review historically. See: What DBAmon Monitors (MSSQL) for details.

    Fixes:

  • (All) Some of the newer WWW routines were not correctly displaying the background color of violet for (S)ecurity events.

  • 5.41 A (Major) Bill Border 12Apr13
  • (MSSQL) New Long Running Job check and associated metric. If a SQL job has been running for at least 12 hours (possibly in the future I will provide a way to change this threshold), then the new DBA943 event will occur. Since you may have SQL Jobs which normally run forever, it is possible to exclude this jobs with the new MSSQL_Job_LR_Check_Name_Excl_String: DBC Parameters .
  • (MSSQL) New Failed Logins check and associated metric. If any 18456 SQL Login errors have occurred, then a DBA942 event will occur.
  • (MSSQL) The MSSQL_Job_Check_Cat_Excl_String: and MSSQL_Job_Check_Cat_Excl_String: DBC Parameters now allow multiple paramters, separated by commas but with no spaces.
  • 5.40 G Bill Border 13Mar13
  • (MSSQL) New MSSQL_Job_Check_Cat_Excl_String: and MSSQL_Job_Check_Cat_Excl_String: DBC Parameters . Using these parameters, you can exlude certain jobs from Job Failure Monitoring.
  • 5.40 F Bill Border 16Feb13
  • (All) Aesthetic corrections to many WWW programs.
  • (MSSQL) New '*All*' Metrics option from Instance Summary WWW page. This is less confusing than the old DET and HST URL's.
  • (MSSQL) New Display in Instance Drill Down which shows the I/O counts to all DBs and DB Files. More to come on this in the future...
  • 5.40 E Bill Border 29Jan13
  • (MSSQL) The event stating that all files are on the C: drive is now skipped for servers that only have a C: drive.
  • (MSSQL) The SIGNAL WAIT event for SQL2012 now has a threshold of 40%. All lower versions have a threshold of 25%.
  • 5.40 D Bill Border 15Jan13
  • (MSSQL) Improved memory cleanup.
  • 5.40 C Bill Border 27Dec12
  • (MSSQL) New Inhibit capability by Day of Month and Replication Subscription Number. This allows you to exclude certain subscriptions from Replication Age Checking for certain days of the month. See: MSSQL Replication Inhibit Documentation .
  • 5.40 B Bill Border 08Dec12
  • (All) dbamon_checker Was enhanced to now count the total number of Cygwin processes. This is to get some early warning of a Cygwin bug where processes hang. If at least 50 total processes are found (by running procps), then the DBAmon administrator will be emailed.
  • (All) Some minor aesthetic enhancements to The WWW Instance Summary page.
  • (All) New Logs URL in Instance Summary page. This will allow you to view DBAmon Global log files and log files that are unique to this instance.
  • (All) The DBAmon Console WWW page has been cleaned up, and new View Log Files transaction.
  • 5.40 B Bill Border 08Dec12
  • (All) dbamon_checker Was enhanced to now count the total number of Cygwin processes. This is to get some early warning of a Cygwin bug where processes hang. If at least 50 total processes are found (by running procps), then the DBAmon administrator will be emailed.
  • (All) Some minor aesthetic enhancements to The WWW Instance Summary page.
  • (All) New Logs URL in Instance Summary page. This will allow you to view DBAmon Global log files and log files that are unique to this instance.
  • (All) The DBAmon Console WWW page has been cleaned up, and new View Log Files transaction.
  • 5.40 A Bill Border 24Nov12
  • (MSSQL) For DBA857 event, the maximum suggested number of TEMPDB file is now 4 (previously it was 8).
  • (MSSQL) DBAMON.Events table - Now ticket=SD rows > 14 days old will be deleted at the end of each iteration. This is because they are not needed long-term, and they account for most of the rows in this table of our production DBAmon Repository.
  • (MSSQL) Perf Events with C severity (see 5.38.G below) now have a more generic SHORT TEXT event message, to better work with Consecutive Duplicate Event Suppression. Also, all DBA852 events now have Long Text.
  • (MSSQL) New Check: DB Files set to PERCENT GROWTH. If any DB file or TLOG file is set with PERCENT GROWTH, the new event DBA806 will occur. The idea for this new check came from a talk by Brent Ozar at PASS.
  • (MSSQL) New Check: DB Files on the C: drive. If any DB file or TLOG file live on the C: drive, the new event DBA807 will occur. The idea for this new check came from a talk by Brent Ozar at PASS.
  • (MSSQL) Performance Metrics detail WWW page - Did some general cleanup.
  • (All) New DBAMONRC Suppress_Events: parameter. You can specify DBAmon Events MSGID's (like DBA806) that you need to suppress for all instances. This works just like the DBC Suppress_Events: parameter, but at a global level.
  • (All) New DBAmon Command: dbamon_drain . This command gracefully stops DBAmon at the end of the current iteration.
  •  
    5.39 G Bill Border 02Nov12
  • (MSSQL) The MSSQL Service Account Name is now collected and displayed on the "MSSQL Instance Information" section of the drilldown page.
  • (MSSQL) The TOP WAITs are now collected also for SQL 2000 (using DBCC SQLPERF (WAITSTATS)).
  • (MSSQL) New MSSQL_Repl_Lag_Excl_String: DBC Parameter . This parameter allows you to specify a Replication Subscription "Search String" to exclude certain subscriptions from the Replication Max Lag metric. See the DBC documentation for more information.
  • (MSSQL) For DBC Parameter: T_PerfCounter: it is now possible to specify the event severity of either P (the default) or C for CRITICAL. This allows you to notify differently for different performance events. See T_PerfCounter: DBC Parameter .
  • (All) The WEEKLY INSTANCE REPORT was showing the total number of events (by type) *including* SD (Suppressed Duplicates). These rows (EVENTS Table) are now excluded.
  • 5.39 F Bill Border 26Oct12
  • (MSSQL) Change in the way that TLOG full is calculated. Before we were just using the value returned by DBCC SQLPERF (LOGSPACE). The problem was while this was a good conservative way to monitor space, it didn't take autogrowth into account. So, this has all been changed now. In the case of:
    • TLog File with Auto-Growth OFF: The value from DBCC SQLPERF (LOGSPACE) (% Full) will be used.
    • TLog File with Unlimited Growth: The value from DBCC SQLPERF (LOGSPACE) (% Full) will be used.
    • TLog File with Auto-Growth SET: The value from DBCC SQLPERF (LOGSPACE) will be multiplied by the size of the TLOG to give the amount of TLog space used (MB). This value is then divided by the Total Max-Size of all TLog files to give the accurate TLog Percent Full vs. TLog File(s) Total Max-Size.
  • 5.39 E Bill Border 24Oct12
  • (Oracle/Win) Some misc. fixes to resolve some issues found in Beta testing.
  • (MSSQL) Six new Windows Performance Counters have been added to dbamon_mssql.cfg. The ones that were all all end in "_PS" (DBAmon variable name).
  • (MSSQL) New check for DBs with certain DB options (such as AutoUpdateStatistics) set to FALSE. The new DBA861 User event occurs in this case.
  • 5.39 D Bill Border 18Oct12
  • (Oracle/Win) Added some diagnostic data displays for a customer who is having connectivity problems.
  • (All) The daily events report was showing SD (suppressed duplicate) events, which made the report HUGE. They are now not reported. Also, there was a broken link near the beginning of the report.
  • (All) The Weekly Instance Report (email) had a broken link. Fixed.
  • (All) The "Events by ID Value" WWW report was displaying SD (suppressed duplicate) events. Now, they are not displayed which makes the report much more readable.
  • 5.39 C Bill Border 06Oct12
  • (MSSQL) Initial coding of New Replication monitoring in probe.
  • (MSSQL) Probe code cleanup. A result of this is that the Lightbulb will have less extraneous data.
  • (MSSQL) SQL Error Log event 7886 is now in the default exclude list.
  • 5.39 B Bill Border 30Sep12
  • (MSSQL) New Performance Metric: SQL_SQLMem_Vs_DBSize_Pct . This is SQL Total Memory divided by the total size of the DB. Specifically: ($perf_readings[$thishost]{"SQL_TotMemKB"} / $perf_readings[$thishost]{"SQL_DBSizeKB"}). This is useful in determining whether the SQL DB size has outgrown the amount of memory allocated to SQL. If this is < 1%, then you need to add memory (that's the initial rule-of-thumb that we're going to use). This can be given a threshold just as for other MSSQL Performance Metrics.
  • (Oracle/NT) Some improvements in performance metrics, URLs on the summary page, etc. Finished documentation on how to add an OracleNT target.
  • (All) New experimental Trend Analysis WWW Transaction. On the WWW Summary page, you will now see a new "Tre" URL. This will run a comparison of all metrics for the selected DB Instance for the last 7 days against the average value for the last 6 months. Deviations will be color-coded in the WWW display.
  • 5.39 A Bill Border 25Sep12
  • (All) The messages that are displayed during Event Notification have been cleaned up.
  • (All) We are now a step closer to being able to do Consecutive Duplicate event suppression from the repository.
  • (Oracle/NT) Some alpha test code which works in the LAB against Oracle 11g is included.
  •  
    5.38 D Bill Border 14Sep12
  • (All) It is now possible to inhbit a certain DBAmon event during certain hours of the day and days of the week. For more information, see Event Inhibit by Event, DOW, Hour .
  • (MSSQL) There were some WWW content highlighting problems that were visible in Firefox. These are now fixed.
  • (MSSQL) When checking the SQL Event and Agent log, we previously only included 500 errors per event - then the next iteration would find the next 500. This means that a problem which manifests itself as 10000 errors in the SQL log would create 20 consecutive events. Now, the 500 limit has been changed to 1,000,000. This way, there should only be 1 event per problem.
  • (MSSQL) The events for SQL Log Alerts and Agent Log Alerts now do not specify the number of new error lines found. This helps Consecutive iteration duplicate suppression.
  • (All) The install script dbamon_setup_apache2 was previously missing. It is now included.
  • 5.38 C Bill Border 10Sep12
  • (MSSQL) For tracking DB Size, I have always used sp_spaceused. The numbers that we tracked however did include the size of the TLOG. DBAmon now will much more accurately track the size of:
  • Tables
  • Indexes for your MSSQL instance. There are therefore new metrics DB_SPACE_TABLES_MB, DB_SPACE_INDEXES_MB, DB_SPACE_RESERVED_MB and DB_SPACE_UNUSED. Basically these are just the 4 values that you will always seen in the 2nd Result Set when you run sp_spaceused.
  • 5.38 B Bill Border 10Sep12
  • (All) We're trying other SSH-Server tools, which would require us to specify the DBC Userid: parm with a domain name, so there is a new DBAMONRC Quote_Domain_Users: parameter. If you specify this as Y, then DBAmon will automatically put single quotes around the Userid: value in SSH commands.
  • 5.38 A Bill Border 01Sep12
  • (All) The Event email messages are now much more readable. They also have new inline URLs to take you to DBAmon instance WWW content.
  •  
    5.37 H Bill Border 01Sep12
  • (All) DBAmon will now log CONSECUTIVE-DUPLICATE events in the EVENTS tables unless you specify the new DBAMONRC Duplicates_To_Events_Table: parameter as N. The reason for this change is that it always has bothered me that if an instance has a continuous problem over a few days, you would only see the first event (with the old behavior). The "EvH" WWW transaction has been adjusted accordingly.
  • (All) On this instance summary page the Actions columns has been cleaned up. Now, Metrics URLs are all grouped together.
  • (All) WWW content formatting now is compatible with Mozilla Firefox. Everything should look fine now which lifts the restriction that you have to use IE. Now, DBAmon WWW content has been tested with Firefox and Chrome.
  • (All) Improved the wording of some SCP connection errors.
  • 5.37 G Bill Border 31Aug12
  • (Oracle/NT) Resolved a few obvious problems. Thanks to Darryl Heath (City of COS).
  • (All) In event.pl I now remove all [ ] (square brackets) which should help in successfully suppressing duplicates (there were a few that were sneaking through).
  • (MSSQL) New Backup metric to measure the number of days since the last successful FULL DB backup. This can be useful if you are running differential backups and it has been a long time since the last good FULL backup. This parameter is in addition to Backup_Age:. The new DBC parameter is Backup_Age_Full_Days: . There is also a new DBAMONRC Default_Backup_Age_Full_Days: parameter for specifying a GLOBAL DEFAULT.
  • (All) We now collect the amount of time that DBAmon spent monitoring this instance with the new PERF metric: PERF_DBA_INSTANCE_DUR_SECS.
  • 5.37 F Bill Border 15Aug12
  • (All) The DBMS WWW page didn't drill down correctly. This was because I was missing the os_fam entries for NT-6. Fixed now.
  • (MSSQL) The Lightbulb transaction was slow because of how I was collecting memory usage. Fixed.
  • (MSSQL) In some browsers, the small text links on the WWW summary didn't work (like "Per"). Fixed.
  • 5.37 E Bill Border 04Aug12
  • (MSSQL) New Perf_Metric_Label: DBC Parameter . This parameter gives you the capability of specify labels for any performance metric.
  • (MSSQL) Aesthetic improvements to Ploticus-generated charts.
  • (MSSQL) The MSSQL Synthetic Transactions/User Metrics have been improved. You can now create your own User Metrics (see the URL above) in addition to RT's from Synthetic Transactions.
  • 5.37 D Bill Border 31Jul12
  • (MSSQL) The event number for SQL Agent Log errors has been changed from DBA651 (the same as SQL log messages) to DBA658.
  • 5.37 C Bill Border 27Jul12
  • (MSSQL) We now will detect the string /unable to/i in the SQL Agent Error log. This can happen when there are email problems.
  • (MSSQL) In some cases, a call to sp_msforeachdb must be qualified with master.sys.sp_msforeachdb. Now, for SQL versions below 2005 we will specify master..sp_msforeachdb and for 2005+ we will specify master.sys.sp_msforeachdb. This is in the VLF check sub.
  • (MSSQL) I made the WMIOperatingSystem SUB into a switched call, turned off for now. This means that we won't see LAST REBOOT, etc.. The problem was that it was causing a long delay in the UP probe for some servers. Must be something flakey with WMI and that class.
  • 5.37 B Bill Border 21Jul12
  • (MSSQL) The probe was not specifying the location of sp_msforeachdb in the VLF routine. Now I call master..sp_msforeachdb.
  • 5.37 A Bill Border 18Jul12
  • (MSSQL) This is the base version that is certified to work with Strayberry Perl on TARGET servers. :@)
  • (All) The WWW Summary page was cleaned up. A few columns were consolidated and some style inconsistencies were resolved.
  •  
    5.36 D Bill Border 10Jul12
  • (MSSQL) Added 2 new Performance Counters to dbamon_mssql.cfg: \Memory Manager\Memory Grants Pending and \Memory Manager\Memory Grants Outstanding
  • 5.36 C Bill Border 06Jul12
  • (MSSQL) The removal of calls to Win32::Registry is complete. This release is Beta test of these changes. This means that DBAmon now works fine with MSSQL targets using, for example, Strawberry Perl.
  • (All) In end_stuff.pl we now use the "move" Perl call (part of File::Copy) instead of system(mv). The reason for this is that I sometimes see the CYGWIN "train wreck" on these system(mv) and system(cp) calls.
  • (All) WWW Summary Page - Some columns headings now use a slightly smaller font.
  • (All) WWW Summary Page - The Backup Age column is now formatted better. You will see the value for DB backups shown distincly from the backup age for LOG backups.
  • (MSSQL) The time of last OS reboot and OS reboot timestamp are now accurately collected and reported. There is a new sub WMIOperatingSystem which gathers this from WMI.
  • 5.36 B Bill Border 27Jun12
  • (MSSQL) More changes in the probe to remove Win32::Registry calls.
  • (MSSQL) New Metric: TOP SQL WAITS. We query sys.dm_os_wait_stats (2005+) to find the top 5 waits. This can then be tracked over time to see performance changes in your SQL instance.
  • 5.36 A Bill Border 26Jun12
  • (MSSQL) I would like to remove all calls to Win32::Registry so that we can start using Strawbery perl on MSSQL Targets. The reason for this is that since DBAmon is an Open-Source tool, it should rely only on other Open-Source software. This release starts making this conversion.
  •  
      Starting with verion 5.36 I will reinstitute the practice of MAJOR (number incremented) and MINOR (letter incremented) versions and releases of DBAmon.
     
    5.35   Bill Border 03Jun12
  • (MSSQL) It is now possible to monitor the response time for an MSSQL Synthetic Transaction .
  • (MSSQL) Two new MSSQL DBC Parameters have been added:
    • Backup_Age_TLog: - Allows you to specify a Backup Age threshold for TLOG backup which is different than the threshold for DB backups.
    • Backup_NoCheck_DBs: - With this parameter you can specify the SQL Databases for which you DO NOT want to check backup age.
  • (MSSQL) Backup Age checking (DB and TLOG) has been cleaned up. The WWW Backup Details section has been clarified.
  • (B) (MSSQL) Due to bugs in the CYGWIN OS, it was necessary to replace system calls to "cp" with the Perl File::Copy function. This will improve performance, and avoid the OS BUG.
  • (B) (MSSQL) When DBAmon is recycled, now it will not kill the httpd[2] daemon. Oops.
  • 5.34   Bill Border 13May12
  • (MSSQL) Correction to the logic which calculates TLOG fullness. Previously, we didn't correctly handle DBs with more than 1 TLOG. That is now corrected - the only thing that we now care about is how full the TLOG is internally (used space). This reading is obtained from DBCC SQLPERF (LOGSPACE).
  • (MSSQL) Cosmetic change - The WWW Summary page now displays Physical Disk Average RT (MS).
  • 5.33   Bill Border 30Apr12
  • (MSSQL) New check for DBs with DBState=RECOVERING. A DBA671 User event occurs in this case.
  • 5.32   Bill Border 13Apr12
  • (MSSQL) New DBsNotSimpleRM=n status/config message for instances where at least 1 DB is in Full or Bulk-logged Recovery Model.
  • (MSSQL) The long text for instances of MSDE now says MSDE. It used to read: DesktopEngine.
  • (All) This program (dbamon_checker) has always stopped DBAmon to compress the log file /opt/dbamon/log/dbamon.log (the normal STDOUT file) when it went over 7.5mb. It still does that, but it shuts down DBAmon gracefully. Before it would abruptly kill DBAmon, which caused events to republish (bad).
  • (MSSQL) New logic to deal with WMI returning NOTHING from the query to show all drive sizes. This used to cause a METRICS_CURRENT insert error. Now, even if WMI does not return anything valid (I'm not clear on how/why that could happen), a plan-B of running the DBAmon disk info command will be tried. If ever the size of a drive that is returned to the master is ZERO, and new DBA990 event will occur.
  • 5.31   Bill Border 29Mar12
  • (MSSQL) New PhoneHome_Messages: dbamonrc parameter. This allows you to suppress probe diagnostic email messages.
  • (MSSQL) Bug fix: For one of our customers, perf counters were null. As it turns our, typeperf was showing correct column names (the 1st line), but missing counters showed up as -1 in the values line. So now we skip all -1 values in the values lines.
  • 5.30   Bill Border 02Mar12
  • (MSSQL) New No_Tickets_For_Events: DBC parameter which allows you to suppress tickets for certain events, for an instance.
  • (MSSQL) The DBA351 event has been modified to NOT occur if the job has a status of "betweenretries".
  • (MSSQL) The behavior of the "Backup_Check_DBs:" DBC Parameter has been changed. Now, if you DO NOT specify this parameter, then ALL DBs will be checked for Backup_Age:. Previously you had to explicitly specify DBs for which you want to check Backup_Age:. The same is now true for TLOG Backup Age checking.
  • 5.29   Bill Border 08Feb12
  • (MSSQL) New support for SQL Server (Microsoft) 2012. Stay tuned for more information.
  • (MSSQL) SQL Server 7 is no longer supported. Sorry man, but nobody should be running this any more - like... it's 2012!
  • (MSSQL) New DBAmon check for MAX SERVER MEMORY set to INFINITE (2^31). New DBA860 event will occur if your MSSQL instance has MAX SERVER MEMORY set to the out of the box default setting. This event has some advice on how to set correctly.
  • 5.28   Bill Border 20Jan12
  • (All) Program dbamon_mssql_sumread.pl was rewritten to be more efficient.
  • (All) New dbamonrc Use_DNS: parameter. This can be used to disable NSLOOKUP hostname checking on your DBAmon MASTER (rarely would this be needed).
  • (MSSQL) New MSSQL_String_Check: DBC parameter which allows you to search the SQL for any string and then report from the resulint DBAmon Performance Counter variable. See the URL above for more information.
  • (All) New Event Index at the top of the Events Detail WWW page.
  • (MSSQL) New PERF_SQL_LPIM_LOCKED_KB Metric which will show you whether LOCK PAGES IN MEMORY is REALLY enabled. New STATUS FLAG to show whether LPIM is ON or OFF.
  • (MSSQL) New PERF_SQL_RUNNABLE_REQS Metric which will show you the number of RUNNABLE tasks. See WHAT DBAMON MONITORS History for details
  • 5.27   Bill Border 08Jan12
  • (All) Some Iteration Completion messages are improved.
  • (All) A report of the DBC file contents are now displayed with INSTANCE DETAILS (WWW).
  • (All) New dbamonrc Admin_Pager: parameter where you can specify the EMAIL ADDRESS of a pager. If there is a fatal DBAmon error or if the DBAmon WATCHDOG finds that DBAmon has been dead for at least 90 minutes, a message is sent here.
  • (MSSQL) New Event_EMail_For_Sevs: DBC parameter which allows you to override the default behavior with regard to sending Event notifications via email. By default, DBAmon sends email notification only for (C)ritical and (U)ser events. With this new DBC parameter, you can additionally force EMail Event Notification for other severities.
  • (All) Now, the WWW Event Details page display what (if any) notification occurred for this event (COOL!).
  • (All) BUG FIX - For Sev=W events, consecutive-iteration duplicate event suppression was not working. It is working now.
  • 5.26   Bill Border 14Dec11
  • (MSSQL) New MSSQL_Job_OK_Owners: DBC parameter where you can specify OK Job Owners (in addition to SA).
  • (MSSQL) New MSSQL_DB_OK_Owners: DBC parameter where you can specify OK DB Owners (in addition to SA).
  • (MSSQL) New VLF (Virtual Log File) metric and check. New T_MSSQL_VLF_Count: DBC parameter where you can specify a monitoring threshold. If the threshold is exceeded, a DBA859 event will occur.
  • 5.25   Bill Border 05Dec11
  • (MSSQL) TLOG Backup age check - We don't do this for DBs that are in SIMPLE logging mode. Don't know wh I didn't do this sooner.
  • (MSSQL) Job Failure check - This event won't occur if the Job has status of Executing.
  • 5.24   Bill Border 26Nov11
  • (All) Cleanup of WWW Instance Summary pages. New "wider" look, a better looking header, etc.
  • (MSSQL) New DBA857 check and event for TEMPDB database file count. See the event documentation for more information.
  • (MSSQL) New DBA858 check and event for SIGNAL WAIT PERCENT. See the event documentation for more information.
  • 5.23   Bill Border 13Oct11
  • (MSSQL) New DBA664 event for "I/O Delay" messages in the SQL Log.
  • (MSSQL) New DBA670 event for "A significant part of SQL memory has been paged out" messages in the SQL Log.
  • (MSSQL) New MSSQL_Log_Min_Sev: DBC parameter which allows you to override the default SQL Log message severity of 17.
  • 5.22   Bill Border 05Oct11
  • (MSSQL) New DBA354 event for failed SQL Server jobs. New MSSQL_Job_Fail_Check: parameter.
  • 5.21   Bill Border 03Oct11
  • (MSSQL) New DBA856 event for SQL Server SUSPECT_PAGES rows. This new check looks for SQL Engine-detected PAGE CORRUPTION.
  • (MSSQL) New DBA519 event for new SQL Server check: Databases in FULL or BULK-LOGGED Recovery Model, but no TLOG backups within the last 30 days. This is a WARNING event.
  • 5.20   Bill Border 25Sep11
  • (MSSQL) New DBA352 and DBA353 events for MSSQL Jobs and DBs with an owner other than 'SA'. This new functionality can be turned OFF by specifying the new SQL_Job_Owner_Event: or SQL_DB_Owner_Event: dbamonrc parameters as N.
  • 5.19   Bill Border 15Sep11
  • (MSSQL) BUGFIX: SQL Error log checking - If we "last" out of the while, then a "finish" is missing on the statement handle. This only happens when there are ZILLIONs of errors.
  • 5.18   Bill Border 14Aug11
  • (All) New Windows GADGET code (prototype).
  • 5.17   Bill Border 01Aug11
  • (MSSQL) New Check - BAD DB Options. If you specify a DB option which is known to cause performance issues (currently AUTOCLOSE and AUTOSHRINK), then a new DBA855 (Performance severity) event will occur.
  • 5.16   Bill Border 19Jul11
  • (MSSQL) BUGFIX - Had to add more logic to deal with SQL DBs with spaces and hyphens in the DB name.
  • 5.15   Bill Border 10Jul11
  • (MSSQL) New MSSQL HUNG BACKUP check (SQL 2000+ only). A DBA854 (Critical severity) will occur if a SQL backup is found to be running at least 24 hours.
  • (MSSQL) New check of the SQL AGENT Log. If the string error is found in the text of an AGENT Log entry, an event is created.
  • 5.14   Bill Border 29June11
  • (MSSQL) New MSSQL DBMail check (SQL 2005+ only).
  • 5.13   Bill Border 26June11
  • (MSSQL) BUGFIX: The DBC Parameter: T_FG_Full: was not disabling sqlUp() with "N" specified. Fixed.
  • (All) New dbamonrc Default_DBMS: parameter. This specifies the default DBC DBMS: setting.
  • 5.12   Bill Border 12June11
  • (MSSQL) New DBC Parameter: T_PerfCounter: to specify warning and critical event thresholds against Windows and SQL performance counter readings.
  • 5.11   Bill Border 09June11
  • (All) New daily reporting program for Repos=SQL dbamon_mssql_eventrpt.pl.
  • 5.10   Bill Border 04May11
  • (MSSQL) New information has been added to the Instance Summary which displays the current CPU, Memory and Disk readings for this server.
  • 5.09   Bill Border 26Apr11
  • (MSSQL) New dbamon_mssql.cfg file to store various parameters. This allows me to eliminate some hard-coded parms (log check exclude strings and performance counter names and verbs).
  • 5.08   Bill Border 14Apr11
  • (MSSQL) Various fixes.
  • (All) New CUR icon on instance summary to view current readings.
  • (All) Logic change - for the DBAMON.INSTANCES table, now all of the MISCn columns will be populated from the IDn fields (DBC).
  • (MSSQL) The new event: DBA200 (User severity) will occur when any DB file is set to MAXSIZE=Unlimited.
  • 5.07   Bill Border 03Apr11
  • (MSSQL) New WWW Pulldown and Direct-Graph capability.
  • 5.06   Bill Border 28Mar11
  • (MSSQL) New CONFIG_SAVE capability. We now save important instance information for every SQL instance in /opt/dbamon/dat/config_save.
  • 5.05   Bill Border 18Mar11
  • (MSSQL) New MSSQL Job monitoring. You can specify MSSQL DBC MSSQL_JOB* Parameters which tell DBAmon to monitor certain MSSQL JOBS that should be running continously. The new event: DBA351 will occur if a job should be running, but is not running.
  • 5.04   Bill Border 11Feb11
  • (MSSQL, All) We now collect SYSTEM Metrics on Windows from Windows "Counters". The Windows "typeperf" command provides a good interface to this date. DBAmon now extracts and reports from these metrics in sqlPerf(). Some metrics that were previosly unavailable: System CPU Busy %, SQL Buffer Cache Hit Ratio, SQL Page Life Expectancy, etc. VERY COOL!
  • 5.03   Bill Border 01Feb11
  • (MSSQL) New MSSQL sqlPerf() routine. We now track MSSQL Performance metrics.
  • 5.02   Bill Border 14Jan110
  • (MSSQL) Various fixes after initial implementation in CYGWIN.
  • 5.01   Bill Border 08Jan11
  • (All) Previously DBAmon depended on an external graphing tool for graph. Now DBAmon had a built-in capability to dynamically create GIF Line Plot graphs, that are viewable on the WWW.
  • 5.00   Bill Border 28Dec10
  • (All) DBAmon Master logic has been ported to run under Cygwin (Windows).
  • (All) DBAmon can now use a SQL Server database as its repository.
  • (All) Many other enhancements, too numerous to list.
  • (MSSQL) All current SQL Server versions through 2008R2 are now support.
  • (MSSQL) Many improvements in WWW pages, LightBulb, etc.
  • 4.38 (Base) Bill Border 12Feb08
  • (MSSQL) New support for MSSQL 2005 64bit.
  • (All) The WWW summary page has been reworked so that everything shifts to the left (viewable without scrolling).
  • 4.37 (Base) Bill Border 29Jan08
  • (Oracle/UX) New DBA318 event for DB instances which have a grant to a non-SYSTEM userid for the IMP_FULL_DATABASE role (dangerous).
  • (Oracle/UX) New DBA319 event for DB instances which have a grant to a non-SYSTEM userid for the ALTER USER system privilege (dangerous).
  • 4.36 (Base) Bill Border 19Dec07
  • (MSSQL) DBAmon will now NOT create any backup age events (or rerun backups) for an MSSQL 2005+ snapshot DB.
  • 4.35 (Base) Bill Border 11Dec07
  • (Oracle/UX) New monitor for DF count within a tablespace. There is an Oracle limitation of 1022 datafile for non-bigfile tablespaces. This new metric measure the percentage of datafiles vs. 1022.
  • (Oracle/UX) The DST patch check will not occur for SAP instances.
  • 4.34 (Base) Bill Border 10Dec07
  • (Oracle/UX) New ability to exclude certain Alert Log strings on a per-instance basis. They are specified in the file /home/oracle/.dbamon_SID_alert_exclude.txt .
  • 4.33 (Base) Bill Border 22Oct07
  • (Oracle/UX) New DBA323 event for DB instances which DO need the DST2007 patch (either for TS-Cols or JVM) and DO NOT have the patch currently applied. Much more sophisticated than the previous DST2007 logic.
  • 4.32 (Base) Bill Border 12Oct07
  • (Oracle/UX) New monitoring logic to see if the COMPATIBLE parameter is set at least one version lower than the software.
  • 4.31 (Base) Bill Border 01Oct07
  • (Oracle/UX) New iSQLPlus icon on DBAmon WWW summary, if iSQLPlus is running.
  • (Oracle/UX) If iSQLPlus is not found to be running, it will be automatically started.
  • (Oracle/UX) If EM (10g) is configured and not found to be running, it will be automatically started.
  • 4.30 (Base) Bill Border 14Aug07
  • (Oracle/UX)New support for Oracle 10g+ DBs using ASM and FRA.
  • 4.28 (Base) Bill Border 17Jul07
  • (Oracle/UX)New DBA606 event. The number of datafiles vs. the DB_FILES parameter is now monitored.
  • 4.29 (Base) Bill Border 14Aug07
  • (Oracle/UX)New DBA940 event. The DB is now monitored for DB Block Corruption.
  • 4.28 (Base) Bill Border 17Jul07
  • (Oracle/UX)New DBA606 event. The number of datafiles vs. the DB_FILES parameter is now monitored.
  • 4.27 (Base) Bill Border 13Jun07
  • (All)New ID9: and ID10: DBC parameters.
  • 4.26 (Base) Bill Border 07Mar07
  • (Oracle/UX) New DBA956 event which indicates that the cron server daemon is not running.
  • 4.25 (Base) Bill Border 22Feb07
  • (MSSQL) DoubleTake monitoring support.
  • 4.24 (Base) Bill Border 12Feb07
  • (Oracle on Windows) New logic for the 2007 DST Change. New DBA320 DBA321 DBA322 events to determine whether a DB instance needs to be patched.
  • 4.23 (Base) Bill Border 05Feb07
  • (Oracle on Windows) New DBA655 event. This occurs when all Oracle Online Redo Logs are on one Windows drive.
  • (Oracle on UX) New DBA520 event. This occurs when the average Log Switch Rate for the DB exceeds 12 log switches per hour. This is a performance event. Solving this problem will result in improved performance.
  • (Oracle on UX) New DBA521 event. This occurs when the average Maximum Daily Redo Data Rate (over the last 30 days) is greater than 1.1 times the size of the archivelog filesystem. In this case, you should increase the size of the archivelog filesystem.
  • (Oracle on UX) The "Redo Rate" is now displayed on the WWW Instance Summary.
  • 4.22 (Base) Bill Border 07Dec06
  • (Oracle on Windows) New DBA654 event. This occurs when all Oracle controlfiles are on one Windows drive.
  • (Oracle on UX) New DBA380 event. This occurs when the backup schedule is missing, either for LVL* or ARC* RMAN backups.
  • (Oracle on UX) New dbamonrc Default_BA_Arc: parameter. This specifies the default Archivelog Backup Age.
  • 4.21 (Base) Bill Border 25Sep06
  • (Oracle/UX on HP-UX) New DBA932 event. When the maxuprc HP-UX Kernel parameter is exceeded for the userid which starts the Oracle DB, the results can be disastrous. DBAmon now counts the number of processes that this userid currently has active (at the OS level) against the maxuprc value. The new dbamonrc Default_T_NUSERPROC: parameter controls the default thresholds for all instances and the T_NUSERPROC: DBC parameter controls the thresholds and the instance level.
  • 4.20 (Base) Bill Border 14Sep06
  • (Oracle/UX) New DBA931 event. Now, if an orphaned RMAN OS process is detected, it will automatically be killed. See the details of the above event for details.
  • 4.19 (Base) Bill Border 02Jun06
  • (Oracle/UX) It is now possible to specify the SGA Full Monitoring Threshold on a per-instance basis. The new T_SGA_Full: DBC parameter allows you to specify Warning and Critical thresholds.
  • 4.18 (Base) Bill Border 07Mar06
  • (Oracle/UX) DBAmon now stores many details about each instance in a repository table. For details, see INSTANCE_DETAILS Table Overview . A schema change is required for this enhancement:
     alter table instances add instance_key varchar2(32); 
  • (All) The Notepad now has a second window for planning information.
  • 4.17 (Base) Bill Border 28Jan06
  • (MSSQL) New MSSQL Event: Check for Zero Non-System DB's. User DBA663 event.
  • (All) New ability to run DBAmon Test Mode from the WWW.
  • 4.16 (Base) Bill Border 11Nov05
  • (Oracle/UX) New Perf Monitor: Default tablespace (perm or temp) set to SYSTEM. Warning DBA930 event.
  • 4.15 (Base) Bill Border 31Oct05
  • (Oracle/UX) New Security Check: DANGEROUS init.ora parameters. For example, the REMOTE_OS_AUTHENT parameter is inherently dangerous. So if this parameter is set to TRUE, a DBA316 event will occur. The parameters that are checked are:
    • REMOTE_OS_AUTHENT
    • REMOTE_OS_ROLES
    • O7_DICTIONARY_ACCESSIBILITY
    If any of these are set to TRUE, then the event will occur.
  • 4.14 (Base) Bill Border 27Oct05
  • (Oracle/UX) The RMAN process hung event has been changed. Previously each hung PID would result in 1 event. Now all hung RMAN processes are combined into 1 event.
  • (All) There was always an issue when we monitor a server-wide event, such as a hung RMAN process. If a server has 10 instances, each instance would report the same event. Now there is a new feature called server-wide-events where duplicate events can be eliminated. So now, for the DBA912 RMAN process hung event, only the first occurance per server/userid and instance will be reported. This will result in far fewer chronic duplicate events.
  • 4.13 (Base) Bill Border 21Oct05
  • (Oracle/UX) New check for an archivelog destination under the ORACLE_HOME directory. This is a bad practice. Now on any instance where this is the case, a DBAmon Event DBA662 occurs.
  • 4.12 (Base) Bill Border 25Aug04
  • (Oracle/UX) New check for empty crontab. If crontab is empty then DBAmon Event DBA661 occurs.
  • (All) New ID5-ID8 DBC fields.
  • (All) New data is now extracted from STAR.
  • (All) New DBC_Class DBC Configuration Parameter.
  • 4.11 (Base) Bill Border 25Aug04
  • (Oracle/UX) New check for the number of controlfiles. See DBAmon Event DBA659 for details.
  • 4.10 (Base) Bill Border 18Jul05
  • (ALL) Fix to histCreate.pl routine. There are some MSSQL DB names that are very long. This was causing an INSERT to error. We now check the length of the field before inserting.
  • 4.09 (Base) Bill Border 06Jun05
  • (Oracle/HP-UX) DBAmon will now check for the presence of HP-UX autostart scripts.
  • (Oracle/HP-UX) If the $ORACLE_HOME/network/log/listener.log file is >= 50M, it will be gzipped.
  • 4.08 (Base) Bill Border 23May05
  • (ALL) Major Change: The DBAmon probe software is now download (on UX servers) to /tmp/DBAmon_{DBC_USERID}/ rather than /tmp. So, the probe software no longer has to be world-writable. This solves many security problems.
  • 4.07 (Base) Bill Border 14Apr05
  • (Oracle/UX) New performance monitored event: Server Memory Usage. This only works at this time for HP-UX. See: DBAmon Event DBA929.
  • 4.06 (Base) Bill Border 11Apr05
  • (Oracle/UX) New performance monitored event: DB Cache size underspecfied. See: DBAmon Event DBA928.
  • 4.05 (Base) Bill Border 11Mar05
  • (Oracle/UX) New performance monitored event: Dictionary Objects have been analyzed. This can cause serious and mysterious performance problems. New event is DBA927.
  • 4.04 (Base) Bill Border 04Mar05
  • (Oracle/UX) There was a bug in the collection of the timestamp of the most recent OFFLINE backup for Oracle/UX standby databases. Also solved a problem where the LVL0 age was being reported incorrectly for standby DB's.
  • 4.03 (Base) Bill Border 24Feb05
  • (Oracle/UX) New performance events:
    • &event("P",$thishost,"MTS is being used for this Non-RAC/OPS instance - Bad for performance - mts_queue=$mts_queue[$thishost]","MTSOn","DBA919");
    • &event("P",$thishost,"UNDO_MANAGEMENT Is not set to AUTO - It should be - undo_mgmt=$undo_mgmt[$thishost]","UndoAutoOff","DBA925");
    • &event("P",$thishost,"FORCE LOGGING Should be turned on - force_logging=$force_logging[$thishost]","ForceLogOff","DBA926");
  • 4.02 (Base) Bill Border 26Jan05
  • (Oracle/ALL) New event for the presence of an SPFILE. We don't use SPFILE, so we need to know where it is being used. This is only active if the Run_SPFile_Check: dbamonrc parameter is set to Y.
  • 4.01 (Base) Bill Border 19Jan05
  • (Oracle/NT) New Oracle/NT Performance Monitoring. Most metrics monitors for Oracle on UX are now monitoring for Oracle on NT.
  • 4.00 (Base) Bill Border 08Jan05
  • (ALL) New event classification:
    • New "S" Security Event Type
    • New "P" Performance Event Type
    WWW Reports changed to accomodate this change.
  • New Security Exceptions Report. This was created because we now have a role of security administrator. This report will become a to-do list for that person of security exceptions to fix. The DBA293 event (Probe Connect Timeout) is now a W event (it was C.) It didn't make sense for this to be C since it is almost always followed by a DBA290C event.
  • 3.95 (Base) Bill Border 16Dec04
  • (ALL) The DBA293 event (Probe Connect Timeout) is now a W event (it was C.) It didn't make sense for this to be C since it is almost always followed by a DBA290C event.
  • 3.94 (Base) Bill Border 14Dec04
  • (Oracle/UX) New performance monitor to see if the buffer cache has < 10 free buffers. In this case, a User event occurs. It is a rule-of-thumb that if your instance has no free buffers, then it could benefit from a larger buffer cache.
  • (Oracle/UX) For 10g, DBAmon will automatically detect which port the OEM WWW interface uses, if configured. On the WWW Instance Summary there will be a URL to the OEM WWW interface for that instance.
  • 3.94 (Base) Bill Border 25Nov04
  • (All) Many changes for a new Sun installation. Syntax changes to many grep commands.
  • 3.93 (Base) Bill Border 23Nov04
  • (Oracle/UX) The component mismatch event now will only occur on thread=1 in RAC/OPS clusters.
  • (Oracle/UX) Now "problem DB userids" will be automatically fixed.
  • 3.92 (Base) Bill Border 29Oct04
  • (Oracle/NT) DBAmon now correctly handles monitoring an instances whose listener password is set.
  • 3.91 (Base) Bill Border 22Oct04
  • (Oracle/UX) Now for OPS/RAC clusters, tablespaces will be monitored only on instance=1. This will eliminate duplicate events and improve performance.
  • 3.90 (Base) Bill Border 20Oct04
  • (ALL) The remsh retry logic has been enhanced to only create a DBA293 event on the LAST retry. Previously an event was occuring once per retry.
  • 3.89 (Base) Bill Border 11Oct04
  • (MSSQL) New check for how full any Drive is that contains MSSQL database files. New DBA805 event. The DBC parameter T_Disk_Full: controls this feature. The default is 95/99.
  • 3.88 (Base) Bill Border 28Sep04
  • (MSSQL) The MSSQL Transaction Logs are now monitored. See MSSQL TLog Monitoring for details.
  • 3.87 (Base) Bill Border 09Sep04
  • (Oracle/UX) The format of event DBA642 was altered to place the percentage near the beginning of the event text.
  • 3.86 (Base) Bill Border 10Aug04 Changes for MSSQL:
  • The TLOG size is percent full is now measured.
  • The MSSQL lightbulb now displays TLOG status for each database.
  • 3.85 (Base) Bill Border 10Aug04 New monitoring capability:
    • Oracle/NT 9i
    • Oracle via ssh
    3.84 (Base) Bill Border 27Jul04 Some improvements to the patch reporting.
    3.83 (Base) Bill Border 11Jul04
    3.82 (Base) Bill Border 11May04
    • (All) Change to Instance Summary WWW pages: Now the OS type and Comm_Method: will be displayed next to the DBMS version.
    3.81 (Base) Bill Border 24Feb04
    • (Oracle/UX) New check for "orphaned" datafiles. See error documentation for DBA313 for details.
    3.80 (Base) Bill Border 20Jan04 2 new DBC parameters:
    • (All) New parameter Suppress_Events:. Specify a list of event ID's (DBAnnn,DBAnnn) to suppress for this instance. This is handy for DB's with systemic problems that will never be solved.
    • (All) Fixed bug which prevented events from being generated for Oracle/UX process table overflow.
    3.79 (Base) Bill Border 02Dec03 2 new DBC parameters:
    • (All) New parameter Priority:. Specify H, M or L for the priority of this instance. Is passed to Ticket Creation Interface.
    • (All) New parameter Make_Tickets:. Specify Y or N for whether to create tickets for this instance.
    3.78 (Base) Bill Border 28Oct03
    • (Oracle/UX) The default threshold for T_Read_Hit: now, if not specified, is 80% (it was 90%).
    • (All) The Event History Viewer now allows you to report on ONLY C, W, I or U events.
    • (Oracle/UX) New DBA312 event which occurs when a non-SYS* DB user has been granted the DBA role.
    • (MSSQL) Fixed problem where automatic rerun of backups was not working correctly.
    3.77 (Base) Bill Border 18Sep03
    • (All) DBAmon now counts the number of databases in all Oracle, Informix and MSSQL instances. The count is reported in the instance summary. Also, the total amount of space allocated by DBMS is reported there.
    • (All) New dbamonrc parameter: Probe_Timeout:. There is now code in DBAmon to automatically kill any outbound connection after this number of seconds.
    3.76 (Base) Bill Border 03Sep03
    • (Informix/UX) There was a problem where a DBAmon Internal Error email message resulted from the chunks not being readable by the Userid: specified in the DBC file. Now, there is a new Event for this condition.
    • (Oracle/UX) DBAmon now monitors for whether the next extent of an object will fit in the designated tablespace. This is in addition to monitoring for full tablespaces.
    • (All) New dbamon_dbc_compile routine which compiles the DBC files into the repository. This compiled data will be used in a future release which contains a WWW-based DBC update feature.
    • (Oracle/UX) Before this release, DBAmon would monitor for passwords matching userid's, even for standby DB's. Now, we only monitor for this in non-standby instances.
    3.75 (Base) Bill Border 19Jul03 (Oracle/UX) New DBC Parameter: DF_Offline_Sev: . The default severity of the "Offline Datafiles" event is C (critical). With this new parameter, you can override that severity to W, I or U. We have a DB with known offline datafiles that we do want to monitor.
    3.74 (Base) Bill Border 25Jun03 (Oracle/UX) New logic to alter the listener.ora to permission=700 and to set a listener password.
    3.73 (Base) Bill Border 14Jun03 (Oracle/UX) New Monitor: UX NFILE's. If the total number of UX file descriptors is within 90/95% of the Kernel NFILE parameters, Warning/Critical event will occur.
    3.72 (Base) Bill Border 02Jun03 (Oracle/UX) New DBC parameter: In_Sync_Unrec_Sev: . With this parameter you can specify the severity of the DBA668 event.
    (Oracle/UX) There was a bug in the LAN half-duplex checking. Also, there were a few probe STDERR messages which were falsely causing DBAmon to re-rcp the software every iteration. Fixed.
    3.71 (Base) Bill Border 19May03 (Oracle/UX)New Performance event:
    • DBA923 - Rollback Segment Header Waits to Gets ratio.
    Also, new END_OF_PROBE string now appears at the end of every probe execution. This will help to diagnose Database hung problems.
    3.70 (Base) Bill Border 14May03 (All)The ID4: DBC parameter is now fully implemented. Also, there is a new dbamonrc parameter: ORACLE_Password: which specifies the Oracle Repository password for user=dbamon.
    3.69 (Base) Bill Border 05May03 (Oracle/UX)New events:
    • DBA308 - The DB is in archivelog mode, but the archiver is STOPPED.
    • DBA308 - The DB is hung because all online redo logs are full.
    3.68 (Base) Bill Border 30Apr03 (Oracle/UX)Major improvement to Primary/Standby InSync monitoring. New DBA668 event for which occurs when an unrecoverable change is detected on the primary SINCE the last standby rebuild.
    3.67 (Base) Bill Border 29Apr03 (Informix/UX)New DBA238 event for Informix objects that approaching the 32gB object size limit.
    3.66 (Base) Bill Border 28Apr03 (Oracle/UX) DBAmon will now work with listeners that are configured with a password.
    3.65 (Base) Bill Border 25Apr03 (MSSQL) It is now possible to monitor MSSQL using ssh. The Connect_Method: and Userid: DBC parameters now work for DBMS: MSSQL.
    3.64 (Base) Bill Border 21Apr03 (Oracle/UX) New check for Oracle userids that have passwords equal to the username. For system passwords that are predictable, DBAmon can automatically change the password to one of your choosing.
    3.63 (Base) Bill Border 31Mar03 (ALL) New dbamonrc WWW_Event_Isolate parameter. Specify here DBAmon Events that you want to isolate to seperate WWW pages. A URL to these events will appear at the bottom of the Short and Long Instance Summary pages. If you specify more than one msgid, separate then with commas.
    3.62 (Base) Bill Border 28Mar03
    • (ALL) When DBAmon task(s) were in the middle of an iteration after a DBC file had been added, or after DBAmon has been started, the "Lightbulb" check did not work. This has been rearchitected, so the issue is gone.
    • (Oracle/UX) New DBA655 event which measures the number of dbwr_io_slave's versus the Oracle maximum of 40.
    • (ALL) New WWW_Font: dbamonrc parameter.
    3.61 (Base) Bill Border 24Mar03 (Oracle/UX) New Filesystem Capacity checking feature. See FS Checking Overview for details. New FS_Check* DBC parameters.
    3.60 (Base) Bill Border 27Feb03 (Oracle/UX) New DBC parameter: Alert_Log_Check:. If you set this to N then DBAmon will not perform normal Oracle Alert Log checking for this instance.
    3.59 (Base) Bill Border 27Feb03 (Oracle/UX) New performance event which detects OTRACE being on. If any .dat files are found in ORACLE_HOME/otrace/admin, then a DBA913 event occurs (Critical Event). OTRACE can cause performance problems and Oracle recommends that it be off. Also, DBAmon now checks the instance-level setting of SQL_TRACE. If it is set to TRUE, then a critical event will occur.
    3.58 (Base) Bill Border 26Feb03 (Oracle/UX) New Prevent_DB_Restart: DBC parameter. If this parameter is set to Y then even if Monitor: is set to Y DBAmon will never attempt to automatically start the DB if it crashes.
    3.57 (Base) Bill Border 21Feb02 (ALL) New Mailer , Mass Mailer and Notepad Search transactions. Also, the Notepad Edit transaction has been rewritten to improve useability.
    3.56 (Base) Bill Border 13Feb02 (Oracle/UX) Change to the dbamon_ora.pl probe. It now will immediately exit if the STATUS from V$INSTANCE is not OPEN. There was a theory that a few ORA-00600 [17059] errors that we have seen were caused by DBAmon querying DBA* tables while a DB was transitioning from MOUNTED to OPEN. This cannot occur now.
    3.55 (Base) Bill Border 07Feb03 (All) New STARS email interface.
    3.54 (Base) Bill Border 03Feb03 (All)New dbamon_stethoscope program.
    3.53 (Base) Bill Border 29Jan03 (All) New DBMS Software Version Oversight feature. See Documentation for details.
    3.52 (Base) Bill Border 28Jan03 (MSSQL) Now, all events found in the MSSQL event log during one DBAmon iteration will be consolidated into one event, rather than each event causing the creation of one DBAmon event.
    3.51 (Base) Bill Border 27Jan03 (Oracle-UX) New test to see if there are any 'rman ' UX processes that have been running for more than 2 days. If any are found, a critical event will list the offending process PID.
    3.50 (Base) Bill Border 21Jan03 (All) New auto-detect of UX server netaliases. Any time that a UX server has a different hostname than the DBC file supplied hostname or any network aliases are detected, DBAmon will place these names on the WWW Instance Summary with a pointer to the hostname supplied in the DBC file. This feature is enabled if the dbamonrc Auto_Detect_Aliases paramater is set to Y. This feature only works for Oracle on UX.
    3.49 (Base) Bill Border 08Jan03 (All) Abandoned confusing version naming convention. Now, all release will simply increment the release number. Also, add RMAN LVL0 age detection.
    3.48 (Base) Bill Border 19Dec02 (Oracle-UX) For 9i Oracle databases, now the UNDO tablespaces are not checked to see if they are full. SMU does a better job of managing space in 9i.
    3.47 (Base) Bill Border 21Nov02 (Oracle-UX) New funtionality: Oracle RMAN LVL0 Backup Age checking.
    3.46 (Base) Bill Border 12Nov02 (All) New addition to Instance Summary Page ... Event History over the last 18 hours and last 7 days.
    3.45 (Base) Bill Border 11Oct02 (All) I got rid of the previous confusing release naming convention. Also, New DBAMON.EVENT_HISTORY table and new DBAmon Ticket Governor.
    3.44
    A Bill Border 04Sep02
    • 1. (Oracle/UX) - New Oracle performance monitoring (data block buffer hit ratio). Associated T_Read_Hit* DBC parameters.
    • 2. (MSSQL) - New MSSQL_Agent_Mon: DBC parameter. Specify as N to prevent agent monitoring.
    • 3. (Oracle/UX) - Refinement to Oracle performance monitoring (data block buffer hit ratio). Now, the db_block_buffer hit ratio will be ignored if the number of consistent gets is < 1000000.
    • 4. (Oracle/UX) - DBAmon will now do archivelog filesystem monitoring for multiple archivelog destinations (8.0 and above).
    • 5. (Oracle/UX) - In the archivelog filesystem full logic, DBAmon will optionally start an archivelog backup (or whatever command you specify with the DBC: T_Arclog_Command: parameter) if the archivelog filesystem is over the specified threshold full. There was an issue when DBAmon ran this command for a DB that did not have any archivelogs to backup. So, this enhancement will prevent the command from being invoked if there are 0 archivelogs to backup. destinations (8.0 and above).
    3.43
    B Bill Border 29Apr02
    • 1. (Informix/UX) - The way that users are counted has changed. Now, a query is run against sysuserthreads for non-informix threads. Previously, onstat -u was run and the 'max concurrent' number was captured. This will satisfy an IBM requirement which requires us to report the number of concurrent users.
    • 2. (All) - The Notepad icon now appears differently if there are notes for and instance versus if there are not any notes.
    • 3. (SAP) - Fixed a bug where under some circumstances, an SAP instance down was not detected.
    • 4. (Oracle/UX) - Enhanced InSync logic to check that the primary DB is up.
    • 5. (SAP/UX) - Under some circumstances, SAP being down (0 work processes) was not being detected. Fixed.
    A Bill Border 26Apr02
    • 1. (All) - Anther Major Enhancement A new WWW "Event Detail" page. If you click on the Event Severity values from the Instance Summary, you will see all events of that severity.
    • 2. (MSSQL) - Bug fix. If a DB name contained a space (this is actually legal in MSSQL) the history data was not being created properly, not was the Instance Detail page correct. Fixed. Also, there was a bug where the ticket text would sometimes be for the wrong instance. Fixed.
    • 3. (All) - New 'Marquee' on the Instance Summary which shows the instances with the highest event count during the last 24 hours.
    • 4. (Oracle/UX) - Monitor: B now also invokes the "InSync" feature.
    • 5. (Oracle/UX) - Monitor: B now also invokes the Oracle Tablespace Full routing for the purpose of collecting Tablespace Size History data.
    • 5. (Oracle/UX) - If the Magnify: dbamonrc parameter is set to Y, there is now an on-screen pulldown on the DBAmon Instance Summary where you can invoke immediate display commands.
    • 6. (All) - Usability enhancements made to the WWW "Notepad" feature. New WWW icon for Notepad on WWW Instance Summary.
    3.42
    A Bill Border 11Mar02
    • 1. (All) - Major Enhancement Dist lists are now in the repository.
    3.41
    C Bill Border 28Feb02
    • 1. (All) - New "InSync" capability. For standby databases There was a bug in the bin/dbamon logic in how tasks were divided up when you use the task_config file. Fixed.
    • 2. (All) - The event message for the "Fileage" event now displays a range of ages instead of the precise age of the file. This will prevent numerous consecutive duplicate events.
    B Bill Border 31Jan02
    • 1. (Oracle/UX) - New "InSync" capability. For standby databases it is sometimes necessary to monitor how far 'out of sync' the standby database is from its primary DB. This new feature measures this time and creates events depending on the In_Sync_Age: parameter that you specify in the DBC Configuration for Oracle/UX.
    • 2. (All) - New DBAmon "Lock" capability. Sometimes there are processes that you may need to run against a DB which will cause DBAmon events. For example, a standby DB refresh that runs periodically that stops and starts Oracle. During that time, you do not want to receive DBAmon tickets that your DB is down. So, this new feature, which only works for Oracle on UX, will cause DBAmon to check for the existence of file /tmp/DBAmon_Lock_{ORACLE_SID}.txt. If this file does exist, then DBAmon will sleep until the file does not exist. Note that if the file exists for > 10 minutes, dbamon_checker will detect a hung probe and it will kill the probe. This will show up a connection error. So, if this feature is used, ensure that the file exists for no more than 10 consecutive minutes.
    • 3. (All) - A feature was added to the "InSync" logic: the ability to detect whether NOLOGGING tables or indexes exist on the Standby DB's primary DB. See: DBAmon Error DBA666.
    • 4. (All) - BUG Fix: When running in multi-task mode with a task_config file, the letters not contained in the task_config file were not being properly assigned. Fixed.
    A Bill Border 31Dec01
    • 1. (All) - New dbamonrc parameter Loc_Breakout: which, if speficied as Y, will cause a breakout by network location to appear on the WWW Instance Summary.
    • 2. (All) - The ID1, ID2 and Network Location breakout 'scoreboards' of the WWW Instance Summary now show an average Health Index for each entry. Also, the "Event Severity" / "Event Count" scoreboard now more accuratly reflects the total number of events of each type. Previously, it only counted the first event of each severity for each instance.
    3.40
    A Bill Border 20Nov01
    • 1. (Oracle/UX) - Major Enhancement DBAmon now is compatible with Oracle/UX Version 9i.
    • 2. (Oracle/NT) - The backup type is now correctly reported. Also, the table DBAMON.BACKUP_AGE is now interrogated. If it exists, then it will be used solely.
    • 3. (Oracle/UX) - Another Major Enhancement New "Magnifying Glass' WWW feature. This feature is active if the WWW_Magnify: dbamonrc parameter is set to Y. The magnify feature only works for Oracle/UX databases. If you click on the magnifying glass that is next to each instance on the WWW Instance Summary page, you will see a menu of possible commands that you can run. The first type is orastat commands which can be used to display most Oracle DB metrics. Most of the more commonly used orastat commands are displayed on this menu. The second type of command on the menu is 'oraadmin' commands. These commands allow you to:
      • Start Oracle
      • Stop Oracle
      • Change archivelog Mode
      • etc.
      all from the WWW (you don't have to logon to the server).
    • 4. (Oracle/NT) - Another Major Enhancement The "Magnifying Glass Feature" now also works for Oracle/NT. Same functionality.
    • 5. (Oracle/NT) - Fixed bug where the Listener status would always be checked, even if Oracle is down.
    • 6. (Informix/UX) - Changed dbamon_arc_ontape to remove references to 'xd'. DBAmon no longer requires xd.
    • 7. (All) - Cleaned up some error messages; got rid of a few duplicates. Enabled Filecheck code - events.
    • 8. (Informix/UX) - An error in the logic of infLocks prevented backup age checking from work for Informix V5. Fixed.
    • 9. (All) - There was a bug whereby some critical events had a message text which contained a newline. This caused some events to be treated as duplicates erroneously. Fixed.
    3.31
    C Bill Border 06Nov01
    • 0. (Oracle/UX) - The Oracle SGA is now checked for being full. If it is >= 90% full, an INFO event will occur; if it is >=95% a WARNING event will occur. At some time in the future, I will change these severities to CRITICAL and WARNING.
    B Bill Border 19Oct01
    • 0. (Oracle/UX) - New code which will automatically attempt to restart broken archive log destinations. If a destination is in error status, DBAmon will automatically find the appropriate "log_archive_dest_?" parameter and issue the alter system command to reactive the destination.
    • 1. (Oracle/UX) - There was a bug in the logic which automatically alter tables and indices to MAXEXTENTS UNLIMITED. If the object name contains a $, it would fail. Fixed now.
    A Bill Border 21Jun01
    • 1. (OracleApps/UX) - Rewritten. Added many new parameters; see DBC Configuration for Oracle/Apps. Also see What DBAmon Monitors for what is now checked for OracleApps.
    • 2. (All) - It was noticed that if a DBC file was removed during DBAmon execution, under some circumstances, the software would not be downloaded for the remaining instances. Now, if a DBC file changes, the software will be downloaded always on the next iteration.
    • 3. (All) - New dbamonrc parameter: Id1_Breakout:. This causes DBAmon to create a separate WWW page with all DBC ID1: values. Submit a support request for more information.
    • 4. (Oracle/UX) - Previously, if an archive destination was ever in ERROR status, a critical event would occur. Now, if the destination in ERROR status is OPTIONAL and the REOPEN value is non-zero, then the event will only be a WARNING.
    • 5. (All) - Under some circumstances, the software download software was not correctly be reloaded when is should have been. Fixed.
    • 6. (All) - New condensed Instance Summary which has pointers to other pages with the actual instance details. For example, if you view this page, all of the instances on servers whose names begin with A are listed, and so on. This change only applies to users who use the Oracle repository.
    • 7. (All) - New ID1_Breakout: and ID2_Breakout: dbamonrc parameters. If specified as Y, then instances will be additionaly summarized by their ID1: and ID2: DBC values.
    • 8. (Oracle/UX) - New T_Arclog_Command: DBC Configuration for Oracle/UX parameter. When and Oracle archivelog filesystem reaches either the warning or critical threshold (defaults to 80/90), the command that you specify here will be invoked with "at now". Also, the default warning and critical threshold were changed from 90/95 to 80/90.
    • 9. (Oracle/UX) - New N Backup_Age: DBC Configuration Value. You can now enter an N in the DBC Configuration for Oracle/UX for the Backup_Age: parameter. This informs DBAmon that you will not be backing up this DB. The Backup Type that will display on the WWW Instance Summary will be bkDBCOff.
    • 10. (Oracle/UX) - The Status/Flags column of the instance summary will now show if T_Arclog_Cmd: is specified.
    • 11. (Informix/UX) - There was a problem when comparing the number of V shared memory segments to the critical and warning thresholds. The comparison was character instead of numeric. Fixed.
    • 12. (Oracle/UX) - Change in the behavior of Oracle extent monitoring. There used to be a parameter "Fix" which you could specify which would instruct DBAmon to attempt to ALTER TABLE ... MAXEXTENTS UNLIMITED when the T_Extents: threshold was exceeded. Now, this ALTER TABLE is always attempted UNLESS you specify NOFIX. The reason for this change is that there is no good reason to not alter the table.
    • 13. (All) - DBAmon no longer pre-deletes all /tmp/dbamon* files before downloading.
    3.30
    I Bill Border 30May01
    • 1. (Oracle/UX) - New check for Online Redo Logs in exception status. Creates critical event if any are encountered.
    • 2. (Oracle/UX) - New check for the number of processes versus the configured init.ora "processes" parameter. This will proactively prevent outages caused by procecesses being exceeding by notifying before it reaches 100%.
    • 3. (Informix/UX) - DBAmon now collects the concurrent sessions HWM. It is displayed on the "D" Details WWW page and is saved as STA history data.
    • 4. (Oracle/UX) - Significant performance improvement in the Oracle Tablespace Full checking logic. In one case, elapsed time went from 10.5 minutes to 2 seconds.
    • 5. (Oracle/UX) - Extent checking is now only done every 10th iteration, to improve throughput.
    • 6. (Informix/UX) - The former "zero divide #5" in infDBS.pl is now an event. I was too easily overlooked before. It also now will detect if dbaccess did not run because TEMP dbspace is full.
    • 7. (All) - Whenever a Server NOT-Pingable error is detected, the download_software flag will be turned off causing DBAmon to reload the software during the next attempted communication. before.
    H Bill Border 16May01
    • (All) - New dbamonrc parameter: . Should only be if suggested by DBAmon support. Prints diagnostic data to the Day log.
    • (All) - The Day log files (/opt/dbamon/log/Mon,Tue, ...) now show detailed text for all events.
    • (All) - There are now stdout messages written when every code section starts.
    • (All) - The Local_Or_Remote: DBC parameter is now obsolete. All monitored servers are treated as remote.
    • (Oracle/UX) - The Oracle DBID is now captured. It is displayed on the "D" WWW page and in the MISC3 column of the dbamon.instances table.
    G Bill Border 22Apr01
    • (SAP-R3/UX) - DBAmon now monitors SAP/R3 on Unix. See What DBAmon Monitors for details on what is monitored. New SAP DBC Parameter: SAPSYSTEMNAME .
    • (All) - New userexit: Ticket that in onvoked in order to create Call Tracking System tickets. See: DBAmon Userexits for details. Module dbamon_make_ticket.pl is now obsolete.
    • (Oracle/UX) - There was a bug where if the include= init.ora parm contained a ? (short for ORACLE_HOME), it could not be opened properly. Fixed.
    • (Oracle/UX) - There was another bug if you are extent checking and you have partitioned tables, the wrong column was being read. Fixed.
    • (Oracle/UX) - There was yet another bug in the expansion of the * DBC value for ORACLE_HOME. If it changed during DBAmon execution, it was not being re-read properly.
    • (Oracle/UX) - There string 'corrupt' is now looked for in the alert log.
    • (Oracle/UX) - Some customization to detect different backup types.
    • (Oracle/UX) - New Alerts: init.ora Parameter Errors:
      • If large_pool_size > 0 and backup_tape_io_slaves is FALSE and dbwr_io_slave is 0, then create EVENT
      The event severity is Warning.
    • (All) - Previously, the requirements for Perl were that there be a link in /usr/local/bin/perl on monitored servers and /usr/bin on the Master. Hmmm... It is now consistent in that there must be a symlink which invokes Perl V5 called /usr/local/bin/perl on both the Master and the Monitored server.
    • (All) - Fixed major problem in reading the dbamonrc file when you are not using the repository. Thanks to Eric at Worldcom.
    • (All) - Solved problem where gzip was not found on non-HPUX OS's. Also, converted all bdf's to df -kPl. Also converted all ll's to ls -l. Thanks again to Eric at Worldcom.
    F Bill Border 10Apr01
    • (Oracle/UX) - When tablespace full checking occurs, DBAmon will automatically coalesce any tablespace which contains 'TEMP' before reporting that it is full.
    • (Oracle/UX) - When tablespace full checking occurs, DBAmon will automatically SHRINK all active rollback segments if the tablespace name contains 'RBS', before reporting that it is full.
    E Bill Border 18Mar01
    • (Informix/UX) - New check: INFORMIXDIR Filesystem Full . If the filesystem containing the INFORMIXDIR directory is >= 99% full, a critical event will occur.
    • (Informix/UX) - There are now 4 new Informix DBC Parameters that are easier to remember than the old names:
      Old ParameterNew Parameter
      Informix_Dir: INFORMIXDIR:
      Inf_Server: INFORMIXSERVER:
      SQL_Hosts: INFORMIXSQLHOSTS:
      ON_Config: ONCONFIG:
      Note that the old parameters will still work, but new DBC files should use the new parameters.
    D Bill Border 13Mar01
    • (Oracle/UX) - New Oracle Automatic Crash Restart. For most common Oracle crashes, DBAmon will automatically startup the instance, drastically reducing downtime. See: What DBAmon Monitors for details on when this will occur and under what circumstances.
    • (MSSQL) - If the automatic rerun of a backup (DBC Backup_Command: parm) in foreground fails, then DBAmon will now make a critical event.
    • (All) - There was a bug where DBAmon Program Errors did not attach diagnostic data. Fixed.
    C Bill Border 07Mar01
    • (All) - The syntax of the DBC files are now checked (I don't know why I didn't do this long ago). If a bogus parm is specified, an error message will be EMail'ed to the Admin_EMail: (dbamonrc) email address.
    • (MSSQL) - New Backup_Command: DBC parameters allows you to automatically invoke and NT command any time that backup age is exceeded for any DB listed in the Backup_Check_DBs: DBC parameter. This can be used to automatically invoke an MSSQL backup. Note that you have to provide the backup command to be invoked. See MSSQL DBC File Configuration Reference .
    • (All) - New dbamonrc parameter Paging which controls whether to activate the paging logic. The default is Y. We would only specify this in our DBAmon test instance as N, to prevent paging while running DBAmon in test mode.
    • (All) - New Download_Every: DBC Configuration Parameter to instruct DBAmon to re-download the DBAmon probe software on every iteration. Only use this if asked to by DBAmon support.
    • (Oracle/UX) - New Oracle/UX feature where DBAmon will automatically save the init.ora file on your DBAmon Master. It will be stored in: /opt/dbamon/dat/config_save/config.{ServerName_{DBC_Title1}. This feature could Save Your Bacon if you have a catastropic server failure and need a copy of the init.ora file.
    B Bill Border 28Feb01
    • (Oracle/NT) - New logic to Monitor Tablespace Capacity for Oracle/NT. This works a little different than on UX in that if *ANY* datafile of a tablespace has AUTOEXTEND=ON, then no events will occur for that tablespace. Setting AUTOEXTEND on is a more common practice on NT.
    • (All) - New DBAmon History Repository Database data: SPC DB Space Utilization Data. Note that for now this data is also written to /opt/dbamon/dat/history/dbspaces. At some future date, this data will only be written database and not to the dbspaces directory.
    • (All) - Some minor cosmetic improvements to the Instance Summary WWW Page: The Event short text indicators now appear in a smaller font and they are "click-able" to get you to the Events Page for an instance (previously only the E URL for an instance would get you there).
    • (All) - The T_TS_Full: (Oracle) and T_DBSpace_Full: parms now work slightly differently. If they are not specified for any instance, then TBLSpace/DBSpace monitoring will not occur.
    • (All) - New Iter_Min_Secs: dbamonrc parameter. If specified, tells DBAmon that no single iteration should run for less than this number of seconds. If an iteration completes in less than the number of seconds specified here, DBAmon will sleep the difference between the the iteration duration and this number before starting the next iteration. For example, if this number is set to 600 (10 minutes) and an iteration completes in just 6 minutes, then DBAmon will sleep for 4 minutes before starting the next iteration. This feature prevents DBAmon from "beating up" a DB server. This parameter is similar to the Sleeptime: parameter, but is more sophisticated in the the sleep only occurs if the iteration ran quickly.
    A Bill Border 26Feb01
    • (All) - Major Enhancement
      The main module dbamon.awk which was about 8500 lines long has been rewritten in Perl. It was also modularized and broken down into many independant modules. This will give DBAmon much better flexibility and will greatly improve performance. I will now be able to run all Oracle DBI calls from the main program which will eliminate expensive context switching to invoke external programs to perform DB access. DBAmon now connects to the Oracle repository DB once at the beginning and stays connected for the entire time that DBAmon is active, again saving the overhead of constantly connecting and disconnecting. When DBAmon was first written in 1993, awk was the scripting language of choice and Perl was in its infancy.
    3.25
    E Bill Border 06Feb01
    • (All) - All dbamonrc SYSTEM section parms that begin with HTTP or HTML are now obsolete. Always, ALL WWW output is written to /opt/dbamon/htm without exception. All URL on pages that are create there are relative to /opt/dbamon/htm . If these are specified, then DBAmon admin will receive a warning EMail.
    • (All) - New module dbamon_mailer is used to send all mail. dbamon_mailer uses sendmail, not mailx which used to be used.
    D Bill Border 01Feb01
    • Oracle/UX - An event now occurs if any archive destination is in ERROR status.
    • Oracle/UX - If an archive log dest ended in "/", the archive log FS full check did not work. Now it does!
    • Informix/UX - DBSpace full events will not occur for HDR-Secondary instances.
    • (All) - Remsh Retry. A new dbamonrc parameter. This parameter controls how many times DBAmon will retry a failed connection. Every communication from the DBAmon Master uses the "remsh" UX service. If this parameter is set to > 0, then if a remsh connection fails for any reason (most probably due to network problems), then the connection will be retried Remsh_Retries: number of times after sleeping 30 seconds.
    • (All) - New dbamon_checker utility which runs from cron which replaces the old dbamon_mgr. Its job is to:
      1. Kill any hung connection to a DB server that has been running for > 10 minutes.
      2. See if all DBAmon tasks are running (from /opt/dbamon/adm/processes_prod.txt). If any tasks listed there are not running, dbamon_stop is invoked to kill all DBAmon tasks, and DBAmon is restarted.
      Change your cron entries which currently invoke dbamon_mgr to look like: Software Installation Instructions.
    • (All) - STA/sessionshwm being recorded.
    • (All) - STA/buf/dict/lib-hitratio being recorded.
    • (All) - New static DBAmon Historical Graphs link on the instance summary page. This link points to a new directory /opt/dbamon/htm/graphs. These graphs are created by optional SAS programs which I can provide.
    • (All) - New DBAmon functionality: DBAmon History Repository Database. This is new logic where historical data is written to a repository table. Measures being recorded now are:
      • STA/sessionshwm - Oracle concurrent sessions HWM
      • STA/buf/dict/lib-hitratio - Oracle shared pool hit ratios
    C Bill Border 05Jan01
    • Oracle/NT - DBAmon will now check the log_archive_dest disk to ensure that it is not full. The Warning/Critical thresholds are 90/95. The DBC T_Arclog_Full parameter controls these thresholds.
    B Bill Border 28Dec00
    • MSSQL/NT - The report that is created in the (E)vents WWW page when the Backup_Age: is exceeded will not display all registered MSSQL backups for the DB in question. This will aid in troubleshooting the event.
    • (All) - If you are using the Oracle Repository, then the new Instance Summary now has a URL when you can click to see only the Instances of that DBMS. For example, in the "Scoreboard" section under the heading "DBMS/Application" you see Informix, Oracle etc.. Those strings are now URL's to the page that contains the Instance Detail only for that DBMS.
    • Informix/UX - Version 5 of Informix is now fully supported.
    A Bill Border 02Dec00
    • MSSQL/NT - Enabled logic where you can now specify DBC parameter Perl_Path: if the Strawberry Perl bin dir is not in the default path.
    • Oracle/UX - DBAmon will now detect if the Oracle database is running in Standby mode. If it is, then the Instance Summary will indicate so. Also, there is a bug in Oracle (8.1.6?) where tablespaces sometimes will show RECOVER mode, when they are really ONLINE. The DBAmon code that checks for offline datafiles will now not report on datafiles that are in RECOVER mode on a Standby DB.
    • (All) - Major Enhancement:
      Due to numerous problems that we have experienced with MySql which had been used for years as the DBAmon data repository, the decision has been made to switch from using MySql as the DBAmon repository to Oracle. Coding begins in this release for this change. Stay tuned.
    • (All) - Another Major Enhancement:
      Coding has started to allow DBAmon to run Multi-Task mode. This will allow monitoring to occur in parallel, versus the syncronous mode that it previously ran in. This will help very large shops to reduce the lag time between the times that metrics are checked on DB servers. Again, stay tuned.
    3.24
    E Bill Border 04Nov00
    • Oracle/NT - Official initial support of Oracle on NT. New dbc DBMS: value of Oracle/NT. For now, DBAmon will monitor:
      • Oracle is up
      • SQL will run
      • OracleServiceSID is active
      • Check for offline datafiles
      • TNSListener Service Active
      Monitoring of Oracle/NT will only work for version 8 of Oracle.
    • Instance Summary - New format of table where instance counts are displayed. New Hi/Lo version by DBMS column.
    • Parameters - Now, invalid DBMS: values will create an error that will be sent to Admin_EMail:.
    D Bill Border 02Nov00
    • Oracle/Linux - Officially support of Oracle on Linux. Configuration and operation is identical to Oracle/Unix.
    • MSSQL - Now there is Backup Age Monitoring. See MSSQL DBC Configuration for details on configuration.
    • Informix - Support for version 9 of Informix.
    C Bill Border 28Oct00
    • Instance Summary - Consolidated SAP version and disks columns to "Misc." column.
    • Oracle - For Oracle instances that run in OPS mode, the node number now displays on the instance summary.
    • Instance Summary - There is now a column on the far right which dislays the number of seconds spent monitoring each instance. This will simplify the debugging of communications problems which cause one instance to monopolize monitoring.
    B Bill Border 09Oct00
    • Oracle - DBAmon now checks to see if the filesystem where $ORACLE_HOME resides is >= 99% full. If it is, a critical event occurs.
    • Oracle - DBAmon now checks to see if the DB is in RESTRICTED SESSION. If it is, a critical event occurs.
    • Oracle - If an Oracle DB is running in OPS mode, then the service name in SQLNet is not predictable. DBAmon now detects if the DB is running in OPS mode; if it is, then we just run lsnrctl status to verify that SQLNet is running.
    A Bill Border 14Sep00
    • MSSQL Monitoring - DBAmon now monitors MSSQL. There is a new download dbamon_mssql.pl. It checks:
      • MSSQL Running (SQL will run, can see Master DB)
      • Alerts (If there are any alerts since the last time checked with SEV >= 17)
    3.23
    F Bill Border 26Aug00
    • MSSQL Monitoring (Well Kind Of ...) - The DBMS: .dbc parm now allows the value MSSQL. For now this can only be used for Monitor: N (documentation purposes). During the next few months, I will add some simple MSSQL monitoring.
    • SSH "Through The Firewall" Support - If you specify Comm_Method: ssh in the .dbc file, DBAmon will use ssh instead of remsh for communication. Instructions on how to configure ssh can be found at SSH Configuration. This feature allows us to monitor DB's that are outside of the firewall from inside the firewall.
    E Bill Border 11Aug00
    • MAJOR ENHANCEMENT - DBAmon now can automatically add datafiles to Oracle tablespaces (I can also do this for Informix if anyone wants). There is a new DBC parameter: T_TS_Command: where you can specify a shell command to be invoked when a tablespace reaches its WARNING threshold. See DBC Configuration for further details. This parameter is used properly can fully automate expansion of Oracle tablespaces.
    • When an Oracle instance is running OPS (Oracle Parallel Server) this is now recognized. An "OPS" indicator will appear under FLAGS on the Instance Summary. Future versions will check OPS status.
    • Perl V5.6 is now recognized as valid.
    D Bill Border 13Jul00
    • New WWW interface from the Instance Summary to View AND EDIT the inhibit file for an instance. No more need to vi Inhibit Files. Changes were made to CGI dbamon_inhibit.pl.
    • Added new Backup_Command: dbc parameter to facilitate automatic restarting of Oracle backups (I will do Informix shortly). If this parameter is present for an instance, when a backup age exceeded event would have occured, DBAmon will automatically issue this command instead of the critical event. The command is issued by dbamon_ora at an at now command. This will save MUCH TIME in our issuing backup rerun commands. If on the iteration following the issuing of this command a backup is not running and the age is still exceeding the threshold, then a critical event will occur.
    • Software download errors are now critical events. We had a case where there was a disable Oracle account causing the download to fail and we never noticed it.
    • On the Instance Summary the DBMS values are now color coded (easier to read).
    • Added the same Backup_Command: code for Informix. It works the
    • Fixed bug where the comparison to see if a Tablespace/DBSpace was full was not numeric but character. It now works to set the critical threshold to 100 (I wonder how we went all of those years with this bug?). same as for Oracle.
    C Bill Border 23Jun00
    • Added new dbamonrc parameter Remsh_Sev: which determined the severity of remsh errors. It can be set to W or C (warning or critical). The default is W. This can eliminate pages (and tickets) for bogus remsh errors.
    B Bill Border 01Jun00
    • Added code to the Informix Logical Log Full check to better diagnose dbaccess errors.
    • Changed all mailx statements to specify the -m option which prevents the MIME headers from being included. We were getting some MIME messages on our pager
    • Fixed problem with pager notification. If you had specifed Pager_EMail: and not a subject it was not working. It now fills in a default subject if one is not supplied.
    • The Oracle DB up check was missing the DB not being OPEN. It now tried to run SQL against a non-existent table which will fail if the DB is not open and will create a critical event.
    A Bill Border 17May00
    • Fixed some Oracle monitoring problems in download dbamon_ora.pl. If a DB server has > 1 instance and the name of instance A is part of the name of instance B it became very confused. Also, there is an Oracle bug which prevents svrmgrl from reading data from a here document. I added code to dbamon_ora.pl to put an obvious message in the Event Log if this happens indicating which patch to apply.
    • New monitoring mode Backup-Only Monitoring. This was coded for a need to just monitor backup age. There is a new value for Monitor: DBC parameter: B. See DBC Configuration for details.
    • Downloads: Added code to prevent multiple downloads to one host. This was previously a common occurance where there were multiple DB's on one host. Now a flag is set to prevent >1 download per host.
    • Fixed bug in Oracle download monitor where if a filesystem name was long then the Archive Log Dir % full was incorrectly retrieved.
    • Added code to detect an Oracle bug in Oracle 7.3.4. There is a bug 622943 which prevents svrmgrl from reading from STDIN. Without a fix for this bug, nothing will work from DBAmon. I added a message that displays with the DB DOWN message instructing the user to apply this patch.
    3.22
    Q Bill Border 15May00
    • Added Oracle Backup Aging. At the present time, it only works with ora_backup which employs the RMAN/Veritas interface. It works the same way as with Informix (Backup_Age: .dbc parameter).
    • Minor change to Instance Summary to display the backup method in the backup age column (why didn't I do it that way in the first place?).
    • Addition of new DBAmon logo in the Instance Summary page. This new logo (a jpg file) is supplied in the /opt/dbamon/images directory.
    • Changed all mailx command to use the "-m" switch to disable MIME encoding. The problem was that DBAmon messages that were sent to Outlook produced a message about being unable to decode.
    • Cleaned up the .dbc parameters that control paging. Now, if you specify Paging_EMail: an email will be sent to that address (assumed to be a pager) unconditionally. I added Custom Code to allow the DUMMY Pager_Subject: parameter to work only for ???.
    P Bill Border 01May00
    • I encountered a server where Perl5 was not installed. This naturally prevented all monitoring from working since the downloaded .pl modules are coded in Perl5. I added a check to the download section where it checks the version of Perl by running /usr/local/bin/perl -v. Thus, a prerequisite to running DBAmon is also that /usr/local/bin/perl points to the Perl 5 executable.
    • DBAmon will now recognize a backup type of RMAN by looking in cron.
    N Bill Border 24Mar00
    • A new check for Oracle: Archive Log Dir Full. There is a new Configuration parameter T_Arclog_Full: for Oracle.
    • The Instance Summary Now Displays the Oracle Backup Type and whether Archive Logging is ON.
    M Bill Border 25Feb00
    • A new check for Oracle: Object Extent Checking. There is a new Configuration parameter T_Extents: for Oracle.
    • There is a new MYSql table: instance which is recreated at the end of each iteration with information about all DB's being monitored. The table looks like:
      Field   Type    Null    Key     Default Extra
      status  char(1)
      system  char(16)
      instance        char(16)
      model   char(16)
      os      char(8)
      dbms    char(8)
      dbmsver char(12)
      dbmssn  char(16)        YES             NULL
      alloc   int(11)                 0
      used    int(11)                 0
      ts      timestamp(14)   YES             NULL
          
    L Bill Border 07Feb00
    • New Oracle monitoring routine: oraAlerts. This new alert checks the Oracle alert log for words that you can configure (error, full, ...). See Configuration for additional details.
    • New System Parameter: Use_MySQL:. This parm should be specified as Y if you are going to use MySQL DBMS calls.
    • New Host Parameters: Monitor_Hours:, Monitor_Days: and Monitor_Exclude:. These parms will tell DBAmon to only monitor during certain Hours and Days of the week. See Configuration for details.
    • Ontape backup aging Y2K fix. If a backup timestamp read from the reserved page is in the future, it is discarded. We were having a problem where L1's taken after the date on a server was returned to normal were not overwriting backup dates recorded during Y2K testing (future date). Changed module dbamon_arc_ontape.
    K Bill Border 25Jan00
    • There was a bug in Informix ontape backup age checking where if the dbamon_time script failed that an event would be created because a time value of 0 was used. Added code to dbamon_arc_ontape to ensure that a valid time value was retreived.
    • Fixed a problem where the tablespace size (Oracle) was not calculated correctly for large tablespaces.
    • Changes to dbamon_ora to tolerate Oracle 7.*. See DBAmon Home Page for Oracle version compatibility.
    • There is a report at the top of the System Summary stating how many Informix and Oracle instances are being monitored.
    J Bill Border 10Jan00
    • The Oracle oraLsnr check (listener active) will now restart the listener if it is not active.
    • The Oracle oraUp check now will check for the presence of the database name in /opt/oracle/adm/config/ora_chk_instance.excl. This was done to accomodate the tools being used by our colleagues in Roseville to stop and start Oracle for offline backups.
    • There is a new Informix check for the number of used NFILE's. The routine is called infNFile. The data is gathered by the check_locks routine.
    • I renamed the old download pgm dbamon_locks.pl to dbamon_inf.pl. All new Informix routines will go into this module. At some point in the future, I want to have only 2 downloads, one for Informix and one for Oracle.
    I Bill Border 29Dec99
    • To improve performance, the check for LTAPEDEV value (Informix logical log archiving) is done by the DBSpaces function.
    H Bill Border 20Dec99
    • More Oracle Montoring. Now monitors the Listener and Tablespaces. See What Is Monitored for more details.
    G Bill Border 15Dec99
    • DBAmon now monitors Oracle instances. The first check (more is to come) is whether the instance is active (able to run SQL and the required daemons active).
    F Bill Border 08Dec99
    • New dbamonc instance config parm: Monitor: - If this parm is set to N no monitoring will occur. This is useful for customer who do not purchase our monitoring service. In that case, we want to track the instance with DBAmon, but we do not want to monitor anything. Instances in that state will show up white on the System Summary. Details are on the configuration WWW page of the DBAmon home page.
    • Recoded the code where the color or the Backup Age value is on the System summary.
    E Bill Border 22Nov99
    • MAJOR CHANGE! - A new event type: USER EVENT. User events will create an entry in the HTML event log for an instance and will send email to the distribution list for that instance. This will be used for checks where we want the info only to be sent to the customer (longtx. extents, ...).
    • A new check: Long Transaction Proactive Checking. This check will not be turned on by default, but when a server has a LONGTX problem. This new check will create a User Event which sends email, but does not create a BLT ticket. For how to configure and other information, see Long Transaction Detection.
    • Thanks to Jean-Francois Le Carre Petit for suggesting these changes:
      • New dbamonrc SYSTEM section parameter: Make_Tickets:. If this is specified as Y, dbamon_make_tickets.pl will be invoked for critical event. The default is N.
      • Postnote event notification messages now display the instance name, date and error message identifier.
      • Previously, DBAmon always tried to use rsql to insert rows into mysql tables. I have now changed the code so that rsql is only invoked here in Colorado Springs. If you wish to use the mysql interface, change all occurances of our server name to your server in dbamon.awk.
    D Bill Border 17Nov99
    • DBAmon now checks the number of days since the last LEVEL=0 backup. There is a new .dbc parameter: L0_Age: where you can specify a number of days. The default is 30 days. If the threshold is exceeded, a critical event occurs.
    • There is now support for Oracle. There is no monitoring yet, but there are new .dbc file parameters (See guide below on .dbc file). In future releases there will be some simple checks for Oracle instances.
    • I noticed that during the first iteration of DBAmon that the routine which counted the number of the tables performed poortly. Since this data is rarely used by us, this routine is now "optional". There is a new dbamonrc file parameter called "Count_Tables:" which specifies whether table_counting should occur. The default is "Y". See the "Configuration" section of the DBAmon Home Page for details.
    C Bill Border 04Nov99
    • The System Summary now displays the Backup_Age: threshold for instances where it has been specified.
    B Bill Border 26Oct99
    • It is now possible to inhibit all DBAmon checking for all instances. There is a new (optional) file in the /opt/dbamon/adm/inhibit directory called ALL. The dates in this file are the same as for individual instances. This feature may be handy during time zone changes when many or all instances will be down.
    • There is a bug in Informix where the "locks" column of the sysesprof SMI table has invalid data. DBAmon was changed to ignore the condition where the total number of locks (from the syssesprof table) exceeds the LOCKS onconfig parm.
    • On an instance where the total amount of V shared memory is > 1gb, there will be no recommended SHM values recommended and no events created.
    A Bill Border 11Oct99
    • Introduction of Backup Age Inhibit . This capability will inhibit backup age checking for a user-specified amount of time. There is a new option "B" on the System Summary that will access the data entry panel where you specify the inhibit period. NOTE: This option uses mysql. If non-Colorado-Springs users want this capability, contact me.
    • When one instance has > 1 DBSpace critical or warning messages, only one colored message will now appear on the System Summary.
    3.21
    H Bill Border 20Sep99
    • The error message text for remsh errors now shows the cause of the error.
    • The number of maximum concurrent users is now tracked and reported at the end of the text instances report (in the /opt/dbamon/dat/reports directory).
    G Bill Border 29Jul99
    • The DBSPACE critial message now contains information about how full the dbspace and how much free space remains.
    F Bill Border 12Jul99
    • If a backup is currently executing on the server (ontape or onarchive) then a critical BACKUP AGE event will be reduced in severity to a warning.
    E Bill Border 01Jul99
    • If the box is running HP-UX 11.0, an indication was added to the system summary to indicate whether it is running in 32 or 64-bit mode.
    D Bill Border 25May99
    • Support for HP-UX Memory Windowing. This new feature of HP-UX allows memory to be partitioned. DBAmon was changed to prefix all commands with the setmemwindow command. See DBAmon Configuration for details. The new .dbc parameter is called Mem_Window:.
    C Bill Border 21May99
    • Support for Informix 7.30.FC (64 bit). The only necessary change was to the chunks_down routine to look at a different record offset due to long address field.
    • We found a problem with Informix 7.31 where certain sessions have garbage in their SMI table entries. Changed dbamon_locks.pl to ignore sessions where the number of locks exceeds the total configured for the entire instance.
    • The System Summary now displays the time that DBAmon was started.
    B Bill Border 23Apr99
    • Enhancements to Informix Version Management process. We have discovered that we need 3 colors to track defective versions of Informix.
      • Red: Version has critical bug(s). Upgrade is imperative
      • Yellow: Version had bug(s) with workaround
      • Green: No known significant bugs
      So, there are now 3 files to list versions. The old good and bad file and a new "soso" file. Red and Yellow designations will be included in the bad instance report. There is also a new pointer on the System Summary on the Informix Version column heading which takes you to our Informix Version Management page.
    • Removed Informix SN, DB Count, DBSpaces Count and Table Count from System Summary for performance reasons (our page was 120k). These values still appear on the /opt/dbamon/dat/reports/instances.txt report.
    A Bill Border 22Apr99 Added 3 new Actions to System Summary:
    • C: View the current dbamonrc (or *.dbc) settings for that instance. Note that the current settings, not the current contents of the .dbc file will be shown.
    • H: View Event History for that instance. Code has been added to insert a row into a mysql table any time there is an event (any severity). If I find that there is too much data, maybe at some point in the future I will only save W and C events.
    • N: View/Edit "Notes" for this instance. On clicking this URL, you will see a screen with any prior Note entries for this instance and a form to allow you to enter new Notes. This data comes from another mysql table.
    These new functions use the MYSQL relational database. You ask, why didn't you use Informix, because MYSQL is free! DBAmon now has code to manipulate MYSQL tables. There will be more to come as I convert all historical data storage to MYSQL. If you want to implement DBAmon with MYSQL, give me a call.
    3.20
    J Bill Border 17Mar99
    • MAJOR BUG FIX: The routine which measured the number of hours since the last successful ONArchive backup was not correct when the most recent backup occured more than 0 days ago.
    • HDR Change: There is a bug in Informix which forces us to run a dbspaceset=* backup when we have to do the HDR turn-on restore. We have found that it is difficult to remember to change our backup tool back to parallel backups after performing one of these special backups. A new check has been added to the CheckHDR() routine which will create a warning event if:
      1. The most recent level-0 backup is a dbspaceset=* backup -and-
      2. HDR is active
    I Bill Border 20Feb99
    • Added a column to the System Summary which displays the SAP kernel and backend version, if it is determined that the instance is SAP.
    H Bill Border 11Jan99
    • There was a problem where the 3rd column was wrapping on the System Summary. Also, I changed the appearance of the PGR and MBUN indicators.
    • The CLEANERS check previously recommended values above 127 which is the max CLEANERS ONCONFIG value. The max recommended value is now 127.
    • New code to check for an appropriate number of AIO VP's. Code was added to the downloaded dbamon_dbs.pl to capture the number of TOTALOPS (from onstat -g iov) for the first and last AIO VP. Then a ration of the last to the first is captured and expressed as a percentage. If this percentage is > 10, then we need more AIO VP's (we could adjust this threshold over time). A new INFO event will be then generated accordingly. The situation that this should prevent is when we configure ONCONFIG to have 1 AIO VP because we are turning on KAIO, but somehow the KAIOON env var is not set at Informix startup. The EVENT message will indicate the recommended number of AIOVP's and will also print a suggested onmode command to dynamically add AIO VP's to bring the instance to the recommended value.
    • Fix to System Summary so that the 4th column always has a color of black.
    G Bill Border 06Jan99
    • There is a new column on the System Summary "Events" which lists a short summary of what events currently exists for that instance.
    • The System Summary now scrolls horizontally without word-wrapping enabling you to set the width of your browser to something less than the whole screen.
    F Bill Border 21Dec98
    • Change the severity of extent warning from WARNING to INFO. Also added code for future check which will verify correctness of NUMAIOVPS.
    E Bill Border 11Dec98
    • Fixed bug where the was occaisionally duplicate DBSpace history data. This problem occured when there were dbamonrc system definition changes.
    D Bill Border 07Dec98
    • Fixed alignment problem with totals line at the bottom of the System Summary
    • Removed Non-Sys-DB column from System Summary
    C Bill Border 29Oct98
    • Added new WSTATS flag. For the time being, it will appear red on the System Summary page because we have recently fount that WSTATS=1 can cause significant performance degradation.
    B Bill Border 09Oct98
    • Our DBAmon->SMS interface to create Helpdesk tickets when an event occurs had previously truncated the test of the message on the problem summary for remsh errors. Message text was changed to not include a colon (:) which fixes the problem.
    • The archive age checking routine has been re-coded. Now, even for onarchive backed-up instances the number of hours since the last backup is measured (it wasn't before - it was only tested). A new column has been added to the System Summary which displays the number of hours since the last good backup which is color coded according to the Backup_Age: threshold for that instance.
    • When a remsh error has previously occured the report on the (E)vent page contained garbage. This has been fixed (I think).
    A Bill Border 01Oct98
    • Extent checking has been re-implemented. It had been disabled last fall because it didn't work correctly for instances with fragmented tables. It now works at the fragment level. A warning event happens if Max_Extents: (from dbamonrc) is reached and a critical event happens if the number of extents in a table reaches 200.
    • Performance enhancement to dbamon_table_count.sql:
    • The Test Mode of DBAmon now does not interfere with an instance of DBAmon running production. This was done by ensuring that work files when in test mode are different than those of non-test mode.
      • It now counts tables by running "select count(*) from systabnames".
      • A PDQPRIORITY of 25 is now used.
      These changes will improve the performance of the first iteration.
    3.19
    I Bill Border 15Sep98
    • Bug Fix: Stephan Reichart of BBN (thanks for the good feedback) found a problem where under certain conditions if a system is rebooted while in a download failed condition that DBAmon will not again reattempt to redownload the software making it necessary to restart DBAmon. The fix is to force a re-download any time that the "No software download" is issued.
    H Bill Border 14Sep98
    • Added code to allow the test version of DBAmon to run concurrently with the production version of DBAmon. That is, if you need to test a config change it is now not necessary to stop DBAmon to run dbamon test.
    G Bill Border 08Sep98
    • Another Y2K testing fix. A negative value for the hours since last backup is now a critical event. This has happened when a system that has been used for Y2K testing reverts back to the current datetime. There is now a new error message [DBA216C] which explains how to solve this problem.
    F Bill Border 03Sep98
    • Changed to a smaller font for the System Summary. The PAGER and HDR-P/S indicators now appear in the 3rd column.
    E Bill Border 02Sep98
    • The dbamon_install script had some problems with the names of directories. These problems have been fixed.
    • Migrated DBAmon from the mike server to a new server. This meant that I had to migrate it from UX 9.x to UX 10.x. There were no issues.
    • Y2K fix (well not really). An Informix instance was running on a system where its date was set to March something, 2000. The problem was that the logic which calculated the number of hours since the last successful backup came up with a negative number (that's actually correct). So I changed the logic so that the date to which the backup time is compared is now the time on the system where Informix is running; not the DBAmon server. The dbamon_arc_ontape program was changed and a new download dbamon_time.ksh was added.
    D Bill Border 02Sep98
    • Addition of Title3 config parameter. At AIT-ASO(CS) we will use this for the hours of support for that Informix instance.
    C Bill Border 02Sep98
    • Asthetic changes to the WWW System Summary (smaller font, colors).
    B Bill Border 02Sep98
    • The CLEANERS routine now will also ensure that the number of cleaners is >= the number of LRUS (something that we've recently learned about).
    A Bill Border 02Sep98
    • There is a new check: CheckpointDur. This check will use information gathered by check_locks and issue (for the time being) an INFO event if the current average checkpoint duration is > 120 seconds. At some future date, if this number does not create excessive events, this will become a critical event. There have been a few occasions recently where due to bugs in Informix we have seen checkpoints in the 2000-3000 second range.

    Version Programmer Date Description of Changes
    3.18
    Bill Border 17Jul98
    • The DBSpace full warning and critical messages now specify the name of offending DBSpace.
    • Code changes to support Informix 7.30.
    • Removed comments on dbamonrc parameters from the supplied dbamonrc and created new Configuration WWW page below.
    • DBAmon will now log to mike any time that DBAmon starts anywhere. This will enable me to better track who is using DBAmon.
    • Changes made at the request of Singapore users:
      • An instance that is inhibited now triggers an INFO event rather than a WARNING event.
      • Added concept of userexits. At key points in the code, dbamon.awk will invoke (if they exist and are executable) user written scripts. This will prevent users from having to modify dbamon.awk after every new release. See User Exits URL below.
      • Added new dbamonrc parameter OpC_Trailer. For any OpC message issued, the string supplied here will be appended to the text of the OpC message.
      • Previously users were changing the names of the colored "balls" for the WWW pages because the ones that I was using were not standard. I now supply all known images in /opt/dbamon/img. After every new installation you should now copy the contents of this directory to the location that you specify with the dbamonrc Images_Dir: parameter.
    3.17 Bill Border 29Jun98
    • Duplicate ONCONFIG checker. If a un-commented duplicate ONCONFIG parameter is found, an Info event will be generated with the parm that is duplicate.
    • Read/Write hit ratios will only be checked for instances where BUFREADS are > 10,000,000. This will eliminate events for instances that have recently been started or are not busy.
    • Cosmetic change: System Summary now displays DBAmon logo (new). It is supplied in /opt/dbamon/img.
    • Due to popular demand, moved the Related Documents section to the top of the system summary.
    • Fixed a bug discovered by a user in Singapore: If a monitored system does not have a link from /usr/local/bin/perl5 then the check_locks function did not work including the Average Checkpoint column of the System Summary. The fix invokes all downloaded Perl programs with the "perl" executable instead of the #! string at the front of the script.
    3.16 Bill Border 08Jun98
    • Inhibit viewer.
    • New experimental code to insert a row into an Informix/NT DB on my PC for every critical event. This is coded so that it only occurs for my instance of DBAmon running Colorado Springs.
    3.15 Bill Border 26May98
    • Added new feature which will verify that you are running the most current version of DBAmon. Every time that you start DBAmon, it will check to see what the latest version of DBAmon is (from mike.cs.itc). If you are running an old version, it will generate an EMail for the DBAmon administrator.
    • There is a new possible value on the Flags column of the system summary. If an instance is using HP-UX SHMEM "Magic" an M will be displayed. SHMEM Magic enables Informix to use > 2GB of SHMEM.
    • The backup method used for and Instance (A:ONArchive or T:ONTape) now displays as a Flag.
    3.14 Bill Border 22May98
    • Added the "M" value to the "Flags" column to system summary to indicate that SHARED MEMORY MAGIC is enabled.
    3.13 Bill Border 20May98
    • Added "Flags" column to system summary. At the present time it will indicate:
      • K: KAIO Enabled
      • S: Shared SHM Segments being used
    • Added code to display the current average checkpoint duration. At this time, no events are generated from values displayed here.
    • I changed the Informix Version Mgmt. section to NOT generate events. The reason being that it takes so long for some instances to arrange the upgrade that it seems counterproductive to have an instance in exception status for long periods of time.
    • Moved part of the legend that we previously at the top of the System summary to the bottom.
    • Reduced font size of instance detail so that browser window is not so wide. Since this made the page seem busier, I changed the bgcolor from gray to white.
    • Rearranged the columns of the System Summary so that less important columns appear on the right side.
    • The SHMVIRTSIZE section now check the current coded ONCONFIG value so that if the change has already been made from the event recommendation that an additional event will not be generated.
    3.12 Bill Border 02Feb98 We here in CS are going to need to track the total number of non-system Informix DB's. So, a new history data file: /opt/dbamon/dat/history/appldb/{DATE} has been created. The online_up subroutine now will check to see if this number has yet been captured today for every instance. If it has not, it will write a record in the format:
    1998.02.02 13:08:23 boi97:DW-Prod 12
    (date, time, instance, number of non-system DB's). I will later write SAS programs to create graphs from this data.
    3.11 Bill Border 29Jan98
    • Informix Version Management - This new feature compares the Informix version of every instance to a list of known good and bad Informix versions. If the version is found in /opt/dbamon/adm/informix_ver/good.txt the version is made green on the System Summary. If the version is found in the bad.txt file, it is flagged red and an INFO event is generated. If the version is not found in either, it is flagged yellow and an INFO event is generated.
    • Cleaners Check - The number of ONCONFIG CLEANERS is compared to the number of DB disks. If CLEANERS is < 75% of disks, an Info event is generated.
    • SHM Check Change - It no longer creates a WARNING event, only an INFO event.
    3.10 Bill Border 12Dec97 More major changes:
    • Performance (These changes have cut our iteration time (101 instances) in half:
      • DBSpace fullness measure; recoded to gather all info in 1 remote call (vs. 3 before in 1/3 the time.
      • Serial Number / OS version now is gathered with the table count. This eliminates 2 remote calls.
      • All software downloads are now done only once per instance, in the 1st iteration. This will save 6 remove calls per instance per iteration.
    • New Checks (2):
      • Virtual Shared Memory check. If total number of V segments >= 4 warning; if >= 10 critical.
      • HDR Check. If an instance has HDR turned on, the check will verify that HDR is On or Read-Only.
    • Asthestic:
      • System Summary Detail Section not as wide
      • System Summary Scoreboard not as tall
      • Any instance which runs HDR will have a P or S following the instance name to denote Primary or Secondary.
    3.00 Bill Border 24Nov97 Major changes:
    • dbamonrc File: The System: definitions for each instance now reside in a seperate file in /opt/dbamon/adm/instances. There is a new Include: line in dbamonrc which points to this new directory. In the directory /opt/dbamon/adm/instances, any file which has the suffix .dbc at DBAmon start time will be compiled.
    • System Summary WWW Page: The Scoreboard section now reports which checks have been performed during the most recent iteration including the execution time for each check.
    • New check_locks Check: A new check has been added to check the number of locked used vs. the number configured in the Informix ONCONFIG file. If the amount is >= 80% of the maximum, a critical event will be generated.
    • online_up Performance Enhancement: The dbamon_table_count.sql module which runs as part of the online_up subroutine now counts the number of tables in an instance by checking sysextents (it used to look at systabnames). This is much faster.
    • Log Files: The stdout output from DBAmon, which used to go to /tmp/dbamon.out now is written to /opt/dbamon/log/DOW where DOW is the day of the week (Sun, Mon, ...). Also, all messages now have a date and time stamp.
    2.30 Bill Border 28Oct97 Logical log checking works now for Informix V7. Also moved scoreboard to the top of the WWW System Summary page.
    2.28-
    2.29
    Bill Border 03Sep97 Added scoreboard to show how many of each type of event. Other asthestic changes to WWW page.
    2.27 Bill Border 05Jul97 New dbamonrc parameter: T_DBSpace_Free: (MB) This parm serves as an override to the T_Disk_Full dbspace critical thresholds. A dbspace will be critical if it is > T_Disk_Full % full -AND- the amount of freespace is less than T_DBSpace_Free.
    2.24-
    2.26
    Bill Border 03Jun97 dbamonrc cleanup: Informix_Version and Local_Or_Remote now have defaults 7/R. Added new parms Title1_URL, Title2_URL and Host_URL to specify URL to be associated with those fields of the System Summary.
    2.23 Bill Border 16Oct96 New dbamonrc parms "Title1/Title2" were added. The values are displayed on the System Summary page.
    2.22 Bill Border 01Oct96 The UX box type is now displayed on the System Summary page.
    2.21 Bill Border 23Sep96 Cosmetic - The HP-UX version is now displayed on the System Summary page. Also, the amount of output in the log should be reduced; I stopped displaying diagnostic info for archive age checking.
    2.20 Bill Border 26Apr96 Performance improvements (each iteration has been taking 1-1.5 hours!). DB object counting and extent checking will not be done every 10th iteration. Added auto-refresh code to the system summary HTML doc.
    2.19 Bill Border 25Mar96 Added logic to exclude "bogus" Informix messages that appear on the Informix message log. The example is a -27001 error that appears during an incorrect user connection attempt. This should not trigger a critical event. There is a new file in the /adm/ directory called dbamon.msg_critical_bogus which lists strings that appear in bogus critical error messages. These messages no longer appear as critical events.
    2.18 Bill Border 06Mar96 Creation of "inhibition" logic. It often becomes necessary to turn off monitoring of an Informix instance for scheduled down time. During those times, we need to turn off messages and paging. Logic was added to dbamon to check for the presence and read the contents of an "inhibit" file that can be set up for any Informix instance. This file contains dates and time for which DBAmon monitoring is NOT to take place. See the "Inhibition" section of the DBAmon Home Page for more info.
    2.17 Bill Border 01Mar96 A "-P" now appears next to the instance name for systems with paging enabled (usually production instances). Also, OV* (onstat -p) conditions are now critical events (were warning).
    2.16 Bill Border 14Dec95 Major enhancements to the System Summary WWW page, Missed DB backup messages are now critical (they were warning).
    2.14-
    2.15
    Bill Border 31Oct95 Various HTML asthetic changes. Event log is now created for each system, in addition to globally. HTML System Summary now has URL for the individual files. I also rearranged our local HTML files. Links found below have been fixed.
    2.13 Bill Border 30Aug95 DBAmon now has error messages. The HTML event log now has URL pointer to the correct message ID. In future releases I will further identify all messages. Look at my event log for sample output.
    2.12 Bill Border 18Aug95 Table extents are now monitored. There is a new SYSTEMS section parm called "Max_Extents" which specifies the maxiumun tolerable number of extents per table.
    2.11 Bill Border 16Aug95 DBAmon now creates (once a day) a dbspace size history file. It's in /opt/dbamon/dat/history/dbspace/*. This file contains one line for each dbspace of each system monitored. This file can then be used as input to SAS (my package of choice) to create data growth reports/graphs.
    2.10 Bill Border 18Jul95 Support for Informix 7.10. Minor bug fixes. Informix version now prints on log file.
    2.09 Bill Border 06Jul95 Reworked all files to facilitate install into /opt/dbamon making it a "real" software product.
    <2.09 Bill Border 01Jan94-06Jul95 Old README File.

    DBAmon.com
    This Document: http://dbamon.com/misc/change_history.shtml