Getting started with Foglight for SAP ASE

Getting started with Foglight for SAP ASE

The Foglight Cartridge for SAP ASE release package contains the following:

1. Foglight Cartridge for SAP ASE 5.9.5.10
   • DB_Sybase-5_9_5_10.car
2. Product Documentation, including:
   • Foglight for SAP ASE 5.9.5.10 User and Reference Guide (PDF and online help)
   • Foglight for SAP ASE 5.9.5.10 Release Notes (this document)

Installation Instructions

Upgrade

SAP ASE cartridges former to 5.7.5.40 cannot be upgraded to the current SAP ASE cartridge version (5.9.5.10).

Workaround: You may install the new SAP ASE cartridge on the same FMS instance as the old cartridge. The new SAP ASE cartridge must use a different FglAM than the legacy cartridge, as well as a new SAP ASE user account.

History data

To maintain cartridge history, do not remove the legacy cartridge. For the same reasons as mentioned above, the history data in the legacy cartridge is not accessible from the new cartridge. Also, as mentioned in the workaround above, both legacy and new SAP ASE cartridges can be installed side by side. Hence legacy history will be available via the legacy cartridge.

Monitoring the SAP ASE instance

Same SAP ASE instance can be monitored by both Legacy SAP ASE agent and new SAP ASE agent (5.9.5.10), if unique FglAM and unique SAP ASE user account are used for each account.

ASP enhancements

• Changes in agent startup parameter (ASP) values no longer require the agent to be deactivated and reactivated for the change to take effect.
• Changes in agent startup parameter (ASP) values such that frequency and max rows are defined on a per-collection basis. Edit the Collection Details list to define the frequency and max rows of each collection.

Sybase open client

SAP ASE cartridge 5.9.5.10 does not require Sybase Open Client to be installed.

Installation

After installing the cartridge, update the SAP ASE account for Foglight by manually downloading and running the scripts DB_Sybase_FirstRun_Scripts located under Foglight > Dashboards > Administration > Agents > Cartridges > Components for Download.

1. Run script rapsAdmin.sql as sa user. This script creates only two helper stored procedures: 
   • sp_fgl_addgrant and sp_fgl_adduser
   • isql -Usa -Ppassword -SserverName -i rapsAdmin.sql -o rapsAdmin.out
2. Run these scripts to complete the upgrade and to display the correct information on the new dashboards. For script execution instructions, see "Configuring Sybase Login Privileges" in the Foglight for Sybase User and Reference Guide. Failed to upgrade the user account will result in broken agent instances.
3. Once you have installed the cartridge, deploy the agent package. For complete information, see "Deploying agent packages to monitored hosts" in the Foglight Administration and Configuration Help. After upgrading the cartridge and starting the agent, the Agent log will display the database version, cartridge version, EBF level, and so on.
   • When you start using a new SAP ASE user or when the SAP ASE cartridge is upgraded with a new version, the stored procedures will be automatically reinstalled.
   • For RS cartridge you need to configure the path to the sql.ini file in the ASP with all the servers participating in the RS Agent. You can take the sql.ini file which exists in the Replication Server as an example.
   • When creating a new agent, it is recommended to clone all the default lists to new lists which will be used only for this agent – in the same way you did with the legacy cartridge.

Post Installation Instructions for 5.9.5.10

After installing the Cartridge for SAP ASE, perform the configuration steps below:

To create a new SAP ASE user, run the following scripts as sa user (use your username and password).

exec sp_addlogin 'username' , 'password' , sybsystemprocs
exec sp_fgl_adduser 'username' , 'foglightGroup'

Grant mon_role to 'username'

    Note: The new user should have only one role: mon_role.

Viewing the Cartridge for SAP ASE:

On the navigation panel, under Dashboards, click Administration > Cartridges > Cartridge Inventory. For details specific to the installation of the cartridge agents, see the following sections.

Sybase Adaptive Server Prerequisites: Sybase_MDA Agent

Install Sybase_MDA

The first pre-requisite is that the Sybase_MDA feature be installed on the respective ASE. This feature is not automatically installed on all versions of Sybase ASE. A check the DBA can run is the query: “select * from master..monState”.

If the monitoring tables are not installed in your Adaptive Server (12.5.4 or later), have the Sybase DBA for the respective ASE follow the steps to install the tables listed in the Addendum at the end of this section.

For versions 15.x, there is no need for loopback and installmontables.

Configure Sybase_MDA

The Sybase_MDA feature has numerous parameters to both turn on and turn off specific metrics and determine the amount of memory the ASE will set aside for these metrics.

Performance monitoring how has the ability to enable the user to set the per_object_statistics flag to off.

Configure ports

Callback collections require communication between the Foglight Management Server and the Sybase server.  Ensure that the port used by the Sybase host server is open between the Sybase host and the Foglight Management Server.

Sybase 'mon_role' assigned

The Sybase login defined in the Foglight agent property for the respective agent must have the “mon_role” assigned. This is also applicable to the ‘sa’ login.

Command to execute via ISQL or other client tool:

grant role mon_roleto_<logon_name>

Sybase Adaptive Server Pre-requisites: Sybase_RS Agent

The Sybase_RS agent requires separate common logins to be created for the Replication Server, the RSSD data server, the Primary data server, and the Replicate data server.

• Replication Server - Create a user with no special permission for each Replication Server being monitored.
• RSSD data server - Create a login for RSSD data server. Create a user with the same login name for the RSSD database. This user should be a member of the rs_systabgroup.
• Primary data server - Create a login with the replication_role in each Primary data server.  Create a user with the same login name for the Primary database.
• Replicate data server - Create a login in each Replicate data server.  Create a user with the same login name for the Replicate database. This user should have select permission for the rs_lastcommit table.

Note: Refer to the Sybase_RS "Setting Connection Details" topic in the Managing Sybase Database Systems online help for more information.

Addendum

Preparation of the ASE version 12.5.4 or later for Foglight Cartridge for SAP ASE 5.9.5.10

Install MDA

If the monitoring tables are not installed in your Adaptive Server (12.5.4 or subsequent release), have the Sybase DBA for the respective ASE follow these steps to install the tables.

First, a server named “loopback” must be included in sysservers before installing the scripts for the MDA tables. Proxy tables for the monitoring tables are not created by default when you configure Adaptive Server. The tables are created in the second step using the installmontables script that is included in the Adaptive Server install (located in the $SYBASE/ASE-12_5/scripts directory).

1. Create a loopback server entry in ISQL:
   1. Logon to Ada.
   2. Execute:

      sp_addserver 'loopback', null, <ASE server name> go

2. Execute the installmontables script located in the $SYBASE/ASE-12_5/scripts directory (%SYBASE%/ASE-12_5/scripts for Windows) using ISQL:

   isql –Usa –P<sa password> -S<server name> -n –i%SYBASE%/%SYBASE_ASE%/scripts/installmontables

Adaptive Server Enterprise configuration parameters

Sybase_MDA agent requires the following configuration for it to run correctly and gather the specified data for the Foglight Management Server.
The values shown for the following parameters are the minimum required values that the Foglight Cartridge for SAP ASE 5.9.3.10 needs for proper data collection and reporting. Any of these parameter values could be increased if necessary. (You can copy, paste, and execute the following script into an ISQL or other client session.)

sp_configure "statement cache size" <size_of_cache>
go
sp_configure "errorlog pipe max messages",1000
go
sp_configure "max SQL text monitored",256
go
sp_configure "sql text pipe max messages",3000
go
sp_configure "statement pipe max messages",3000
go
-- Flags
sp_configure "enable stmt cache monitoring" , 1
go
sp_configure "enable literal autoparam" [0|1]
go
sp_configure "enable monitoring", 1
go
sp_configure "sql text pipe active", 1
go
sp_configure "errorlog pipe active", 1
go
sp_configure "per object statistics active",1
go
sp_configure "statement statistics active",1
go
sp_configure "statement pipe active",1
go
sp_configure "wait event timing",1
go
sp_configure "SQL batch capture",1
go
sp_configure "process wait events",1
go

The following tables list proprietary Sybase flags and the Sybase_MDA agent tables dependent upon them. If any of the settings do not have values that fall in the recommended value range, data collection will issue complaints and fail to successfully collect; indicating that some MDA table collection was canceled as a result of the flags being set incorrectly. To prevent these alerts from occurring, use the appropriate Data Management properties to disable the collection that is failing to collect. Below is a listing of Sybase_MDA agent tables and the configuration settings they depend on:

Additional resources

Additional information is available from the following:

• Online product documentation (http://documents.quest.com/ProductsAZ.aspx#F)
• Foglight Community https://www.quest.com/community/products/foglight/

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe.

This release has the following known capabilities or limitations: The server will be enabled for Global Operation, but not localized to any particular locale.

Back to Top

About Us

About Us

We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.

Our brand, our vision. Together.

Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.

Contacting Quest

For sales or other inquiries, visit https://www.quest.com/company/contact-us.aspx/.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

• Submit and manage a Service Request.
• View Knowledge Base articles.
• Sign up for product notifications.
• Download software and technical documentation.
• View how-to-videos.
• Engage in community discussions.
• Chat with support engineers online.
• View services to assist you with your product.

Back to Top

Copyright© 2020 Quest Software Inc.

Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.

Back to Top