立即与支持人员聊天
与支持团队交流

Foglight for Sybase 5.7.5.50 - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

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

 


Known issues

Known issues

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

Sybase_RS Agent

Defect ID

Known Issue

CR-0231424

The RS_ConnectionStatus rule does not trigger an alarm, even when the rule conditions are met.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

CR-0230497

Latency and Synchronizing Servers. Invalid latency values reported in the RS_Latency table.

Workaround: In order to report accurate latency values, all Replication Servers, Primary, and Replicate data servers within an ID server domain must be synchronized. 

CR-0230496

The RS_PartitionStatus rule does not auto clear after the partition is reset from Offline to Online.

Workaround: This rule event must be manually cleared because we do not report partition online statuses which could possibly result in a data overload within the Foglight database.

CR-0168297

Memory leak on Windows platform.

Workaround: This is a Sybase Open Client API issue and a case is currently open with Sybase.

CR-0130361

The Sybase_RS agent does not launch on AIX 5.2.

Workaround: Since the Sybase_RS agent has the ability to perform most of its monitoring remotely, implement the following workaround:

  1. Choose another server which has the Sybase software (either ASE or Replication Server) installed.
  2. Set up the interfaces file so it has the Sybase Replication Server entry and entries for all of the other associated Sybase Servers (RSSD server, Primary Data Server, Replicate Data Server etc.) being monitored.
  3. Configure an instance of the Sybase_RS agent on this server (the server selected in step 1) to monitor the Replication Server running on the AIX 5.2 server.

Note: Since the Sybase_RS agent is monitoring the Sybase replication server remotely, the tables related to the replication server error log (RS_ErrorlogDetail and RS_ErrorlogSummary) do not post any data.

PR-069037

Some of the graphical views display incorrect view legends.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

PR-068923

The '/n' character appears in the RS_ErrorLogMsg rule message.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

PR-068260

Unusual table names appear in the Data Browser view for the Sybase_RS agent. The RS_ThreadSummary and RS_PartitionSpaceUsedTrend table names should be listed as the table name followed by the identity columns. Only their identity columns appear in the table’s hierarchy. For example, the RS_PartitionSpaceUsedTrend table should be listed as: RS_PartitionSpaceUsedTrend /apps/sybase/sybase1253/data/sq2 104 sq2 /apps/sybase/. Instead, this table is listed as:/apps/sybase/sybase1253/data/sq2 104 sq2 /apps/sybase/.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

PR-063860

The agent properties do not display the Agent/DCM versions after the agent starts successfully.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

PR-063489

The RS_Latency table does not display a negative value properly.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

PR-036588

The RS_Latency_Graph view has an incomplete view label.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

SDB-353

SDB-352

On the Databases dashboard, the Up Since and Workload Info columns are not populated for Sybase_RS agent entries. That is because the Sybase_RS agent is not a database monitoring agent. This is expected behavior.

Sybase_MDA Agent

Defect ID

Known Issue

CR-0231209

Received exception: position beyond end of string from BenchMarkTimes.

Workaround: There is currently no workaround for this issue.

CR-0231189

UsersBlocking view shows incorrect data.

Workaround: There is currently no workaround for this issue.

CR-0231131

Data for UsersBlocked view gets displayed in UsersBlocking view.

Workaround: There is currently no workaround for this issue.

CR-0230878

The SYBM_ASE_Availability view does not show the name of the Sybase server.

Workaround: There is currently no workaround for this issue.

CR-0230847

The Agent Version and Stored Procedures Version fields are blank.

Workaround: There is currently no workaround for this issue.

CR-0230645

The agent parameter Exclusion list name is not the same as in Foglight 4.

Workaround: There is currently no workaround for this issue.

CR-0230598

The Sybase_MDA agent does not work on Windows. The agent has trouble automatically running the rapsinstall2*.sql scripts under Foglight 5 due to the use of a relative directory path name.

Workaround: To work around this, manually run rapsinstall2.sql for any monitored ASE and then manually run rapsinstall2_ase15.sql for any ASE of version 15.X. This is applicable to Windows 2000 and Windows 2003 only.

For example, to manually run rapsinstall2.sql:

c:

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

If the ASE of interest is version 15.X, also do this:

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

CR-0230499

The RS_Latency_Graph view has an incomplete view label.

Workaround: Expected Sybase behavior.

CR-0203573

There are an excessive number of messages in the Foglight Management Server log. If the Sybase_MDA agent attempts to collect from a database where the user does not have a login or permission to access the data, then an error message will be written to the client log file with details on how to resolve the issue. If the agent continues running without the user permission level being modified, this results in several messages being written to the client FMS log file each collection cycle.

Workaround: There is currently no workaround for this issue. It will be fixed in a future server release.

CR-0147037

The EngineSummary Table shows intermittent negative values for cpu_busy_pct.

Workaround: There is currently no workaround for this issue.

PR-070213

Two similar views, SYBM_DbSpaceTrendBar and YBM_DiskSpaceTrendBar, do not show data.
Workaround: There is currently no workaround for this issue. It will be fixed in a future release.

PR-070055

The Cache_Efficiency Rule does not have a property named dcache_name.
Workaround: There is currently no workaround for this issue. It will be fixed in a future release.

PR-070038

The view list includes an extra database name in some of the views.
Workaround: There is currently no workaround for this issue. It will be fixed in a future release.

SDB-414

Excluding databases can only be done by populating the Exclude DBs list manually in the Sybase_MDA agent properties.
Workaround: There is currently no workaround for this issue.

Sybase Dashboards

Defect ID

Known Issue

N/A

Roles mechanism. To view the new Sybase dashboards, a user must have the minimum privileges of:

  • Foglight Operator

  • Sybase Administrator

To activate or deactivate agents from the Sybase dashboards, the user must have Foglight administrator privileges.

Workaround: There is currently no workaround for this issue. It will be fixed in a future release.

N/A

On the Top Activity dashboard, SQL Details tab, long SQL statements are displayed across multiple table rows.

Workaround: There is currently no workaround for this issue. It will be fixed in a future release.

N/A

When creating a new agent, the Server Configuration collection and Space Trending collection are updated only after one hour (until then, data is not available).

Workaround: There is currently no workaround for this issue. It will be fixed in a future release.

SDB-407 Sybase reports are only be accessible by those Foglight users whose accounts include the Sybase Admin role.

Upgrade

Defect ID

Known Issue

n/a

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. 

Workaround: You may install the new Sybase cartridge on the same FMS instance as the old cartridge.  The new Sybase cartridge must use a different FglAM than the legacy cartridge. Both FglAMs may be installed on the same FMS.

 


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.

System requirements

System requirements

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

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:

Value Requirement
sp_configure 'number of locks' 50000
sp_configure 'number of open objects' 2500
sp_configure 'number of open indexes' 1500
sp_configure 'number of open partitions' 1000
sp_configure 'permission cache entries' 50

Supported platforms

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

Operating System

Replication Server

Primary Adaptive Server

ASE 12.5.1 through 15.5

32-Bit

64-Bit

AIX 5.2

Not supported

Yes

Yes

AIX 5.3, 6.1

12.1, 12.5, 12.6, 15.0 to 15.2

Yes

Yes

HP-UX 11.11.11

12.1, 12.5, 12.6, 15.0 to 15.1

Yes

Yes

Linux Red Hat with kernel level 2.4

12.1, 12.5, 12.6, 15.0 to 15.2

Yes

No

Linux Red Hat with kernel level 2.6

12.1, 12.5, 12.6, 15.0 to 15.2

Yes

Yes

Solaris 2.10 on Intel/X86

Not supported

No

No

Oracle Solaris 2.8, 2.9, 2.10

12.1, 12.5, 12.6, 15.0 to 15.2

Yes

Yes

Windows 2000 SP4 and Windows 2003

12.5.3 to 15.2,
15.0.3 supported only for ASE 15.0.3 EBF16550 ESD#1

Yes

No

Windows 2003 64-bit

12.5.3 to 15.2,
15.0.3 supported only for ASE 15.0.3 EBF16550 ESD#1

No

Yes

Windows 2008

12.5.3 to 15.2,
15.0.2/EBF 15963 ESD#5, and
15.0.2/EBF 15963 ESD#6

Yes

Yes

Windows 2008 R2 64-bit

Not supported

No

Yes

 


相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级