Resolved issues and enhancements

Resolved issues and enhancements

This 5.7.5.50 release of Foglight for Sybase does not include any resolved issues.

Back to Top

Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Sybase_RS Agent

Sybase_MDA Agent

c:\>cd Program files\Quest Software\Foglight
c:\> Program files\Quest Software\Foglight> cd config\Sybase\scripts...> isql -Usa -P<Password> -S<SERVERNAME>
-i .\rapsinstall2.sql -o rapsinstall2_out.txt

...> isql -Usa -P<Password> -S<SERVERNAME> -i .\rapsinstall2_ase15.sql -o rapsinstall2_ase15_out.txt

Sybase Dashboards

Upgrade

Back to Top

Installation and compatibility

Installation and compatibility

Review the information below prior to installing the Cartridge for Sybase.

• Due to architectural changes in the Cartridge for Sybase 5.7.5.50, legacy cartridge versions cannot be upgraded to version 5.7.5.50.  This means that the history in the legacy cartridge is not accessible from the new cartridge.
  • You may install the new cartridge on the same FMS as the legacy cartridge, provided that each cartridge uses a different FglAM.
• The Cartridge for Sybase 5.7.5.50 requires Foglight Management Server version 5.7.5. If you upgrade the Foglight Management Server to version 5.5.8 or later, you must upgrade the Cartridge for Sybase to version 5.5.5 or later.
• To install the Cartridge for Sybase 5.7.5.50:
  • To maintain cartridge history, do not remove the legacy cartridge.
  • Install version 5.7.5.50 of the cartridge as you would a new Cartridge for Sybase, installing version 5.7.5.50 in addition to the existing cartridge version. Note that the new cartridge will need to be managed by a different FglAM than the legacy cartridge.
  • For detailed cartridge installation instructions, see "Installing Foglight cartridges" in the Foglight Administration and Configuration Help.
• After installing the cartridge, update the Sybase account for Foglight by running manually the scripts located in the Foglight Agent Manager installation directory, under /agents/SybaseCartridge/<version_number>/config/Sybase/scripts. 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.  Failure to upgrade the user account results in broken agent instances.
• Once you have upgraded 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 leve, etc.

2017-08-13 17:15:31.336 INFO    [FglAM:IncomingMessage[5]-111] com.quest.glue.core.agent.AgentInstance - Created agent
2017-08-13 17:15:31.336 VERBOSE [FglAM:IncomingMessage[5]-111] com.quest.glue.core.agent.AgentInstance - Starting data collection
2017-08-13 17:15:31.336 INFO    [FglAM:IncomingMessage[5]-111] com.quest.qsi.fason.core.agent.AbstractAgent - Sybase 16 new2 entering startDataCollection()
2017-08-13 17:15:31.337 INFO    [FglAM:IncomingMessage[5]-111] com.quest.foglight.sybase.common.connection.SybaseConnectionPool - Successfully loaded Sybase driver com.sybase.jdbc4.jdbc.SybDriver
2017-08-13 17:15:31.338 INFO    [FglAM:IncomingMessage[5]-111] com.quest.glue.core.agent.AgentInstance - Started data collection
2017-08-13 17:15:31.391 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.common.agent.SybaseCollectionsSharedData - DB connect availability was changed from null to true
2017-08-13 17:15:31.427 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.SybaseVersionInfoProcessor - Set DB version to 16.0
2017-08-13 17:15:31.427 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.SybaseVersionInfoProcessor - Set EBF to 22385
2017-08-13 17:15:31.428 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.SybaseVersionInfoProcessor - Set cluster to false
2017-08-13 17:15:31.428 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.SybaseVersionInfoProcessor - Full version - Adaptive Server Enterprise/16.0/EBF 22385 SMP/P/X64/Windows Server/asecepheus/3530/64-bit/FBO/Sun Feb 16 06:52:50 2014
2017-08-13 17:15:31.441 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.GetVersionProcessor - DB Version 16000000
2017-08-13 17:15:31.460 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.SybaseQuestDBInfoProcessor - Use quest DB true
2017-08-13 17:15:31.516 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.StoreProceduresVersionInfoProcessor - The agent stored procedures detected in the monitored DB belong to version= 5.7.5.92.
2017-08-13 17:15:31.545 INFO    [Sybase 16 new2-highPriorityPool-1] com.quest.foglight.sybase.mda.collection.processor.startup.InitServerIsLocalProcessor - Set local server to false

• When you start using a new Sybase user or when the Sybase cartridge is upgraded with a new version, there is the automatic reinstall of the stored procedures. If there is a problem to install the stored procedures the relevant script block with the error is written to the Agent log – send the log file to support. An example of an error in the log:

2017-08-02 13:45:45.871 ERROR [FRT21_1503_42-lowPriorityPool-3-[SybaseServerStatus][2017/08/02 13:45:43]] com.quest.foglight.sybase.mda.collection.processor.startup.InstallSpProcessor - Error while running SP script
if exists (select 1
from sysobjects
where sysstat & 7 = 4 and uid = user_id()
and name = 'sp_fgl_version')
begin

• To use more than one agent (either with the legacy Sybase cartridge or with the new Sybase cartridge) on the same Sybase database, you must use and configure different Sybase user for each agent. Refer to Installation Instructions for information on creating a new user.
• The history you have from the Agent of the legacy cartridge will not be shown in the Agent of the upgraded cartridge.
• For RS cartridge you need to configure in the ASP the path to the sql.ini file with all the servers participating in the RS Agent. You can use the sql.ini file which exists in the Replication Server as an example.
• When you create 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.

Back to Top

System requirements

System requirements

Before installing Foglight for Sybase, ensure your system meets the following minimum hardware and software requirements:

• System requirements
• Hardware requirements
• Software requirements
• Supported platforms

The Foglight Cartridge for Sybase must be installed onto an already running Foglight Management Server, and requires that the Foglight Agent Manager be installed on all the hosts that you want to monitor.

To learn about the system requirements for these components, refer to the Foglight Release Notes and Foglight System Requirements and Platform Support Guide.

Hardware requirements

For the hardware requirements of Foglight Cartridge for Sybase, refer to the Supported Platforms table.

For the Foglight Management Server hardware requirements, refer to the Foglight System Requirements and Platform Support Guide.

Software requirements

For the Foglight Cartridge for Sybase 5.7.5.50 to operate properly, the Foglight Management Server must be running from 5.7.5 to 5.9.2. The Foglight Agent Manager (FglAM) should be from 5.8.5 to 5.9.2.

Recommended Sybase Configuration

The values below are minimum requirements for the given parameters:

Supported platforms

Before installing Foglight Cartridge for Sybase, ensure your system meets the following minimum hardware and software requirements:

Back to Top