This contains some questions users have asked while trying to setup or use PATROL for Microsoft SQL Server to monitor Microsoft SQL Server.
If you have a question that does not appear in this, please refer to PATROL for Microsoft SQL Server Documentation for migration, installation, and configuration information, and general information about the features in PATROL for Microsoft SQL Server.
BMC Software, Inc. also offers a customer support website that contains a complete list of fixes, workarounds, and frequently asked questions. However, the latest version of PATROL for Microsoft SQL Server may resolve many if not all of the problems discussed in the customer support website, so we recommend that you upgrade to the latest version, if you have not already done so. To access the customer support website, go to http://www.bmc.com/support and under the Solve a Technical Problem topic, select Search for Fixes, Workarounds & FAQs in our Knowledge Database.
Note
You need a BMC customer user name and password to enter the BMC customer support website. If you do not have one, please contact your BMC sales representative.
List of questions
- Why are some parameter icons missing?
- What should I do if SQL Server objects are not available?
- Why is the SQL Server instance in an offline mode even though the SQL Server is online?
- Why are some of the application icons missing?
- Why does PATROL for SQL Server require system administrator privileges to run?
- Why do the BlockerProcs and IdleProcs parameters fail to alarm?
- Why do I get repetitive creations and deletions of the Publication and Subscriber instances?
Why is the SQL Server not starting?
If the SQL Server does not start, look at the error log created in /log/ERRORLOG for information about why it will not start. You may also want to start SQL Server from the command line using the -f startup option. This option starts the SQL Server in a minimal configuration mode and enables you to reconfigure the SQL Server. See your Microsoft SQL Server documentation or consult with the SQL database administrator for more information.
Why are some parameter icons missing?
See the online Help topic for the missing parameter for information about why a particular parameter icon does not appear on your screen.
What should I do when SQL Server objects are not available?
The SQL Performance objects must be installed on the SQL Server and available to PATROL in order for PATROL for Microsoft SQL Server to operate. Occasionally the SQL Performance objects are missing from the server. If PATROL for Microsoft SQL Server cannot find the SQL Server performance objects it requires to operate, it cannot configure the instance, and it generates the following message:
These SQL Server performance objects are not available.
The missing performance counters can be rebuilt using lodctr command and the configuration file (perf-MSSQLSERVERsqlctr) located at ..\MSSQL\Binn directory. Please consult with the SQL DBA and the System Administrator before making any changes to the SQL Server Configuration. If you cannot resolve this issue, refer to your Microsoft SQL Server manual, see the Microsoft technical information website, or call Microsoft support.
Why is the SQL Server instance in an offline mode even though the SQL Server is online?
If the Server application instance for a SQL Server displays in an offline mode (grayed-out), and you are sure that the SQL Server is online, then it is possible that PATROL discovered the SQL Server but could not locate the Osql.exe file on the SQL Server.
Also, PATROL discovery sends a query to determine the status of the SQL Server, and it is possible that another problem caused the query to fail.
Why are some of the application icons missing?
Several of the applications require that you perform specific setup and configuration steps before PATROL for Microsoft SQL Server can generate application icons for those applications. To create an application icon and monitor one of the following features, see the topics listed:
- To create Error Log application icons to monitor error logs, see SQL Server Error Log (Error Log) and Monitoring the SQL Server error logs
- To create File application icons to monitor files, see File application class andMonitoring files and file groups.
- To create Filegroup application icons to monitor file groups, see SQL Server File Group (Filegroup) and Monitoring files and file groups.
- To create Published application icons to monitor the published articles for replication, see SQL Server Published (Published) and Monitoring subscribers and published articles.
- To create Subscribers application icons to monitor the subscribers for replication, see SQL Server Subscribers (Subscribers) and Monitoring subscribers and published articles
- To create Object application icons to montor user-selected tables or indexes, see SQL Server Objects (Objects)
- To create Users application icons to monitor users and processes, see Users application class and Monitoring users and processes.
Note
Changes made to the monitoring status of these features do not take effect until the collector parameter responsible for these features completes a polling cycle.
Why does PATROL for SQL Server require system administrator privileges to run?
The built-in security system for Microsoft SQL Server requires an account with system administrator (SA) privileges for functions that are performed within a database, and PATROL must operate within this security system. Most of the functions performed by PATROL do not require SA privileges, so PATROL uses two different accounts to monitor Microsoft SQL Servers. PATROL uses the account that requires SA privileges to configure PATROL for Microsoft SQL Server to monitor the server, to access vital information about the server, and to execute processes that return critical information about the server's performance. Specifically, PATROL for Microsoft SQL Server uses the SA account when performing the following functions:
- Configuration
- SQL Snapshot
During setup, PATROL objects (stored procedures) are created on the SQL Server in the master database. PATROL calls these stored procedures periodically, and SA privileges are required for those calls.
You can set up PATROL to function without using the SA account by using integrated security on the SQL Server and using another account with SA provileges on the domain and the SQL Server. This would still require a password assignment and updates of the password when password changes are implemented.
Note
PATROL observes password security at every level. All passwords are encrypted by PATROL to prevent unauthorized access.
Why do the BlockerProcs and IdleProcs parameters fail to alarm?
Logins excluded from monitoring do not cause these parameters to alarm. By default, the sa, probe, repl_subscriber, and repl_publishers logins are excluded from monitoring.
SQL Server logins excluded from monitoring using the KM Admin > User Monitoring Admin > Configure Auto User Monitoring fail to cause the BlockerProcs or IdleProcs parameters to alarm.
Why do I get repetitive creations and deletions of the Publication and Subscriber instances?
PATROL for Microsoft SQL Server cannot handle publication and subscriber names that contain spaces. The workaround is to rename the pulications and subscribers in the SQL Server to names without spaces.
Related topics
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks