Skip Headers
Oracle® Enterprise Manager System Monitoring Plug-in Installation Guide for Sybase Adaptive Server Enterprise (ASE)
Release 12.1.0.2.0

E25214-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

  PDF · Mobi · ePub

Oracle® Enterprise Manager

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

Release 12.1.0.2.0

E25214-04

September 2012

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.

Description

The System Monitoring Plug-in for Sybase Adaptive Server Enterprise extends Oracle Enterprise Manager Cloud Control 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:

Versions Supported

This plug-in supports the following versions of products:

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.

Prerequisites

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

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:

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
    

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.

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

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.

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

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 www.sybase.com.

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

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

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.

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.

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.

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.

  2. In the Add Targets Manually page, select Add Non-Host Targets by Specifying Target Monitoring Properties, select Target Type as Sybase Adaptive Server Enterprise, select a Monitoring Agent and click Add Manually.

  3. In the Add Sybase Adaptive Server page (Figure 1), 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.

    • JDBC URL — Provide the URL in the format jdbc:sybase:Tds:<system>:<tcp/ip port>

      For example, jdbc:sybase:Tds:stmpi2.idc.oracle.com:5000

    • JDBC Driver — Optional parameter. Provide this value in the format com.sybase.jdbc3.jdbc.SybDriver

    • Database Username — Valid user for the database in mon_role.

    • Database Password — Corresponding password for the database user

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

Figure 1 Add Sybase Adaptive Server Enterprise Plug-in Page

Surrounding text describes Figure 1 .

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.

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 Adaptive Server home page appears.

    The Sybase Adaptive Server home page appears.

  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.

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

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", 100
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", 100
sp_configure "statement statistics active", 1
sp_configure "per object statistics active", 1

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

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.2.0

E25214-04

Copyright © 2012, 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.