2008

TKU July 2008

When the Oracle RDBMS attempts to link the Database Server instances with instances of TNS Listener, it performs a regular expression match of the Database SID and the TNS Listener SID. This SID may contain characters which have special meaning in regular expressions (e.g. '+').
In TKU July 2008 the pattern now escapes the special characters before it performs regular expression match.

2009

TKU February 2009

In TKU February 2009 we added a configuration section which allows sudo support to be disabled (default) or enabled and allows the path to the sudo process to be user-defined (defaults to PRIV_RUNCMD). This same configuration section also allows pmap support to be disabled (default) or enabled and allows the path to the pmap process to be user-defined.

TKU March 2009

In TKU March 2009 we added 2 new functionalities to the Oracle RDBMS pattern.

The pattern is now able to retrieve Listening Port and Global Name for a give Oracle Sid, by using 2 possible methods. The relevant section contains exhaustive details on both methods.

Furthermore, the pattern is able to retrieve a list of Options which can be installed in the Database, and report on whether these options are actually Installed or not. This is particularly relevant for Licensing purposes. Please refer to the relevant page for further details.

TKU April 2009

In TKU April 2009 we added extra Simple Identifiers, and additional "related processes" links from the Database Server Software Instance.

TKU May 2009

In TKU May 2009 we enhanced the code able to retrieve the list of installed options by adding the ability to get the list from a file on both the Windows and UNIX platforms should the SQL Query fail or be unable to be executed for whatever reason.

TKU June 2009

In TKU June 2009 we added a new method to retrieve ora_home, which uses the Path of the TNS Listener associated with a specific SID. This method also allows the Pattern to recognize if it is acting in an E-Business Suite environment, in which case the pattern knows where to look for the listener.ora file, which will be located in a different directory.

TKU July 2009

In TKU July 2009 we added the ebs_suite attribute to the Oracle Database Server SI. This attribute is only added when we are dealing with on Oracle E-Business Suite Database, and will allow the E-Business Suite pattern to trigger, and subsequently model the appropriate SIs and BAIs.

We also added a Path Versioning method to the TNS Listener, and the ability for the Listener to retrieve the ora_sid in an E-Business Suite environment.

2010

TKU March 2010

In TKU March 2010 we augmented the pattern's possibilities to extract ora_home. This was accomplished by interrogating the TNS Listener SoftwareInstance for that particular attribute.

We also added a Communication Relationship, modeled from the TNS Listener back to the Oracle Database Server

TKU April 2010

In TKU April 2010 four additional processes (Oracle shadow process, Oracle RAC Diagnosibility Daemon, Oracle Memory Manager and Oracle Database Automatic Workload Repository Statistics Gatherer Process) were added to the list of processes linked to the Software Instance via inference.associate() relationship.

TKU May 2010

In TKU May 2010 'ora_lmon' was added to the list of related processes and if found would lead to creation of 'clustered' attribute in SoftwareInstance; simplified greedy regex in listener section (bug #13113); fixed minor bugs: #13120, #13152 and #13204. Also the pattern's behavior was updated - now it populates "service_name" attribute, and if it is not found in tnsnames.ora file when global_name is known - the pattern will assign the value of global_name to service_name (bug #13021).

TKU June 2010

In TKU June 2010 the Database Server pattern no longer includes ora_home as part of the SI key as this could lead to instability in the model produced and duplicate SIs being created. ora_home is obtained in a number of ways and may not always be obtained on a first scan. Re-arranged also the order the pattern attempts to obtain ora_home.
Additionally, an inconsistency where the port attribute could be set as either integer or string was removed. The port attribute is always set to string.

TKU July 2010

In TKU July 2010 the Oracle Database Server and Oracle Database Server Express (UNIX) patterns were updated with improved code to parse oratab files to retrieve the installation path (oracle_home) of the database instance. The new regular expression deals with oratab lines which have more columns than normally seen in an oratab file.

TKU August 2010

In TKU August 2010 two changes were made:

• We amended the way eBusiness instances are handled by the TNS Listener pattern, instance names of APPS_X and X are now treated as separate instances
• Some changes were made to the internal logic of the pattern where the Oracle Database Software Instance obtains the ora_home variable from a related TNS Listener Software Instance

TKU September 2010

In TKU September 2010 the Oracle RDBMS and Oracle Database Express patterns were updated to further improve parsing of the oratab file.
Furthermore, the TNS Listener pattern was updated to improve parsing of tnsnames.ora file in order to prevent the pattern exiting with an ECA Engine error when characters such as '+' were encountered as part of the service name.

TKU December 2010

In TKU December 2010 the Oracle RDBMS pattern was updated that parsing of the XML file containing edition information is now optionally performed with elevated privileges.

2011

TKU April 2011

In TKU April 2011 the Oracle RDBMS Installed Options pattern module was modified. It now detects the Data Mining installed options via a database query. The key of any detailed node created was changed from row, DB SI key and host key to row and DB SI key. The detailed nodes also now age out correctly.

TKU May 2011

In TKU May 2011 the Oracle RDBMS Installed Options pattern module was modified. For ADDM 8.2 onwards, privileged cat commands are now always executed regardless of the state of the UNIX privilege execution flag (now removed as redundant) in the configuration section and instead of 'cat' command.

TKU September 2011

In TKU September 2011:

• Extra functionality was added to obtain the address_names from the tnslistener.ora file
• The TNS Listener pattern has been updated with an improved UNIX path regex to increase versioning coverage.

TKU October 2011

In TKU October 2011:

• A minor change was made to the way the relevant file was parsed to obtain the address_names attribute.
• Added case insensitivity to regex used for extracting information like port and matching hosts from the listener file.

TKU November 2011

In TKU November 2011, a minor update to the Oracle Database Server pattern was made to determine if the version obtained using active command approach is likely to be correct and also to map the version obtained on Oracle 7 installations to that version of the product

2012

TKU February 2012

In TKU February 2012 the regular expression used to obtain the service name was slightly improved

TKU March 2012

In TKU March 2012 the DatabaseServer pattern now attempts to extract the latest edition when multiple context.xml files are to be found on the UNIX platform.

TKU April 2012

In TKU April 2012 the DatabaseServer pattern was updated in the following ways:

• Improved methods for obtaining ora_home; improved active and registry versioning method;
• Enhanced method for obtaining db_unique_name, service_name from spfile.ora or init.ora.
• Populated listen_tcp_sockets, listen_ips and listen_ports attributes from related "TNS Listener" SIs.
• Additional paths to context.xml file added.

The TNSListener pattern was updated in the following ways:

• Enhanced method for obtaining listener_name.
• Added active command for obtaining version and listening addresses.
• Updated method for reading listening addresses and served Oracle instances from listener.ora file
• Added config section for custom paths to listener.ora files

TKU May 2012

In TKU May 2012 the following updates were made:

• DatabaseServer pattern: enhanced regex for obtaining ora_home from Windows service.
• TNSListener pattern: added enhancement for parsing of listener.ora file.