Oracle® Enterprise Manager

System Monitoring Plug-in Installation Guide for Sybase Adaptive Server Enterprise (ASE)

Release 12.1.0.3.0

E25214-05

September 2014

This document provides a brief description about the Oracle System Monitoring Plug-in for Sybase Adaptive Server Enterprise, details on the versions the plug-in supports, prerequisites for installing the plug-in, and step-by-step instructions on how to install, verify, and validate the plug-in.

The following sections are described:

1 Description

The System Monitoring Plug-in for Sybase Adaptive Server Enterprise extends Oracle Enterprise Manager Cloud Control 12c to add support for managing Sybase Adaptive Server instances. By deploying the plug-in within your Cloud Control environment, you gain the following management features:

  • Monitor Sybase Adaptive Server instances.

  • Gather configuration data and track configuration changes for Sybase Adaptive Server instances.

  • Raise alerts and violations based on thresholds set on monitored metrics and configuration data.

  • Provide rich out-of-box reports based on the gathered data.

  • Support monitoring by a remote Agent. Local Agent is an agent running on the same host as the Sybase Adaptive Server. Remote Agent is an agent running on a host that is different from the host where Sybase Adaptive Server is running.

  • Collect and display top SQL Statements and their related statistics, including CPU Time and Execution Count, of your Sybase ASE Database.

  • Collect and display information regarding the top Lock Wait Events in Sybase ASE Database, including top Wait Count by Table and top Wait Times.

  • Utilization of Cloud Control jobs to start and stop the Sybase ASE database. These jobs are not only accessible from the Cloud Control Jobs Library but also from the Sybase ASE plug-in's UI homepage.

  • Expose vital Sybase ASE metrics in the form of easy-to-use charts and tables.

2 What's New in This Release

This release of the Sybase ASE Database plug-in for Oracle Enterprise Manager Cloud Control 12c includes many new features for better visibility into your Sybase ASE environment. Highlighted below are some of the new features included in this release.

Version Support Updates

The Sybase ASE Database plug-in for Oracle Enterprise Manager Cloud Control 12c has been updated to be current with the latest release of Sybase ASE Databases. This includes the added support for SAP ASE 15.7 and 16.0.

Updated User Interface

The user interface has been updated adding in a new Analysis page and updating the Home page from the previous release.

The home page (Figure 1) has been updated to enhance Sybase ASE summary metrics for quicker trouble detection and resolution. The home page has also been updated to expose additional performance and health metrics, such as: job summary, incidents, memory usage summary and more.

Figure 1 Sybase ASE Database Plug-in Home Page

Surrounding text describes Figure 1 .

The all-new Analysis page (Figure 2) has been added to the plug-in to give greater insight into the monitored Sybase ASE SQL Statistics, Lock Waits, Application Waits and more.

Figure 2 Sybase ASE Database Plug-in Analysis Page

Surrounding text describes Figure 2 .

Sybase ASE Top SQL Queries

This release adds the ability to monitor and return metrics on the top SQL queries from your Sybase ASE Database. This view is included in the new analysis page and displays the top queries that can be organized by CPU Time, Wait Time, or Memory.

The Top SQL Statements (Figure 3) can also be adjusted to view the top queries by day, week, or month.

Figure 3 Top SQL Statements

Surrounding text describes Figure 3 .

Sybase ASE Top Lock Waits

Also added to the Analysis page is the metrics for the monitoring of Sybase ASE Lock Wait Events. This table (Figure 4) shows the top lock wait events in Sybase ASE and can be organized by blocking Wait Time or Wait Count.

Figure 4 Top Wait Events

Surrounding text describes Figure 4 .

Additional Jobs

All new to this release are the Startup Sybase ASE and Shutdown Sybase ASE jobs. These jobs can be accessed from the Cloud Control Jobs Library, or directly from the user interface of the plug-in.

See Creating and Editing Jobs for more information on using these jobs.

3 Platforms Supported

The plug-in supports monitoring of Sybase Adaptive Server Enterprise (ASE) on all the platforms where Sybase ASE can be installed.

4 Versions Supported

This plug-in supports the following versions of products:

  • Enterprise Manager 12c Cloud Control Release 4 (12.1.0.4.0) or higher

  • Version 15.7 and 16.0 or higher of Express (XE), Enterprise (EE), and Developer (DE) editions of Sybase Adaptive Server Enterprise.

Note:

The system monitoring plug-in for Sybase Adaptive Server is not certified for monitoring Sybase Adaptive Server Clusters. For more information, refer to the known issues described in the Oracle Enterprise Manager System Monitoring Plug-in Troubleshooting Guide.

5 Prerequisites

The following prerequisites must be met before you can deploy the plug-in:

  • Sybase Adaptive Server Enterprise version 15.7 to 16.0 or higher is installed.

  • The following components of Oracle Enterprise Manager Cloud Control are installed and running:

    • Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4.0) or higher

    • Oracle Management Agent 12.1.0.4.0 or higher (any platform supported by this release of agent)

      You can install the agent on the same computer as Sybase Adaptive Server (referred to as local agent monitoring), or you can install the agent on a different host computer from Sybase Adaptive Server (referred to as remote agent monitoring).

  • The Monitoring and Diagnostic (MDA) tables must be installed before they can be queried. To install MDA tables, do the following:

    1. Ensure that the configuration parameter enable cis is set to 1. If not, restart ASE. Run the following command:

      sp_configure 'enable cis', 1 
      go
      
    2. Install the MDA tables. Do not run this script with 'sqsh' as it will cause errors. 'sqsh' sees a '$' as the start of a sqsh variable, and this distorts the native RPC names, since these start with a '$' as well. Instead, either use 'isql' as below, or run 'sqsh' with the '-Lexpand=0' option to disable sqsh variable expansion feature. This script is included in the installmaster.

      isql -U sa -P yourpassword -S YOURSERVER \
           -i $SYBASE/$SYBASE_ASE/scripts/installmontables
      
    3. Assign mon_role to logins allowed MDA access. This also applies to the 'sa' login.

      use master
      go
      grant role mon_role to sa
      go
      
    4. Test basic MDA configuration as follows. You may need to disconnect and reconnect to activate mon_role when you grant this role to the login you are currently using.

      select * from master..monState
      go
      
    5. Enable all configuration parameters. These are all dynamic (except the per object statistics active parameter). For all 'pipe' tables, the number of messages is set to 100 here, but you can choose a larger size.

      sp_configure "enable monitoring", 1
      go
      sp_configure "sql text pipe active", 1
      go
      sp_configure "sql text pipe max messages", 500
      go
      sp_configure "plan text pipe active", 1
      go
      sp_configure "plan text pipe max messages", 100
      go
      sp_configure "statement pipe active", 1
      go
      sp_configure "statement pipe max messages", 500
      go
      sp_configure "errorlog pipe active", 1
      go
      sp_configure "errorlog pipe max messages", 100
      go
      sp_configure "deadlock pipe active", 1
      go
      sp_configure "deadlock pipe max messages", 100
      go
      sp_configure "wait event timing", 1
      go
      sp_configure "process wait events", 1
      go
      sp_configure "object lockwait timing", 1
      go
      sp_configure "SQL batch capture", 1
      go
      sp_configure "statement statistics active", 1
      go
      sp_configure "per object statistics active", 1
      go
      sp_configure "enable stmt cache monitoring", 1
      go
      sp_configure "max SQL text monitored", 4096
      go
      set mon_stateful_history off
      go
      
    6. Set the following static parameter to a higher value (the setting is in bytes per user connection) if you are expecting a lot of (or long) SQL batches:

      sp_configure "max SQL text monitored", 2048
      go
      

    Note:

    Enabling the following configuration parameters will result in >5% performance overhead:
    sp_configure "sql text pipe active", 1
    sp_configure "sql text pipe max messages", 500
    sp_configure "max SQL text monitored", 2048
    sp_configure "plan text pipe active", 1
    sp_configure "plan text pipe max messages", 100
    sp_configure "statement pipe active", 1
    sp_configure "statement pipe max messages", 500
    sp_configure "statement statistics active", 1
    sp_configure "per object statistics active", 1
    sp_configure "enable stmt cache monitoring", 1
    sp_configure "max SQL text monitored", 4096 
    set mon_stateful_history off
    
  • As part of JDBC URL, either IP Address or host name can be provided. Ensure that the host name can be resolved consistently on the network. Standard TCP tools such as "nslookup" and "traceroute" can be used to verify the host name. Validate using the following commands on Management Agent where plug-in is deployed:

    • nslookup <hostname>

      This returns the IP address and fully qualified host name.

    • nslookup <IP>

      This returns the IP address and fully qualified host name.

  • The plug-in may sometimes depend on the cache size of the TempDB.

  • If the monitoring user does not have permission on all databases in Sybase ASE target, provide permission to query SYSSEGMENTS table to monitoring user or else create guest user account in each database.

  • To enable the use of Jobs for Sybase ASE the following settings are required:

    1. The plug-in for Sybase ASE must be deployed as a local configuration. Local configuration is when the Oracle Management Agent with the plug-in installed resides on the host of the Sybase ASE Server.

    2. Set the Sybase Adaptive Server Enterprise Preferred Credentials for both "Admin Sybase ASE Credentials" and "Agent Host Credentials."

    3. Set the following Sybase environmental variables:

      • STARTSERVER - Must equal the full path to the Sybase startserver executable. For example:

        /apps/sybase/ASE-15_0/install/startserver
        
      • RUNFILE - Must equal to the full patch of the Sybase runfile executable. For example:

        /apps/sybase/ASE-15_0/install/RUN_SYBASE_SERVER
        

6 Configuring Sybase Adaptive Server for Monitoring

To monitor the Sybase Adaptive Server target using Enterprise Manager, the Sybase Adaptive Server user must have the role mon_role. In addition to mon_role permissions, the monitoring user must also have Select permissions to access the following sys tables:

  • syslisteners

  • sysloginroles

  • syssrvroles

The following commands will grant Select permission to the monitoring user:

grant select on syslisteners to public
go
grant select on sysloginroles to public
go
grant select on syssrvroles (name, srid) to public
go

The above steps will give Select permission to all existing users in the database. To grant Select permission to only the monitoring user, referred to as monuser below, run the following commands. To execute these commands, the user must have sa_role permissions.

  1. Create a group.

    sp_addgroup OracleEMGroup
    go
    
  2. Add the user monuser to the group.

    sp_adduser monuser, null, OracleEMGroup
    go
    
  3. Grant Select permission on the tables to OracleEMGroup.

    grant select on syslisteners to OracleEMGroup
    go
    grant select on sysloginroles to OracleEMGroup
    go
    grant select on syssrvroles (name, srid) to OracleEMGroup
    go
    

7 Configure the Management Agent to Deploy the Plug-In

To configure the Agent, you must first ensure that the user starting the Agent service belongs to the Local Administrators Group. Also, you must set the preferred credentials on all Agents where you want to deploy the plug-in. To do so, follow the instructions given in the following sections.

7.1 Assigning Advanced Privileges to User

(For Microsoft Windows ONLY) To assign advanced privileges in a Microsoft Windows environment, do the following:

  1. Locally on the Microsoft Windows node hosting the Agent, check that the user starting the Agent service belongs to the Local Administrators Group. If not, add it.

  2. Open the Local Security Settings Windows Tool and give the following Advanced Privileges to the user starting the Agent service:

    • Act as part of the operating system

    • Adjust memory quotas for a process

    • Logon as batch job

    • Replace a process level token

  3. Restart the Agent service if it is running.

  4. Set the Preferred Credentials for the Host and the Agent in Cloud Control. For more information, see Setting up the JDBC Driver.

    • The OS user set in the Preferred Credentials must belong to the Local Administrators Group.

    • This OS user must have the following Advanced Privileges:

      • Act as part of the operating system

      • Adjust memory quotas for a process

      • Logon as batch job

      • Replace a process level token

7.2 Setting and Validating Preferred Credentials

To set the preferred credentials on all Agents where you want to deploy the plug-in, do the following:

  1. In Enterprise Manager Cloud Control, from the Setup menu, select Security, then Preferred Credentials.

    The Preferred Credentials page appears, showing a table of targets.

  2. Select Host target type from the table and then click Managed Preferred Credentials.

    The Host Preferred Credentials page appears.

  3. In the Host Preferred Credentials page, in the Target Credentials section, select the host that is running the Management Agent where the plug-in has to be deployed, and click Set.

  4. In the Select Named Credential dialog box, Select Credential as New and specify the user name and password and click Test and Save. If your test runs successfully, your credentials are set correctly.

  5. Run the OS Command job for the Management Agent where the plug-in has to be deployed.

    • Log in to Enterprise Manager Cloud Control.

    • From the Enterprise menu, select Job and then Activity.

    • In the Job Activity page, from the Create Job list, select OS Command, and click Go.

    • Fill up the details required in the following pages, and click Submit to run the job. If the job runs successfully, your credentials are set correctly.

8 Deploying the Plug-in

See the Plug-in Manager chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for steps to deploy the plug-in:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm

9 Setting up the JDBC Driver

Following are the steps to set up jConnect for the Sybase Adaptive Server plugin:

  1. Download the jConnect JDBC driver version 6.0 from http://www.sybase.com.

  2. Download the jconn3.jar file from SAP's website (http://support.sap.com/software.html):

    1. Click the Files for your Databases icon/link.

    2. Click the SAP Adaptive Server Enterprise link from the list of file types.

      If prompted, log in with your S-User ID (SAP Service Marketplace Username and Password).

    3. Click Database Patches.

    4. Click the SAP ASE FOR BUSINESS SUITE link.

    5. Under SAP ASE FOR BUSINESS SUIT click SAP ASE 16 DBCLIENT BUS.SUITE.

    6. Select the appropriate platform for where the driver will be placed.

    7. Check the box for download and click Add to Download Basket.

      If prompted, provide SAP Service Marketplace username and password.

    8. Click the Download Basket link to view all of your selected downloads.

    9. Click the ASEBC1600002 Description link to access the download of the DB Client.

      If prompted, provide SAP Service Marketplace username and password.

    10. Save the file to your local storage.

    11. Extract the downloaded .SAR file with SAP's sapcar.exe extraction utility. This must be done on a Windows host.

    12. After extracting the .SAR file, the jconn3.jar should be located in the sybjdbc\jconn3.jar directory.

  3. If it does not already exist, create a $ORACLE_HOME/plugins/dependencies/oracle.em.ssad/jdbcdriver/ directory.

  4. Copy the JDBC driver file (jConn3.jar) into the $ORACLE_HOME/plugins/dependencies/oracle.em.ssad/jdbcdriver/ directory.

Note:

For Linux and UNIX systems, the name of the JDBC driver is case sensitive and must match the jconn3.jar filename.

10 TCP/IP Port Information

The following sections provide information you require to enable the TCP/IP port and to find the TCP/IP port for a particular Sybase Adaptive Server instance.

10.1 Enabling TCP/IP Port

For all editions of Sybase Adaptive Server

  1. From the Sybase Adaptive Server Configuration Manager, select Sybase Adaptive Server Network Configuration in the left panel and navigate to the Sybase Adaptive Server instance.

    The right panel displays all protocols for the specified Sybase Adaptive Server instance and their status.

  2. Ensure that TCP/IP is enabled.

  3. (If TCP/IP is disabled), right-click TCP/IP and select Properties. The TCP/IP Properties dialog box appears.

  4. In the Protocol tab, select enabled, and click Apply.

  5. Restart the Sybase Adaptive Server instance.

10.2 Finding TCP/IP Port

To find the TCP/IP port number for a particular Sybase Adaptive Server instance, run the following query:

Select address_info from syslisteners 

The above query returns the host address followed by the port number.

11 Adding Instances for Monitoring

After successfully deploying the plug-in, follow these steps to add the plug-in target to Cloud Control for central monitoring and management:

  1. From the Setup menu, select Add Target and then Add Targets Manually as shown in Figure 5:

    Figure 5 Add Targets Manually Menu

    Surrounding text describes Figure 5 .
  2. In the Add Targets Manually page (Figure 6), select Add Targets Declaratively by Specifying Target Monitoring Properties, select Target Type as Sybase Adaptive Server Enterprise, select a Monitoring Agent and click Add Manually.

    Figure 6 Add Targets Manually Page

    Surrounding text describes Figure 6 .
  3. In the Add Sybase Adaptive Server Enterprise page (Figure 7), provide the following information for the properties:

    • Target Name: Unique target name across all the Cloud Control targets, such as SybaseServer_Hostname. This is the display name in Cloud Control. It represents this Sybase Adaptive Server target across all user interfaces within Cloud Control.

    • Monitoring Sybase ASE Credentials

      • Sybase ASE User Name: Valid user for the database in mon_role.

      • Sybase ASE Password: Corresponding password for the database user.

      • Confirm Sybase ASE Password: Confirm password entry.

    • Sybase ASE Host Credentials

      • User Name: Operating System account for Sybase host. This account must also be the Sybase User.

      • Password: Corresponding password for the host user name.

      • Confirm Password: Confirm password entry.

    • Properties

      • JDBC Driver: Optional parameter. Provide this value in the following format:

        com.sybase.jdbc3.jdbc.SybDriver
        
      • JDBC URL: Provide the URL in the following format:

        jdbc:sybase:Tds:<hostname>:<port>
        

        For example:

        jdbc:sybase:Tds:stmpi2.idc.oracle.com:5000
        

        The JDBC URL argument represents a data source. Parameter definitions are as follows:

        jdbc:sybase: Indicates that the connection is to a Sybase ASE server.

        server: Fully qualified hostname or IP address of the database server.

        port: TCP/IP server port number assigned to the database server, which is an integer between 0 and 65535. The default port for Sybase ASE is 5000.

  4. Click Test Connection to make sure the parameters you entered are correct.

Figure 7 Add Sybase Adaptive Server Enterprise Page

Surrounding text describes Figure 7 .

After you deploy and configure the plug-in to monitor one or more targets in the environment, you can customize the monitoring settings of the plug-in. This alters the collection intervals and threshold settings of the metrics to meet the particular needs of your environment. If you decide to disable one or more metric collections, this could impact the reports that the metric is a part of.

12 Verifying and Validating the Plug-in

After waiting a few minutes for the plug-in to start collecting data, use the following steps to verify and validate that Enterprise Manager is properly monitoring the plug-in target:

  1. Click the Sybase Adaptive Server target link from the All Targets page. The Sybase ASE home page appears (Figure 8):

    Figure 8 Sybase ASE Home Page

    Surrounding text describes Figure 8 .
  2. Verify that no metric collection errors are reported by clicking Monitoring and then Metric Collection Errors from the Target menu.

  3. Ensure that reports can be seen and no errors are reported by clicking Information Publisher Reports in the Target menu and viewing reports for the Sybase ASE target type.

  4. Ensure that configuration data can be seen by clicking Configuration and then Last Collected in the Target menu. If configuration data does not immediately appear, click Refresh in the Latest Configuration page.

  5. Ensure that the Analysis page can be viewed by clicking Analysis in the Target menu. The Sybase ASE Analysis page appears (Figure 9):

    Figure 9 Sybase ASE Analysis Page

    Surrounding text describes Figure 9 .

13 Creating and Editing Jobs

To create and edit jobs, follow these steps:

  1. From the Enterprise menu, select Job, then click Activity.

  2. On the Job Activity page, select a job type from the Create Job menu and click Go. Select one of the following:

    • Startup Sybase ASE

      • Performs a Startup of the Sybase Adaptive Server Enterprise.

      • When Sybase ASE is shut down, the Startup job icon will be accessible in the Summary section of the Target Home page

      • Requires the STARTSERVER and the RUNFILE environmental variables to be set correctly on the Sybase ASE host.

    • Shutdown Sybase ASE

      • Performs a Shutdown of the Sybase Adaptive Server Enterprise.

      • When Sybase ASE is running, the Shutdown job icon will be accessible in the Summary section of the Target Home page.

      • Requires Admin Sybase ASE Credentials to be configured as a Preferred Credential.

    Note:

    All jobs available for the Sybase ASE plug-in are only available when the plug-in is set up for local monitoring of the database. Preferred Credentials are required to be set for use.
  3. In the General tab of the Create <Job Type> Job page, provide a name for the job and add the individual targets or one composite target such as a Group. If you are editing a job, then modify the job name and the selected targets.

  4. These jobs do not require and parameters to be set in the Parameters tab of the Create <Job Type> Job page.

  5. In the Credentials tab of the Create <Job Type> Job page, select an appropriate option for credentials.

    You can choose to use the preferred credentials that are already set or override the preferred credentials with new credentials. In either case, you need to provide the credentials for agent host and database host.

    To set the preferred credentials, click Preferences at the top-right corner of the Cloud Control console. From the left-vertical navigation bar, click Preferred Credentials. Cloud Control displays the Preferred Credentials page. On this page, you can set the preferred credentials.

  6. In the Schedule tab of the Create <Job Type> Job page, schedule the job.

  7. In the Access tab of the Create <Job Type> Job page, define or modify the access you want other users to have to this job.

  8. Click Submit to create the job.

Note:

To enable use of the Job Buttons found in the Summary section of the Target home page, be sure to set the Preferred Credentials for the Sybase Adaptive Server Enterprise target type.

14 Using the Sybase ASE Plug-in Reports

To further aid administrators with critical tasks such as problem diagnosis, trend analysis and capacity planning, the Sybase ASE Database Plug-in includes twenty-six out-of-box reports (Figure 10):

Figure 10 Information Publisher Reports

Surrounding text describes Figure 10 .

To generate a new report from one of the out-of-the-box reports provided by Oracle, follow these steps:

  1. From the Enterprise menu, select Reports, then Information Publisher Reports as shown in (Figure 11):

    Figure 11 Reports Menu

    Surrounding text describes Figure 11 .
  2. Choose Sybase Adaptive Server Enterprise from the Target Type list inside the Search menu and then click Go as shown in (Figure 12):

    Figure 12 Reports Search

    Surrounding text describes Figure 12 .
  3. After the reports have been sorted to Sybase ASE reports only, find the desired report and click on the report title hyperlink.

  4. In the Specify Target for Report page, click the magnify glass magnifying glass icon to find the specific Sybase ASE target you wish to create a report for.

  5. After selecting the target, click Continue to finish generating the report.

Table 1 shows the Information Publisher Reports provided by Oracle:

Table 1 Sybase ASE Information Publisher Reports

Report Name Report Description

Sybase ASE Engines Statistics

Displays Sybase ASE Engines related information.

Sybase ASE Configuration

Displays Sybase ASE Configuration Information.

License Pack Usage (Target)

Displays the License Pack Usage for a target.

Membership (Target)

Displays the list of aggregate targets where the specified target is a member.

20 Most Common Alerts (Target)

Displays 20 most common alerts for a target over the last 24 hours.

Alerts History (Target)

Displays alerts for a target over the last 24 hours.

Outstanding Alerts (Target)

Displays outstanding alerts for a target.

Availability History (System)

Displays availability history for a system over the last 24 hours.

Availability History (Target)

Displays availability history for a target over the last 24 hours.

Sybase ASE Data Cache Statistics

Displays Data Cache related information.

Sybase ASE Database Log Statistics

Displays Database log related information.

Sybase ASE Databases Space Statistics

Displays Databases Space related information.

Sybase ASE Device IO Statistics

Displays Device IO related information.

Sybase ASE Procedure Cache Statistics

Displays Procedure Cache related information.

Sybase ASE Deadlock Statistics

Displays the deadlock statistics for Sybase ASE.

Sybase ASE Error Statistics

Displays the error statistics for Sybase ASE.

Sybase ASE Open Objects Statistics

Displays the Open Objects Buffer and Page Read/Write statistics for Sybase ASE.

Sybase ASE Process Statistics

Displays the process statistics for Sybase ASE.

Sybase ASE SQL Statistics

Displays the SQL statistics for Sybase ASE.

Sybase ASE User Statistics

Displays the user statistics for Sybase ASE.

Sybase ASE Network IO Monitoring Report

Displays Network Monitoring Statistics Report.

Sybase ASE Performance Statistics

Displays Sybase ASE performance related information.

Sybase ASE Transaction Log Statistics

Displays Transaction log related information.

Sybase ASE Worker Threads Statistics

Displays Sybase ASE worker threads related information.

Target Status Diagnostics Report: Agent-based targets

This report summarizes status and availability transitions for agent-based targets and the monitoring agent(s).

Target Status Diagnostics Report: Repository-based targets

This report summarizes status and availability transitions for repository-based targets.


15 Undeploying the Plug-in

See the Plug-in Manager chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for steps to undeploy the plug-in:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm

16 Troubleshooting the Plug-In

If the following parameters are not enabled for the Sybase Adaptive Server plug-in, metric collection errors may occur:

sp_configure "sql text pipe active", 1
sp_configure "sql text pipe max messages", 500
sp_configure "max SQL text monitored", 2048
sp_configure "plan text pipe active", 1
sp_configure "plan text pipe max messages", 100
sp_configure "statement pipe active", 1
sp_configure "statement pipe max messages", 500
sp_configure "statement statistics active", 1
sp_configure "per object statistics active", 1
sp_configure "enable stmt cache monitoring", 1
sp_configure "max SQL text monitored", 4096 
set mon_stateful_history off

For information about the troubleshooting scenarios that you might encounter while working with the System Monitoring plug-ins, see the Oracle Enterprise Manager System Monitoring Plug-in Troubleshooting Guide:

http://docs.oracle.com/cd/E24628_01/em.121/e35212/toc.htm

17 Complete List of Plug-in Metrics

For a complete list of all the metrics contained in this plug-in, see the Oracle Enterprise Metric Guide:

http://docs.oracle.com/cd/E24628_01/em.121/e51915/toc.htm

18 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


System Monitoring Plug-in Installation Guide for Sybase Adaptive Server Enterprise (ASE), Release 12.1.0.3.0

E25214-05

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.