DBSPI

HP OPENVIEW
Smart Plug-ins for Databases

RELEASE A.06.02
This document contains important information about the Smart Plug-ins for Databases and supplements the
Configuration Guide and reference manuals.
Copyright Hewlett-Packard Development Company, L.P., 2003
Table of Contents:
Chapter 1: Announcements
Chapter 2: Enhancements to this Version (summary)
Chapter 3: Enhancements/Fixes (details)
Chapter 4: Known Problems/Limitations and Workarounds
Chapter 5: Compatibility and Installation Requirements
Chapter 6: Software Availability in Native Languages
Chapter 1: ANNOUNCEMENTS
Version A.06.02 of the Smart Plug-ins for Databases includes enhancements and defect repairs. Refer to
chapters 2 and 3 of these release notes for more information. For installing and using the product, please
refer to the HP OpenView Smart Plug-in for Databases Configuration Guide, A.06.02, and the reference
manual for the specific database type.
DOCUMENTATION
All the following documentation is contained on the CD-ROM:
HP OpenView Smart Plug-in for Databases: Configuration Guide
HP OpenView Smart Plug-in for Databases: Oracle Reference
file name: oracle_ref.pdf
HP OpenView Smart Plug-in for Databases: Informix Reference
file name: informix_ref.pdf
HP OpenView Smart Plug-in for Databases Sybase Reference
file name: sybase_ref.pdf
HP OpenView Smart Plug-in for Databases: Microsoft SQL Server Reference
file name: mssql_ref.pdf

Chapter 2: Enhancements to this Version (summary)
Version A.06.02
The latest version does not include any major enhancements. Please see Chapter 3 for descriptions of the
minor enhancements added to A.06.02.
Version A.06.00 enhancements:
Improved Oracle Cluster Awareness/Support
For Oracle 9, the Database SPI now detects clustered databases and automatically implements metric
collections that take this configuration into account. To monitor a 9i clustered environment, the
Database SPI implements both shared (global) and individual metric collections. For Oracle 8.x and
earlier, users can manually implement the same metric collections. Please see the Configuration Guide,
Chapter 7: Special Configurations, for details.
Tru64 support for Oracle
The Database SPI now supports environments that use Oracle running on a Tru64 platform.
Support for Oracle on some raw devices
Metric monitoring of Oracle running on some raw devices is now supported. Please see the
Configuration Guide, Appendix C for details.
Support for Microsoft SQL Server User Defined Metrics
The Database SPI now supports user-defined metrics for Microsoft SQL Server. Please see the
Configuration Guide, Chapter 6 for detailed instructions.
Application that creates an MS SQL Server user not needing system admin capability
The Database SPI connection to the MS SQL Server can now be configured with limited capability,
ensuring database security.
Improved MS SQL Server logfile monitoring
Ten new conditions have been added to catch common problems.
Additional MS SQL Server metrics (3035, 3233 and 3234)
New metrics for MS SQL Server provide increased DB-SPI monitoring capabilities as follows :
returning information on the longest running transactions for MS SQL; warnings for when the MS
SQL Server database or database log has not been backed up recently.
Chapter 3: Enhancement and Fixes In this Version (detail)
The first section of this chapter covers details of product enhancements. The second section covers product
defects that have been fixed.
A.06.02 ENHANCEMENTS
CR NUMBER DESCRIPTIONSOF A.06.02 ENHANCEMENTS
JAGAE65033 Data in report for Oracle metric 6 now sorted by "Percent Free" ascending order.
General Topic Area: Oracle Metric Reports
Background: In previous versions, the report for Oracle metric 6 was sorted
alphabetically. This made it difficult to find the tablespaces that were most severely
short in space.
Benefits of the Enhancement: Ease of Use
Description of the Enhancement: In B.06, the report is sorted ascending by "Percent
Free" so that the tablespace that has the smallest percentage free is listed at the top.
Steps Necessary to Use/Implement the Enhancement: None
ROSMM18194 Enhanced Reporter integration to build tables on install.
General Topic Area: Reporter Integration
Background: In the past, when the DB-SPI Reporter integration installation packages
were installed on the Reporter system or on the OVO for Windows system (with OVO
for Windows an embedded reporting component is installed automatically through the
common installer), the tables necessary for the DB-SPI reports were not immediately
created. As a result, if reports were generated before any data was gathered for the DB-
SPI reports (which would occur 2 AM the following morning), errors would be reported
both by Reporter and by OVO Windows (embedded reporting component).
Description of the Enhancement: The report integration packages that are
automatically installed with OVO Windows 7.2 or installed on a separate Reporter
system now automatically create the necessary tables. As a result, no errors are reported.
As always, the reports remain empty until the following day.
Steps Necessary to Use/Implement the Enhancement: For the OVO for Windows
integrated reports, no action is needed. For a separate Reporter installation, uninstall the
old report integration packages and install the new packages as described in the Smart
Plug-in for Databases Configuration Guide, Chapter 5.
ROSMM21243 Exclude cache segments for calculation in Oracle metrics 3/16
General Topic Area: Space Metrics
Background: Oracle metrics 3/203 and 16/216 have always included cache segments in
their calculations, resulting in undesired alarms on the segments.
Benefits of the Enhancement: Increased usability
Description of the Enhancement: Metrics 3/203 and 16/216 no longer alarm on cache
segments.
CR NUMBER DESCRIPTIONSOF A.06.02 ENHANCEMENTS
ROSMM27958 Improvement for MSSQL metric 3025 on system with multiple CPUs.
General Topic Area: MS SQL Metrics
Background: In prior versions, metric 3025 for MS SQL Server did not report the
number of CPUs on the system, so it was difficult to interpret the metric.
Benefits of the Enhancement: Increased Functionality
Description of the Enhancement: The metric now returns the number of CPUs being
used by MS SQL Server and the total percentage taken for all CPUs (the value is still
between 0% and 100%); for example: "DBSPI-3025.1: % CPU time used by SQL
Server (90% of 3 CPU(s)) too high (>=80%) for ros51340tst\OVOPS."
Steps Necessary to Use/Implement the Enhancement: Deploy the new template
DBSPI-3025 to the necessary nodes to implement the new message text.
ROSMM28222 Added automatic action report for Oracle metrics 64 and 65 like 62
General Topic Area: Oracle Metric Reports
Background: The automatic action annotation report for Oracle metric 62, which is
"Percentage of space used on Oracle background dump device" showed the file system
name, total K bytes, K bytes used, K bytes available, percentage used and the directory
mount point. This allowed the admin to know which mount point to add space to when
the alarm occurred. Metrics 64 and 65 are "Percentage of space used on user dump
device" and "Percentage of space used on core dump device". These metrics could
benefit from the same report.
Benefits of the Enhancement: Increased Functionality
Description of the Enhancement: Automatic action annotation reports have been
added to Oracle metrics 64 and 65, "Percentage of space used on user dump device" and
"Percentage of space used on core dump device".
Steps Necessary to Use/Implement the Enhancement: You must deploy the new
version 6.0 Measurement Threshold policies DBSPI-0064 and DBSPI-0065.
ROSMM28799 Added new MS SQL Server availability metric
General Topic Area: MS SQL Server Availability Metrics
Background: Prior to B.06, when an MS SQL Server instance was down, DB-SPI
would report: DBSPI10-21: Unable to connect to database 'rosspi8\OVOPS.master' as
'Integrated Security' [Unable to connect: SQL Server is unavailable or does not exist].
Description of the Enhancement: Starting with B.06, a new metric has been added,
3030, which will report that the instance was down. This is a standard metric and has a
monitor policy of DBSPI-3030.
Steps Necessary to Use/Implement the Enhancement: Deploy the new templates
DBSPI-MSS-05min and DBSPI-3030. DBSPI-MSS-05min will now run metric 30.

A.06.00 ENHANCEMENTS
CR NUMBER DESCRIPTIONS.OF A.06.00 ENHANCEMENTS
ROSMM25011 Support raw disks for Oracle metric 3/203, 6/206, 16/216
General Topic Area: Oracle space metrics
Background: Previous versions of DB-SPI did not support any raw disk formats. If an
Oracle data file resided on a raw disk, an error would occur when DB-SPI attempted to
determine the amount of disk space left on the drive.
Benefits of the Enhancement: Increased functionality
Description of the Enhancement: With A.06.00, DB-SPI supports a limited number of
raw disks. This means that the space metrics 3/203, 6/206 and 16/216 return correct
results. See the Configuration Guide for details on specific raw disks are supported.
ROSMM22653 Improved support of Oracle Real Application Clusters (RAC)
General Topic Area: Oracle RAC
Background: Previous versions of DB-SPI had no special support for RAC.
Benefits of the Enhancement: Easier to use
Description of the Enhancement: DB-SPI now automatically chooses one system in a
RAC cluster to be the global system where all metrics are run. All other systems are
considered secondary systems and other, non-global metrics are run on these system.
This configuration eliminates duplicate messages from the space metrics. In addition,
this configuration has meant that the old "OPS" templates could be eliminated because
they are no longer needed.
ROSMM26351 Enhance Oracle 216 to generate a more revealing message.
General Topic Area: Oracle Space Metrics
Background: Previous versions of DB-SPI had a simple message for metric 216
Benefits of the Enhancement: Functionality
Description of the Enhancement: The metric has been enhanced to generate the
following message:
TEXT "DBSPI-0216.1: Number of extents (<$VALUE>) left for <$OPTION
(segment_name)> in tablespace <$OPTION(tablespace_name)> too low
(\\<=<$THRESHOLD> and \\<=<$OPTION(cli_threshold)>) for database
<$OPTION(dbname)>. <$OPTION(reason)>"
Reason will be set to:
Case 1: Hitting max extents
reason="Max extents reached. Max extents = ####.
Current extents = #####."
Case 2: Auto-extend limit.
reason="Reached auto-extend limit. Next extent size is <next size> MB."
Case 3: Found out-of-space condition w/ auto-extend.
reason="Additional space needed. Next extent is <next size> MB."
Case 4: Found can't extend condition w/o auto-extend.
reason="Additional space needed and auto-extend is not enabled. Next extent is <next
size> MB." <next size> is the size of the extent that we would need to get one more
extent. This size varies for each extent, but we must already know this size to determine
the failure.
JAGAE39294 Add filters to metric Oracle 42
General topic area: Filters
Background: Metric 42 did not have a filter.
Description of the Enhancement: Filters have been added to metric 42
Steps Necessary to Use/Implement the Enhancement: Add filter; for example,
SYNTAX_VERSION 4
ORACLE
HOME "/rdbms/oracle/product/9.2.0.1.0"
DATABASE ora920 CONNECT "hp_dbspi/hp_dbspi"
FILTER 42 "table_name <> 'x'"
ROSMM22214 Add back start/stop tool for MS SQL for OVO UNIX with parameter.
General Topic Area: Applications
Background: In a previous version, we removed the MS SQL start/stop applications
because they would only start/stop the default, which was not correct for MS SQL
Server 2000.
Description of the Enhancement: A new application has been added called
"Start/Stop/List Instances" which lists the instances and allows the use to start and stop
individual instances.
Steps Necessary to Use/Implement the Enhancement: Execute the application
"Start/Stop/List Instances"
ROSMM21830 Add an auto action to error 10-82 to build data sources.
General Topic Area: Error reporting
Background: If the customer did not build the data sources using "Enable Graphs" and
"Enable Reports," DB-SPI would generate the error "DBSPI10-82: Data logging failed
for <Object Name>. Make sure Performance Agent is running."
Benefits of the Enhancement: Ease of use.
Description of the Enhancement: An automatic action has been added to the messages
template for error 10-82 to automatically enable graphs and reports.
ROSMM23612 Improve Sybase logfile conditions.
General Topic Area: Sybase logfile template
Background: The Sybase logfile template had limited conditions.
Description of the Enhancement: An additional 30 conditions were added to trap
specific errors.
Steps Necessary to Use/Implement the Enhancement: Deploy the new template.
ROSMM20910 Improve error reporting for override.cfg
General Topic Area: Local Thresholds
Background: In the past, local thresholds were added which allowed a customer to
override an OVO threshold with a more stringent local threshold, as described in
Chapter 7 of the Configuration Guide. However, there was no good way to check the
syntax and verify the threshold.
Benefits of the Enhancement: Ease of use.
Description of the Enhancement: Starting with A.06.00, if you run a metric with a
local threshold, any syntax errors in the override.cfg and the local threshold value
are printed.
Steps Necessary to Use/Implement the Enhancement: For example, if you had an
override.cfg file containing:
MONITOR "DBSPI-0022"
MINTHRESHOLD
MSGCONDITIONS
CONDITION
OBJECT "oradb"
THRESHOLD 80
Then when you test the metric with the -p option, as: dbspicao -m 22 p
If there are syntax errors, they are printed. If the syntax is correct, the local threshold is
printed:
oradb 0022 91.80 (Local Threshold = 80.00)
ROSMM25612 Allow threshold of 0 for Oracle space metric 16/216 - Segment cannot extend.
Background: When Oracle metric 16/216 was rewritten in the A.05 version, it was
modified from "segment cannot extend" to "segment is within N extents of not being
able to extend" where N is the command line threshold. For example,
"dbspicao -m 16:1" would alarm with each segment that was within a single
extent of running out of space. However, a threshold of 0 was not allowed. Zero was
converted to 1.
Description of the Enhancement: With A.06.00, a command line threshold of zero is
allowed, which means that if zero is sent, an alarm occurs only if the segment is
completely full.
Steps Necessary to Use/Implement the Enhancement: Insert zero in the command
line of the template, as in "dbspicao -m 16:0"
ROSMM25172 New metric 72 to alarm when log_archive_start value is set to TRUE and the
v$database log_mode field is set to 'NOARCHIVELOG'
General Topic Area: Oracle Archive Metrics
Background: N/A
Description of the Enhancement: With A.06.00, a new metric has been added, metric
72, which alarms if log_archive_start is set to TRUE and the v$datbase
log_mode field is set to NOARCHIVELOG. This is in case the user temporarily sets
archiving off for the database and forgets to switch it back on.
Steps Necessary to Use/Implement the Enhancement: This new metric has been
added to the 1-day template. If your templates are already deployed, add this metric to
one of your existing metrics and make sure to deploy the DBSPI-0072 to your systems.
JAGAD26745 Add tablespace-name to DBSPI Oracle metric 216 message
Background: In previous version, the tablespace_name in which the segment at fault
was part of was not included as part of the metric 216 message.
Description of the Enhancement: Starting with A.06.00, the tablespace name is
included in the text message:
DBSPI-0216.1: Number of extents (<$VALUE>) left for <$OPTION(segment_name)>
in tablespace <$OPTION(tablespace_name)> too low (\\<=<$THRESHOLD> and
\\<=<$OPTION(cli_threshold)>) for database <$OPTION(dbname)>.
<$OPTION(reason)>. "
Steps Necessary to Use/Implement the Enhancement: Deploy the new policy which
is included with A.06.00. If you deployed the original DBSPI-0016 policy, then you
must modify your existing policy to includd the new text as shown above. To upload the
factory fresh policies (which will overwrite existing policies), execute:
/opt/OV/bin/OpC/opccfgupld -silent -replace -subentity
\/var/opt/OV/share/tmp/OpC_appl/DBSPI/ora_set
ROSMM25330 Do not allow collectors to run overlapping metrics.
General Topic Area: Incorrect Template Deployment
Background: In the past, it was easy for a user to deploy too many templates and run
metrics that would overlap. This causes problems in that metrics use information stored
on disk to calculate the metric values and if these files are accessed by more than one
collector, incorrect results can occur. In addition, it is a waste of system resources to
run duplcate metrics. Finally, if scheduled templates are used to run metrics, it is
possible to queue up many collectors running at the same time and the system could get
saturated.
Benefits of the Enhancement: Performance and Fault Detection
Description of the Enhancement: Starting with A.06.00, DB-SPI prevents collectors
from running the exact same metrics at the same time. When ever this situation occurs,
the following message appears in the browser:
DBSPI collector <Attempted Collector Command Line> is still running. DB-SPI
collector <running collector command line> causes an overlap in metric <Metric
Number> - terminating this collector.
Steps Necessary to Use/Implement the Enhancement: None; however, if for some
reason you want to turn this feature off, add the following line to the defaults file:
OVERLAPPING_METRICS ON
ROSMM20612 Enhance MS SQL Server metric 3014 to have a duration.
General Topic Area: MS SQL Server Metrics
Background: In prior versions, it was common to have one more more blocked
processes at any given instance in time. This is not necessarily a problem. Metric 3014
would report a blocked process, which may be blocked at that instance in time, but this
is not a problem unless it is blocked for an extended period of time.
Description of the Enhancement: With A.06.00, the metric has a "DURATION"
which means it will only alarm if the number of blocked processes is greater than zero
for two collection intervals (default, 5 minutes) in a row. The big limitation of this
metric is that it may not necessarily because the same process is blocked.
Steps Necessary to Use/Implement the Enhancement: Modify the DURATION or
upload the new templates (which will overwrite your existing templates unless you
made a copy) via the command:
/opt/OV/bin/OpC/opccfgupld -silent -replace -subentity \
/var/opt/OV/share/tmp/OpC_appl/DBSPI/mss_set
and deploy the new templates.
ROSMM20621 Improve the MS SQL Server logfile templates
General Topic Area: MS SQL Server Logfile
Background: In A.05, DB-SPI had only 8 or 9 conditions in the MS SQL Server logfile
template.
Description of the Enhancement: Ten new conditions have been added to catch
common problems:"Error 601", "Error 602", "Error 604", "Error 605", "Error
9002","Error 9004""Error 14151", "Error 15457", "Error 17824", "Error 17832"
Steps Necessary to Use/Implement the Enhancement: Use the new template that
comes with A.06.00. To upload the new template, execute the following command (all
changes made to original templates will be lost):
and deploy the new templates to your managed nodes.
ROSMM21698 New Sybase metric 2002 to report database down
General Topic Area: Sybase Availability
Background: In prior releases, if a Sybase database was down, DB-SPI would report:
DBSPI0-0: Open Client Message: Message number: LAYER = (5)
ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
DBSPI0-0: Message String: ct_connect(): network packet
layer:
internal net library error: Net-Lib protocol driver call
to connect two endpoints failed
DBSPI0-0: Operating System Error: Socket connect failed -
error 22
DBSPI40-14: The call to function ct_connect() in
sybsrv_connect failed.
DBSPI40-14: The call to function sybsrv_connect()
in ovam_sql_connect_db2 failed.DBSPI40-13: Connection
attempt to server ellie with user sa failed
Description of the Enhancement: With A.06.00, a new Sybase metric has been added,
2002, which will "cleanly" report when a database is down. The following error is now
generated instead of the DBSPI0-0 errors:
DBSPI-2002.1: Cannot connect to Sybase database server
<$OPTION(dbserv)>
Steps Necessary to Use/Implement the Enhancement: You will need to deploy the
DBSPI-2002 template and modify your 5 minute Program Monitor template to run
metric 2 as well as the other metrics. For example, the default template now runs the
collector like so:
dbspicas -w 120 -c DBSPI-Syb-05min -m 1,2,3,7-
10,13,18,21,27,29,32-33,35-39,41-42,44-48,50-51,53-
55,57,61-76,80,81,203,213,235,236,237,250-251,273
JAGAE45355 Add support for Tru64 systems with Oracle
General Topic Area: Platform Support
Background: Previous versions of DB-SPI did not have a native solution for Oracle on
Tru64.
Description of the Enhancement: Starting with A.06.00, DB-SPI now supports Tru64
as a native platform for monitoring Oracle.
Steps Necessary to Use/Implement the Enhancement: Simply deploy the program
files and policies to the Tru64 system as other platform.
ROSMM15333 Support UDMs for MS SQL Server
General Topic Area: User Defined Metrics
Background: Previous version of DB-SPI did not support UDMs with MS SQL Server
Description of the Enhancement: DB-SPI now supports UDMs with MS SQL Server
Steps Necessary to Use/Implement the Enhancement: See the Configuration Guide
for details
ROSMM20625 Include details of MS SQL Server logfile entry in message
General Topic Area: MS SQL Server Logfile Template
Background: In previous versions of DB-SPI, the logfile template for the MS SQL
Server logfile would display only the line with the error number on it. To find the text
of the message, the customer had to look at the annotations, which showed the last 200
lines of the logfile.
Description of the Enhancement: Starting with A.06.00, the line with the error and
the following line with the details are combined and sent to the browser as one message.
Steps Necessary to Use/Implement the Enhancement: You must upload and deploy
the new policy to all nodes. To upload the new policy, execute the following command
(this will replace any customizations that you may have done on existing MS SQL
Server templates):
ROSMM20618 New metric for MS SQL Server tracks the longest running transactions for MS SQL.
Background: N/A
Description of the Enhancement: In A.06.00, a new MS SQL Server metric has been
added, 3035, which will report on the longest running transaction. The message
generated will be:
"DBSPI-3035.1: Transaction <$OPTION(trans)> in program
<$OPTION(prog)>
(spid=<$OPTION(spid)>) for user <$OPTION(user)> too long
(>=<$THRESHOLD> seconds) for <$OPTION(dbserv)>."
Steps Necessary To Use/Implement The Enhancement: Deploy the template DBSPI-
3035 and change one of your program monitor templates to run this metric. By default,
it is part of the 5 minute metric set.
ROSMM20610 Add a new MS SQL Server metric to warn that a database has not been backed up
recently.
Background: N/A
Description Of The Enhancement: In A.06.00. a new MS SQL Server metric has been
added, 3233, which will alarm if a database has never been backed up or if it has not
been backed up for longer than the OVO threshold. The messages generated are:
DBSPI-3233.1: Database <$OPTION(database_name)> has never
been backed up for <$OPTION(dbserv)>."
DBSPI-3233.2: Database <$OPTION(database_name)> has not
been backed up for <$VALUE> hours
(>=<$THRESHOLD> hours) for <$OPTION(dbserv)>."
Steps Necessary To Use/Implement The Enhancement: Deploy the template DBSPI-
3233 and change one of your program monitor templates to run this metric. By default,
it is part of the 1 day metric set.
ROSMM20611 Removed all occurrences of "DBCC UPDATEUSAGE" in all MS SQL Server metrics.
General Topic Area: MS SQL Server Performance
Background: In prior versions of DB-SPI, most of the "DBCC UPDATEUSAGE" calls
were removed because on very large systems, they would run for a very long time. This
command was used to update the statistics in certain system tables. However, there
were still one or two of these calls lingering.
Benefits of the Enhancement: Improved Performance
Description Of The Enhancement: All occurrences of "DBCC UPDATEUSAGE" have
been eliminated from DB-SPI.
Steps Necessary To Use/Implement The Enhancement: None
ROSMM13530 Added an application to create an MS SQL Server user for DB-SPI.
General Topic Area: Security of MS SQL Server
Background: In all previous versions of DB-SPI, the DB-SPI-configured user
connection to the MS SQL Server database was required to possess System Admin
capabilities. This configuration was deemed a major security risk as the user ID and
password was available to any OVO administrator.
Benefits of the Enhancement: Improved security
Description Of The Enhancement: Starting with A.06.00, a new application has been
added to the Application bank at: DB-SPI -> MS SQL -> Create MSSQL User
When run against a managed node, it prompts the user for a user ID and password and
can create a user with limited capabilitiesjust enough for DB-SPI to run.
Steps Necessary To Use/Implement The Enhancement: Run the application "DB-SPI
-> MS SQL -> Create MSSQL User" to create the user and modify the DB-SPI
configuration to use this new user ID and password instead of the existing user ID and
password with system admin capability.
ROSMM26269 Better cluster support and documentation for OVO UNIX
General Topic Area: Cluster support
Background: In prior versions of DB-SPI, documentation existed in the manual that
explained how to implement a failover using DB-SPI tools with Veritas and MC/Service
Guard. However, this documentation did not take advantage of the updated OVO 7.1
cluster-aware agent.
Description Of The Enhancement: In A.06.00, cluster aware XML files are included
with DB-SPI for all database types. See the manual for details on how they are used and
how to set up a cluster. Requires an OVO 7.1 or higher agent.
Steps Necessary To Use/Implement The Enhancement: See the Configuration Guide
for details.

A.06.02 FIXES
CR NUMBER DESCRIPTIONS OF A.06.02 FIXES
JAGAE46606 Sometimes gets for DBSPI9-5 and DBSPI9-6 generated errors.
Problem: Errors like the following would occur infrequently:
10/08/02 10:02:00 ERROR dbspicao(3988) CFT [metric0018:osfileutil.c:162]: DBSPI10-81:
Unable to gain lock file '/var/opt/OV/dbspi/history/oracle/CFT_m0018.lck'. File already in use
by another process. (File exists) 10/08/02 10:02:00 ERROR dbspicao(3988) CFT
[metric0018:metric0018.pc:323]: DBSPI9-5: Persistent store function 'load' on file
'/var/opt/OV/dbspi/history/oracle/CFT_m0018' failed.
10/08/02 10:16:02 ERROR dbspicao(6968) CFT [metric0018:osfileutil.c:162]: DBSPI10-81:
Unable to gain lock file'/var/opt/OV/dbspi/history/oracle/CFT_m0018.lck'. File already in use by
another process. (File exists)
10/08/02 10:16:02 ERROR dbspicao(6968) CFT [metric0018:metric0018.pc:323]: DBSPI9-5:
Persistent store function 'load' on file '/var/opt/OV/dbspi/history/oracle/CFT_m0018' failed.
Cause: The file locking mechanism contained a subtle design flaw.
Fix: Improved file locking mechanism.
JAGAE58362 Problems occurred with DBSPI UDM metrics and MeasureWare Integration.
Problem: Integration between UDM metrics and MeasureWare did not work on Windows
NT/2000. The DSI logfiles would be created in the wrong place.
Cause: The code was missing a "\".
Fix: The code now builds the DSI logfiles in the right place.
JAGAE68420 "Top Messages" reports gave errors when a message text was > 254 characters in length
Problem: The overall "Top Messages" reports give errors when a message text is > 254
characters in length. Specifically, the following report policy files have the problem:
{a,g,s}_dbspiitoevents[_hist].rpt. The error generated by OV Reporter is: "Error in File
D:\Program Files\HP OpenView\Data\reports\dbspi\a_dbspiitoevents.rpt: Error in formula
<TextTable>. 'Left({@MSG_TEXT}+{@TextOnly}+{@Instance Name}, 48) '
A string can be at most 254 characters long."
Cause: The data type in the report was incorrect.
Fix: The report can now handle > 254 byte messages.
JAGAE70018 DB-SPI monitor fails for MS SQL Server if Sybase has been installed
Problem: On systems that have both MS SQL Server and Sybase, then
the following error could occur:
isql -E -S ""
Syntax Error in '-E'
usage: isql ...
Cause: The problem occurred because isql is not fully qualified and if Sybase is installed, it will
attempt to run the Sybase version of isql instead of the MS SQL Server version.
Fix: The path to the MS SQL Server bin directory is now added to the FRONT of the PATH so
that the correct isql is found by the OS.
JAGAE74851 DB-SPI error DBSPI40-1/Oracle Error 1002 on Oracle metric 69
Problem: The following error occurs when running metric 69: DBSPI40-1: Unable to fetch data
from table 'V$ROLLSTAT, V$ROLLNAME' [ORA-01002: fetch out of sequence].
Cause: The problem was caused by a missing GRANT in the tool that creates the DB-SPI
Oracle user in the Instance Manager.
Fix: A new GRANT was added to the tool: grant select on V_$ROLLNAME to &&DBSPI;
JAGAE74851 DB-SPI error DBSPI40-1/Oracle Error 1002 on Oracle metric 69.
Problem: The following error occurred when running metric 69: DBSPI40-1: Unable to fetch
data from table 'V$ROLLSTAT, V$ROLLNAME'
[ORA-01002: fetch out of sequence].
Cause: The problem was caused by a missing GRANT in the tool that creates the DB-SPI
Oracle user in the Instance Manager.
Fix: A new GRANT was added to the tool: grant select on V_$ROLLNAME to &&DBSPI;
NSMBB50912 DBSPI could write huge values to <SID>.dat file
Problem: DB-SPI would fail to write graphing data to MeasureWare when a value of >
21,474,836.47 billion was logged.
Cause: The real cause of the problem is a defect in Oracle where Oracle metric 37 will
sometimes return huge values. These values were placed in the DB-SPI <SID>.dat file and
then an attempt was made to pump this data into MeasureWare/DSI. The DSI utility does not
allow values > 21,474,836.47, so it fails.
Fix: Whenever a value greater than 21,474,836.47 is encountered, the value is set to
21,474,836.47 so that DSI can process it.
NSMBB52512 dbspicao.bat added multiple -i options to call.
Problem: The dpspicao.bat added an additional "-i " to the calling parameters. Therefore if the
instance was already defined in the OVO scheduled action, the resulting call to the collector
included it twice.
This problem was visable to the user if there were errors returned from the collector (the
customer saw the problem when the DBSPI 20-8 error was returned).
For the OVO scheduled call defined as: dbspicao -m 21,22,35,77 -i GAMI
The returned error message was: "DBSPI20-8: DBSPI collector 'dbspico7.exe -m 21,22,35,77 -i
GAMI -i GAMI ' is still running. DB-SPI collector '21,22,35,77' causes an overlap in metric
'dbspico7.exe -m 21,22,35,77 -i GAMI -i GAMI ' - terminating this collector."
Because the batch file dpspicao.bat always added the -i option to the final call, a -i that was
defined in the original call to the batch file resulted in the "-i" appearing twice in the call to the
pspicoX.exe.
Cause: Flaw in the dbapicoa.bat
Fix: The flaw has been corrected.
ROSMM27319 Filter for metric 16 did not work
Problem: The filter was ignored in some situations.
Cause: Incorrect code.
Fix: The filter is now applied correctly.
ROSMM27863 Starting with MeasureWare Agent C.03.65 on NT, ddfcomp would fail
Problem: Starting with MeasureWare Agent C.03.65 on all Windows versions (NT, 2000, etc.),
the default installation directory is:"C:\Program Files\HP OpenView\"
This caused ddfcomp to fail as it tried to run sdlcomp without putting quotes around the program
name. The error is reported as: Error: Exit code of 'ddfcomp
"c:\usr\bin\opc\cmds\dbspimsom.sp"
"c:\usr\ov\dbspi\dsi\mssql\OVOPS\osm\OVOPS.log" OVOPS -d
MSSQLOSM_AMALTHEA_OVOPS ' execution is 1.
If you run it from the command line, you get:
'D:\Program' is not recognized as an internal or external command, operable program or batch
file.
Cause: The command line was not quoted.
Fix: The command line is now quoted.
ROSMM27899 Metric 16 returned wrong value for local tablespace with USER allocation
Problem: The problem occurred on systems where a tablespace is created as a dictionary
managed tablespace and then converted to a local managed one. In this case the allocation type
is USER (not UNIFORM or AUTOALLOCATE). Metric 16 (216) could not recognize this
situation and operated with this tablespace as UNIFORM, which led to a wrong value.
Cause: The code did not anticipate this situation.
Fix: Changed the SQL statement that gets info about tablespaces, so that information about
allocation type is there. Can now operate with LOCAL managed tablespace with USER
allocation and also with DICTIONARY tablespace.
ROSMM27955 Library load error when trying to connect to Oracle 9 on AIX
Problem: On some AIX systems, the following errors would occur when trying to connect to
Oracle 9.x:
Checking instance: 'XXX' @ '/u00/app/oracle/product/9.2.0': Could not load program
oracleXXX: Dependent module libjox9.a(shr.o) could not be loaded. Could not load module
libjox9.a(shr.o). Error was:
No such file or directory 02/25/03 16:56:42 ERROR dbspicao(66936)
XXX [cola:ora_util.pc:143]: DBSPI10-23: Unable to connect to database 'XXX' [ORA-12547:
TN S:lost contact]. See Instruction text or User's Guide for details.
Cause: The error output from dbspicao shows that only:
LIBPATH=/u00/app/oracle/product/9.2.0/lib32 is set. Libraries from
/u00/app/oracle/product/9.2.0/lib cannot be found.
Fix: Modified dbspicao to add both the lib and lib32 paths: export
LIBPATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib
ROSMM27961 MS SQL Server metrics 3011 was returning incorrect values.
Problem: Even after changing the maximum user connections, the DB-SPI calculated the metric
using the maximum possible user connections (usually 32K), which made the value incorrect.
Cause: The metric was using the wrong value for the calculation.
Fix: Since @@MAX_CONNECTIONS returns the maximum number of simultaneous user
connections allowed, not the current value, we first look into master..sysconfigures table for this
value (config=103). If the value is 0 (< 1), then we can use @@max_connections. If not, then it
is the number currently configured, so we use it. In addition, we do not take into account the first
50 PIDs as MS SQL Server does not take these into account when it counts user connections.
ROSMM28016 MS SQL 2000 metric 3278(9) did not work on some systems
Problem: On some MS SQL Server 2000 systems, the following errors were generated when
attempting to run metrics 3278 or 3279:
DBSPI40-19: Error opening cursor m216_70Cursor
[The cursor was not declared. (16945)]
DBSPI40-19: Error opening cursor mESQLCursor
[SELECT permission denied on object
'sysperfinfo', database 'master', o (14)]
Cause: This problem was caused by the SQL that was used in the metric. In one of the SQL
calls, it attempted to COLLATE based on the SQL_Latin1_General_CP1_CI_AS language. On
some systems, this language was not configured.
Fix: The fix is to use the 'database_default' COLLATE option.
ROSMM28036 Report for Oracle metric 69 was empty if created user was used.
Problem: If a user besides sys or system was used to connect to the DB-SPI (as in a user
created by the Add User feature of the Instance Manager), the report for Oracle 69 was empty:
Report For Database openview
Fri Feb 28 16:22:00 2003
Metric RBSegmentWaitPctCnt (0069)
Percentage
NAME STATUS WAITS GETS WAITS:GETS
--------------------- --------------- --------- --------- ----------
Cause: The script to create the user did not grant access to thev$rollname table.
Fix: The table v$rollname has been added to the list of grants.
ROSMM28114 MS SQL Server Metric 3025 value is incorrect.
Problem: The value for MS SQL Server metric 3025, CPU Used Percentage, is not correct. The
value has been consistently too low.
Cause: @@CPU_BUSY and spt_monitor.cpu_busy is in units of ticks and not milliseconds.
@@TIMETICKS is in units of microseconds.
Fix: To compute the CPU usage by the MS SQL Server, the following formula is now used:
CPU Usage =((((@@CPU_BUSY - spt_monitor.cpu_busy)/1000) *
(@@TIMETICKS/1000))* 100)/(time interval since last run)
ROSMM28117 SPI Oracle Metric 0045 returned a negative value.
Problem: Sometimes, metric 45 would generate the following alarm:
20.02.03 23:23:42 DBSPI-0045.1: Shared pool memory free percentage (- 4136.77%) too low
for PMCBS (<=1.00%). 20.02.03 23:23:43 DBSPI40-1: Unable to fetch data from table
'V$SGASTAT' [ORA-01455: converting column overflows integer datatype].
Cause: The function used to obtain the shared pool size did not allow for large enough values.
Fix: Use a different function, 'atof' instead of 'atoi'.
ROSMM28218 Informix DB-SPI producing extremely high load on customer system
Problem: The following command produces an extremely high load of read and write
operations and hangs the database on HP-UX 10.20:
/var/opt/OV/bin/OpC/monitor/dbspicai7 -m 22,24 -i xxxxx
Cause: The problem was actually caused by a defect in Informix.
Fix: The fix to the problem is to use the latest Informix client SDK to build the DB-SPI
collector. Once the newest SDK was used, the problem was solved.
ROSMM28307 MS SQL Server metric 3230 produced error. DBSPI40-1 (Cursor is not open)
Problem: When running the MS SQL Server metric 3230, the following errors are generated
DBSPI40-19: Error opening cursor mESQLCursor [SELECT permission denied on object
'sysperfinfo', database 'master']
Cause: Cursor processing was changed in MS SQL Server 2000.
Fix: The code processes the cursor using special SQL Server 2000 features.
ROSMM28543 DBSPI40-1: Unable to fetch data from table 'GV$ACTIVE_INSTANCES'
Problem: DB-SPI generated the error "DBSPI40-1: Unable to fetch data from table
'GV$ACTIVE_INSTANCES'" running Oracle metrics.
Cause: A GRANT statement was missing from the application "Create Oracle User" and
therefore the user did not have privileges to read from this table.
Fix: Added the line: "grant select on GV_$INSTANCE to &&DBSPI;"to dbspiocr.sql, used by
the "Create Oracle User" application.
Workaround: Manually GRANT select on the table or use "system".
ROSMM28918 Unable to stat file '...' (Value too large for defined data type)
Problem: The following error occurred with Oracle metrics 3, 16, and 203: 03/21/03 00:03:24
ERROR dbspicao(4305) PR1 [metric0016:ux_scriptcall.c:285]: DBSPI9-17: Unable to stat file
'/oradata/PR1/btabd.data1'. (Value too large for defined data type)
Cause: The involved files are larger than 2GB:
ls -al
/oraindex/PR1/btabi.data1 2621448192 Mar 19 15:39
/oradata/PR1/stabd.data1 3145736192 Mar 19 15:40
Fix: Changed stat and lstat to stat64 and lstat64 for all platforms except Tru64.
ROSMM29109 The dbspimsusr script was in the wrong location on the management server.
Problem: The application "Create MSSQL User" would fail on HP-UX managment servers.
Cause: The application had the call: /opt/OV/DBSPI/bin/dbspixterm -title
'Create User' -e /opt/OV/DBSPI/bin/dbspimsusr $OPC_NODES. But the
script /opt/OV/DBSPI/bin/dbspimsusr was only available for Solaris management
servers and did not exist on HP-UX management servers.
Fix: The script is now included.
ROSMM29129 DB-SPI did not work with CODA (the OVO subagent) on Tru64
Problem: On Tru64 systems, if DSI was not installed (with MeasureWare Agent), an error
would occur when creating grapher and reporter data sources.
Cause: The ddfcomp tool was not properly linked on a Tru64 system. It was missing a math
library.
Fix: The tool is now properly linked.
ROSMM29139 MS SQL Server tools Active Jobs and All Jobs could not be run as the user that DB-SPI creates.
Problem: When a user is created by the DB-SPI tool "Create MSSQL User" and used to
configure the MS SQL Server database connection, an error would occur.
Cause: The tool was missing some GRANT statements.
Fix: The necessary GRANT statements have been added to the tool.
ROSMM29575 MS SQL Server metric 3218 returned an incorrect value.
Problem: Stored procedure sp_spaceused seemed to include transaction logs in "database_size,
but just the unallocated space in the database in "unallocated space." This meant that, for
example, according to SQL Enterprise Manager there was 85MB data, 15MB unallocated,
195MB transaction log, 175MB unallocated transaction log. sp_spaceused now includes the
transaction log data, so the DBSPI calculates:
((Data+Transaction Log)-unallocated)*100
----------------------------------------
(Data+Transaction Log)
which resulted (according to our example) in 94% (85+195-15)*100/(85+195)but should have
been: 82% (85-15)*100/85 (disregarding transaction logs)
Cause: Because sp_spaceused did not return expected values, metric 3218 returned incorrect
values.
Fix: Instead of using stored procedure sp_spaceused, the following SQL statement is used:
select db_name(),
((select
sum(convert(dec(15),size))
from
dbo.sysfiles
where
(status & 64 = 0)) -
(select
sum(convert(dec(15),reserved))
from
sysindexes
where
indid in (0, 1, 255))) * 8,
(select
(select
sum(convert(dec(15),reserved))
from
sysindexes
where
indid in (0, 1, 255)) * low / 1024
from
master.dbo.spt_values
where
number = 1 and type = 'E')
This SQL statement returns the values we expect.
ROSMM29700 File name was truncated in report for MS SQL Server metric 3278
Problem: When running the report for metric 3278, the file in the report was truncated:
Additional
Space ... Filename
----------- --------------------------------------------------
12981248 C:\Program Files\MSSQL\data\m
12981248 C:\Program Files\MSSQL\data\m
Cause: Incorrect report generation
Fix: The filename is no longer truncated:
Additional
Space ... Filename
----------- --------------------------------------------------
12981248 C:\Program Files\MSSQL\data\mastlog.ldf
12981248 C:\Program Files\MSSQL\data\master.mdf
ROSMM30035 Filter code was not converting 3-digit metric number into 4-digit number.
Problem: When configuring filters, you must specify the 4 digit metric number instead of just
the 3 digit number. For example, for the MS SQL Server metric 3209, if the filter metric
number is specified as 209, the filter will not work. It will be accepted, but it will not pass the
SQL to the database when running the metric.
Cause: The code that processed the filter did not take into account the smaller metric numbers.
Fix: The filter process code now adds 1000 to Informix metrics, 2000 to Sybase metrics and
3000 to MS SQL Server metrics if the full 4-digit metric number is not specified.
ROSMM30716 DBSPI10-51: Internal Error from OVO for UNIX (ITO) interface (DBSPI-0216)
Problem: While monitoring Oracle 7.3.4 on HP-UX 11, the following error occurred:
"DBSPI10-51: Internal Error from ITO interface (DBSPI-0216): 'OpC error: Wrong optional
variables.'
Cause: In order to support Oracle 7.3 on HP-UX 11, an older OVO library was included with
DB-SPI. Because this OVO library was relatively old, it did not support blanks in variables.
Fix: A newer OVO library is now included.
ROSMM30833 Oracle metric 6 failed with 'ORA-01405: fetched column value is NULL'
Problem: In some situations, Oracle metric 6 would fail with 'ORA-01405: fetched column
value is NULL'.
Cause: A query came back with a NULL value that was not anticipated.
Fix: The NULL value is mapped to a zero for the query.
ROSMM31156 Report for Sybase metric 55 would hang when there were blocked processes.
Problem: When metric 55 found blocked processes the automatic action executed
/var/opt/OV/bin/OpC/actions/dbspirls -m 55 -r 1 -i MTOMC1.
This would hang the isql child process (using a lot of CPU time) if there were blocked processes.
The report executes with not problem if there are no blocked processes.
Cause: In stored procedure sp_dbspi_rpm_who there was a potential endless loop:
while ((select count (1) from #tmp_blk) != 0)
Fix: The stored procedure was changed to:
while ((select count (1) from #tmp_blk) != 0 and @i > 0)
Now the loop can ot be performed more than 100 times.
ROSMM31191 ORA-01405 null fetch error occurred when V$VERSION contained a NULL
Problem: Sometimes, the error would come up over and over with an Oracle7 instance.
Node: rosspidb3.rose.hp.com
Message group: DBSPI
Application: HP DBSPI
Object: ORCL:cola
Severity: Critical
Text: DBSPI40-1: Unable to fetch data from table 'ovam_get_ora_version Fetch from
V$VERSION' [ORA-01405: fetched column value is NULL].
Cause: A null value in V$VERSION.
Fix: Added an "is not null" to the where clause for the query for the metric.
ROSMM31217 If Sybase SERVER was DISABLED, DATABASE entries still were made in dbtab
Problem: In the following configuration example:
SYNTAX_VERSION 4
SYBASE
HOME "/sybase"
SERVER "sunbase" CONNECT "sa/dbspi99"
DISABLED
DATABASE pubs2
SYBASE
HOME "/oracle/Sybase"
SERVER "SUNBUG_SYBASE" CONNECT "sa/"
DISABLED
DATABASE pubs2
HOME "/sybase"
SERVER "SUNBUG_SYBA" CONNECT ""
DISABLED
The dbtab file had the entries:
ORACLE openview /opt/oracle/product/8.1.7
SYBASE DATABASE pubs2 sunbase
SYBASE DATABASE pubs2 SUNBUG_SYBASE
No DATABASE entries should exist for DISABLED SERVER's.
Cause: The configuration program processed the DATABASE line even when the SERVER
was DISABLED.
Fix: The DATABASE lines are now skipped whenever SERVER/DISABLED is encountered.
ROSMM31531 Metric 45 report returned ORA-01455: converting column overflows integer datatype
Problem: The report for Metric 45 would sometimes return the error
"[metric0045:metric0045.pc:147]: DBSPI40-1: Unable to fetch data from table 'V$SGASTAT'
[ORA-01455: converting column overflows integer datatype]."
Cause: The bytes column in the v$sgastat table had values too large; for example,
db_block_buffers = 8192000000
Fix: Increased the size of the internal datatype
A.06.00 FIXES
NSMBB45238 Arithmetic overflow in Sybase Free Space application
Problem: When executing the Free Space application from the Application bank, the following
output is noted:
Checking log size for Sybase Server: IDEEACP_db
Password: dbName
device_fragments usage size free kB free %
------------------------------ --------------------------
(return status = 0)
Arithmetic overflow occurred.
Cause: In the underlying SP sp_dbspi_checklogsize the multiplications / divisions were
done in an order that caused the overlow for a large database; i.e., large size values.
Fix: Changed the order of the arithmetic operations.
NSMBB47563 Monitor dbspi_lsnr sometimes does detect listener down.
Problem: Monitor dbspi_lsnr sometimes does detect listener down.
Cause: There seems to be a bug in function check_lsnr_status of monitor program dbspi_lsnr.
The function is:
check_lsnr_status()
{
LSNR_STATUS="OK"
LSNR_STATUS=`lsnrctl status | grep TNS`
if [ "$LSNR_STATUS" = "" ]
then
LSNR_STATUS="TNS_ERROR"
if
}
But what if the output is:
LSNR_STATUS=TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
TNS-12541: TNS:no listener
+ [ TNS-12541: TNS:no listener
TNS-00511: No listener = ]
+ [ TNS-12541: TNS:no listener
TNS-00511: No listener = TNS_ERROR ]
This will not give an error because there are plenty of TNS's that are grepped in here!
Fix: Added the check for additional text in the condition for error.
NSMBB48207 Getting Oracle syntax error with metrics 16 and 216 on Windows.
Problem: In some cases, metrics 16 and 216 would fail with the following error:
DBSPI40-10 - Error parsing SQL statement for metric 0016 [select
s.file#,s.block#,s.ts#,s.extsize,dbms_space_admin.segment_number_extents
(ts.ts#,s.file#,s.block#, s.type#,s.cachehint,nvl
(s.spare1,0),o.dataobj#,
decode(bitand(ts.flags,3),1,to_number(0),s.extsize *ts.blocksize)),
s.maxexts, dbms_space_admin.segment_number_blocks(ts.tsts.blocksize from
sys.obj$ o, sys.ts$ ts, sys.seg$ s, sys.sys_objects so where ts.name=:v1
and s.ts#=ts.ts# and s.file#=so.header_file and s.block#=so.header_block
and o.obj#=so.object_id and s.type#=so.segment_type_id and
o.type#=so.object_type_id and s.type# <> 4].
Cause: The problem occurred because a precompiler incorrectly removed a line.
Fix: The code was modified to work around the precompiler problem.
NSMFC33907 MS SQL Logfile Policy did not work for SQLAGENT logfile when in UNICODE format.
Problem: If the SQLAGENT logfile was in UNICODE format, then DB-SPI would not detect
errors in this file.
Cause: A single logfile policy tried to monitor both the error logfile and the SQL Agent logfile.
The error logfile is in ASCII, but the SQL Agent logfile was in UNICODE.
Fix: A preprocessor now converts UNICODE to ASCII and the policy can monitor the
converted temporary file created from combining the SQL Agent logfile and the error logfile.
ROSMM18994 Configuration check looked at Oracle and MSS even if not installed.
Problem: If the following definition for SQL Server was created:
SYNTAX_VERSION 2
MSSQL
SERVER ""
Then when updating the configuration, an error would occur:
"ERROR: Not found the specified file."
Cause: The script tried to check Oracle and MS SQL Server instances even if only one was
installed.
Fix: The script will determine if the Oracle and MS SQL SPI is installed before running the
check.
ROSMM21664 Syntax error on automatic action report for MS SQL metric 5
Problem: Sometimes dbspirlm 5, which is the automatic action report for metric 5, will result in
a syntax error.
Cause: The batch file will execute the command
"type C:/usr/OV\bin\OpC\cmds\dbspirpt0565" (mind the slashes!).
The slashes are there that way, because in the registry,
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\ITO\Installation
Directory contains "/usr/OV"
(this is read and set in dbspienv.bat).
Fix: The script dbspienv.bat get the path for monitors, commands, actions from registry. There is
a wrong slash in the registry. We have changed dbspienv.bat to replace "/" by "\".
ROSMM22967 Create SP/Oracle UDM doesn't work with Oracle 9i
Problem: When using this application with Oracle 9i, the following error occurs:
USING svrmgrl: svrmgrl
command=@/var/opt/OV/dbspi/tmp/temposp.sql
/var/opt/OV/bin/OpC/cmds/dbspiudmosp[605]: svrmgrl: not found
Cause: It was not updated to work with 9i.
Fix: It now using sqlplus where necessary.
ROSMM24177 DBSPI-3279: unit was in kilobytes, not in megabytes
Problem: The metric was returning kilobytes, but the message said megabytes.
Cause: The code was not dividing by 1024.
Fix: The code now divides by 1024 and sends megabytes to the message.
ROSMM24471 If the customer did not accept the default Sybase 12.5 installation directories, DB-SPI would
fail. OCS-12_5 ASE-12_5
Problem: If customer did not accept the default Sybase 12.5 installation directories, DB-SPI
would fail. By default, the ASE and OCS diretories are OCS-12_5 and ASE-12_5. If the
customer used different directories, then DB-SPI would fail.
Cause: DB-SPI did not anticipate that customers could name their own directories.
Fix: Added two new configuration parameters, SYBASE_OCS and SYBASE_ASE which can
be added to define the name of the directories. Only the name of the directories are needed, not
the full path to the directories. For example:
SYBASE
HOME /opt/Sybase
SYBASE_OCS MY_OCS
SYBASE_ASE MY_ASE
SERVER sunbase
CONNECT sa/pass
ROSMM24558 Sometimes an error was generated with MS SQL "Unable to fetch data from table 'sysusages'"
on a network file system"
Problem: Sometimes an error occurred with MS SQL "Unable to fetch data from table
'sysusages'" on a network file system"
Cause: This was caused by an improper usage of a NULL value
Fix: The NULL value is properly handled.
ROSMM24582 dbspicao74 would sometimes create a huge CPU load
Problem: In some situations, the DB-SPI collector dbspicao74 would take a large amount of
CPU because it was caught in an infinite loop.
Cause: On fast machines, it happened that while reading from the pipe, the child process had
been terminated already and the read was interrupted by the SIGCHLD signal. This caused the
program to go into an infinite loop.
Fix: The signal SIGCLD is blocked now during the read from the pipe, and the infinite loop no
longer occurs.
ROSMM24740 MS SQL Server metric 3025 had numerous problems due to Microsoft issues
Problem: First, it was not clear what this metric represents if multiple CPU's were on the
system. Second, sometimes the values returned from this metric did not seem correct.
Cause: Due to misinformation from Microsoft, the algorithm was wrong. The metric did not
consider the number of CPUs.
Fix: In addition to fixing the algorithm, the instruction text was updated to show the number of
CPUs. As a result 100% means 100% of all CPUs.
ROSMM24904 DB-SPI required the customer to install 32-bit libraries on a 64-bit Sybase 12.5 system
Problem: By default, Sybase does not install 32-bit libraries, but DB-SPI required them. This
caused the collector to fail.
Cause: DB-SPI was built with dynamic libraries and it expected the 32-bit libraries to be
installed on the system.
Fix: Starting with A.06.02, for Sybase 12.5, DB-SPI will use a collector that is built with static
32-bit libraries so that the customer is not required to install the 32-bit libraries on the Sybase
12.5 system.
ROSMM24955 Oracle metric 6 dumped core.
Problem: On some systems, Oracle metric 6 would dump core in dbspi_arch_fsfree.
Cause: Improper use of a NULL pointer
Fix: Fixed the usage of the NULL pointer
<**** This CR impacts the documentation ****>
ROSMM24975 Oracle metric 1 was not working as expected for restricted sessions
Problem: When a database was open with restricted sessions, it was expected that the monitor
condition for restricted sessions would be met, but it was not. The message "DBSPI-0001.1:
dbname is in restricted mode." was expected but instead the message "DBSPI-0001.3: DB-SPI
cannot connect to database dbname, may be down; Oracle error: ORA-01035: ORACLE only
available to users with RESTRICTED SESSION privilege." was produced.
Cause: dbspicao tried to connect and look at v$instance to report the state and if in
RESTRICTED mode sent the value 2 to the monitor, resulting in the appropriate message. If it
could not connect to the database, it returned 3 and this resulted in the message that it could not
connect. The problem was that if the database was in restricted mode, and the DB-SPI user did
not have restricted session privilege (by default it did not), then it could not connect and thus the
monitor returned 3: "DBSPI-0001.3: DB-SPI cannot connect to database
dbname, may be down; Oracle error: ORA-01035: ORACLE only
available to users with RESTRICTED SESSION privilege." instead
of 2: "DBSPI-0001.1: dbname is in restricted mode."
Fix: DB-SPI now parses the string to see if ORA-01035 is generated. If so, it returns the value
of 2 and generates the correct message.
ROSMM24998 DB-SPI could not connect to Informix 9.2 on Solaris 2.8
Problem: DB-SPI could not connect to Informix 9.2 on Solaris 2.8; it generated an error
"DBSPI10-21: Unable to connect to database 'sysmaster' as 'informix' [SQLCODE: -25572]."
Cause: This was caused by using an older client SDK.
Fix: Use a Solaris 2.8 client SDK for 5.6, which will run on Solaris 7 and higher.
ROSMM25141 Connection to Oracle would Dr. Watson when > 1 version installed
Problem: When more than 1 version of Oracle is installed, the DB-SPI Oracle collector can Dr.
Watson
Cause: If the wrong version is first in the PATH, DB-SPI will link to the wrong libraries
Fix: The path to the libraries is put at the front of the PATH so it always picks up the right
version.
ROSMM25188 Report for Sybase metric 2055 caused high CPU load
Problem: Sometimes the report for metric 2055, which reports on blocked processes, would go
into an infinite loop and take all the CPU.
Cause: A query in the report was incorrectly written.
Fix: The report was corrected.
ROSMM25443 DB-SPI could not resolve logfile name on Oracle 9.2 on NT
Problem: Staring with Oracle 9.2 on Windows, DB-SPI would generate an error in the browser
such as:
"Logfile D:\oracle\admin\OEMR\bdump\OEMRALRT.log doesn't exist.
Treating as empty. (OpC30-108)"
Cause: The format of the logfile changed with version 9.2. It used to be
"<INSTANCE>ALRT.log" but now it is "alert_<INSTANC"E".log. So for the above example, it
would be "D:\oracle\admin\OEMR\bdump\alert_OEMR.log".
Fix: For Oracle 9.2, format the logfile name differently.
ROSMM26096 DBSPI application 'Create Oracle User' failed for Oracle 9.2
Problem: When running this application, the following error would occur:
SQL*Plus: Release 9.2.0.1.0 - Production on Thu
Oct 17 17:52:53 2002
Copyright (c) 1982, 2002, Oracle Corporation.
All rights reserved.
string ""SYSDBA"" " missing terminating quote (").
Cause: The application was not running sqlplus correctly.
Fix: It was modified to run sqlplus correctly.
ROSMM26190 dbspi_lsnr script still running. (OpC30-610)
Problem: The following error message would appear in the browser from time to time. When it
appeared once, it would continue to appear until customer killed the script:
10/08/02 10:10:20 WARNING opcmona (Monitor Agent)(14083)
[genmona.c:4366]: Can't start monitor script for object 'DBSPI-
Ora-Listener'.
Script still running. (OpC30-610)
Cause: If the defaults file did not exist, a grep into this file would sometimes go into an infinite
loop.
Fix: The grep is not attempted if the defaults file does not exist.
ROSMM26513 LOGFILE entry for SQL*Net was wrong (but was not reported in -l)
Problem: If a remote connection was configured:
C:\>dbspicfg e
SYNTAX_VERSION 4
ORACLE
HOME "C:\oracle\ora81"
DATABASE ora817 CONNECT "system/manager"
LOGFILE "C:\oracle\admin\ora817\bdump\ora817ALRT.log"
MSSQL
SERVER "rosspi6\RANDAZZO" CONNECT "sa/rpmtest"
ORACLE
HOME "c:\oracle\ora81"
DATABASE test CONNECT system/manager@ora817
LOGFILE "C:\oracle\admin\ora817\bdump\testALRT.log"
The LOGFILE entry for the "@ora817" was wrong.
Fortunately, the "-l" did not return the bogus file:
C:\>dbspicao -l
C:\oracle\admin\ora817\bdump\ora817ALRT.log
Cause: The code that populates the LOGFILE entries did not ignore connections with an alias.
Fix: For remote connections (those with "@" in the connect string), we will not add a LOGFILE
entry at all since it is not possible to monitor remote connection logfiles.
ROSMM26567 Oracle metric 6 showed negative file system free space
Problem: DB-SPI would sometimes indicate a negative value for filesystem freespace when
running metric 6, and there was plenty of filesystem freespace.
Cause: The DBSPI computed the difference between MAXBLOCKS (for example 64000) and
BLOCKS (for example 128000) to determine how many blocks are available for expanding the
data file. In some situations, this resulted in a negative number (-64000). This negative number
was then used for further computations and hence the negative free space.
Creating (or even altering) a tablespace having MAXBLOCKS less than the current (or initial) size
was allowed. In this situation, Oracle used the initially allocated data and then failed if more
extents were allocated. Thus, the allocation of more space was effectively turned off.
Fix: If the computation of (SYS.FILEXT$.maxextend < DBA_DATA_FILES.blocks) yields a
result less than zero, set the result to zero, thus handling this situation as 'no more block
available to allocate'.
ROSMM27085 MS SQL Server metric 3277 could report thousands of messages
Problem: MS SQL server metric 3277 reports on the status of all jobs, including jobs that
completed successfully. This clutters up the browser with "Normal" messages.
Cause: It was originally thought that sending a message for completed successful job was OK.
Fix: The condition that reported a successful job was removed. The other conditions for job
aborted or cancelled still remain.
ROSMM27106 Metrics MS SQL Server 3278 and 3279 sometimes alarmed incorrectly.
Problem: Metrics 3278/9 intermittently gave incorrect values, reporting space problems when
there were none.
Cause: Both metrics used the same temporary table and when run at the same time, incorrect
results occurred.
Fix: Unique temporary tables for each metric are used.
ROSMM27106 MS SQL Server metrics 3278 and 3279 would sometime report incorrect values
Problem: Sometimes, metrics 3278 and 3279 would alarm on incorrect values.
Cause: This problem was caused because both metrics would use the same temporary table and
only if they were run at the same time would the incorrect values be generated because the data
in the temporary tables from each metric would collide.
Fix: One of the metrics was modified to use a different temporary table.
Chapter 4: Known Problems & Workarounds
Please see below for potential issues/workarounds as relevant to your database type/environment.
Oracle Database Connection Issue:
Connection to a database can fail if an operating-system user that is different from oracle user is
used. This problem is known at Oracle and occurs because older Oracle versions use different libraries.
As a workaround, Oracle suggests the following:

Configure the Database SPI connections to a database as follows:
1. Run the Configure Database Connections (in the Oracle applications group)application on a
managed node.
(an ASCII text editor opens and displays something like the following):
SYNTAX_VERSION 3
ORACLE
HOME "/opt/oracle/product/8.0.6"
DATABASE openview
CONNECT "system/manager"
LOGFILE
"/opt/oracle/admin/openview/bdump/alert_openview.log"
2. Enter the following alternative for the connection string.
CONNECT <user>/<password>@<$ORACLE_SID>

EXAMPLE:
CONNECT "hp_ito/secret@hr_db"
Cluster Configurations
The cluster fail-over sub-agent (OpC APM) does not currently work correctly for VERITAS clusters
on Solaris. Please go to http://suppport.openview.hp.com/ and search for "veritas clusters" to find the
latest updates and possible resolutions relating to this known problem. For a temporary workaround,
please see Chapter 7, Monitoring Clustered (Fail-over) Environments, Using Earlier OVO Agents.
Chapter 5: Compatibility And Installation Requirements
No new supported operating system or database type versions have been added since the Database SPI
A.06.00 release. Changes to supported versions since A.05.20 up to A.06.00, though are still listed.
NOTE: While only major database versions are listed, you can assume support of minor updates to those
versions as well; for example, because DB-SPI supports Sybase 12.5, it also supports 12.5.01, 12.5.03, etc.
OPENVIEW OPERATIONS SOFTWARE SUPPORTED
Managed Node Version Supported
Changes Since
A.05.20
OpenView Operations (also known
as ITO and VPO)
6.0. 7.0, 7.1
Added 7.1
Oracle Enterprise Server, all 32-
and 64-bit versions
7.3.x (HP-UX 10.20, 11.0, 11i; AIX 4.3, 5L 5.1;
Solaris 2.6, 7, 8, 9; Windows NT 4, 2000)
8.0.x (HP-UX 10.20, 11.0, 11i; AIX 4.3, 5L 5.1;
Solaris 2.6, 7, 8, 9; Windows NT 4, 2000;
Tru64 4.0F, 4.0G, 5.0A, 5.1, 5.1A)
8.1.x (HP-UX 10.20, 11.0, 11i; AIX 4.3, 5L 5.1;
Tru64 4.0F, 4.0G, 5.0A, 5.1, 5.1A)
9.0, 9.2 (HP-UX 10.20, 11.0, 11i; AIX 4.3, 5L 5.1;
Tru64 4.0F, 4.0G, 5.0A, 5.1, 5.1A)
Added Oracle 9.2,
Oracle on Tru64,
Oracle RAC;
Solaris 9
Informix Dynamic Server, all 32-
and 64-bit versions
7.2 (HP-UX 10.20, 11.0, 11i; Solaris 2.6, 7, 8, 9)
7.3 (HP-UX 10.20, 11.0, 11i; Solaris 2.6, 7, 8, 9)
9.1 (HP-UX 10.20, 11.0, 11i; Solaris 2.6, 7, 8, 9)
9.2 (HP-UX 10.20, 11.0, 11i; Solaris 2.6, 7, 8, 9)
Added Solaris 9
Sybase Adaptive Enterprise Server,
all 32- and 64-bit versions
11.0.3.x
(HP-UX 10.20, 11.0, 11i; AIX 4.3; Solaris 2.6, 7, 8, 9)
11.5
11.9
12.0
12.5
Added Solaris 9
Microsoft SQL Server 6.5 (Windows NT 4, 2000)
7.0 (Windows NT 4, 2000)
2000 (Windows NT 4, 2000)

OpenView Performance Agent
(also known as MeasureWare)
C.02 (all platforms or greater)
C.03 (all platforms or greater)

Reporter A.02, A.03

Chapter 6: SOFTWARE AVAILABILITY IN NATIVE LANGUAGES
The Database SPI for both Oracle and MS SQL Server is also available in Japanese, with the localized
Japanese DB-SPI policies containing a _jp suffix. No other change is necessary for the out-of-the-box
policies to work. However, any change within the command-line must take the Japanese policy name into
consideration in order for the localized version to continue working successfully as explained below.
The _jp suffix created the need for two command-line changes:
1. Policies that run metrics according to a schedule will communicate the metric values back to the
threshold policy by name. For example, the DBSPI-Ora-05min_jp policy sends a value to the
DBSPI-0001_jp policy. The new command line option -x suffix=_jp is used to tell the collector
to attach a suffix of _jp to the name of the threshold policy.
2. Some schedule policies require a -c option in order for the collector to acknowledge the schedule
policy that ran it when collection is complete. The -c option should always contain the name of
the policy (for example, -c DBSPI-Ora-05min_jp).
Note: If you use the Database SPI in a cluster-aware environment, please follow the instructions in Chapter
7 of the Configuration Guide. In that chapter you create an XML file that adapts the DB-SPI to a cluster-
aware environment. Please be sure to add the _jp suffix to the XML file name so that the file is
recognized as a localizable file.

DBSPI

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

DBSPI

Încărcat de

Drepturi de autor:

Formate disponibile

HP OPENVIEW

Smart Plug-ins for Databases

S-ar putea să vă placă și