The following is a list of issues addressed and enhancements implemented in this release.
Defect ID |
Resolved Issue or enhancement |
SYFOG-13 | The stored procedure installation script detected the Sybase version using the Emergency Bug Fix (EBF) number instead of the Sybase Service Pack. This resulted in stored procedures for some versions of Sybase not compiling correctly, yielding empty dashboards. |
SYFOG-14 | The User Blocked stored procedure was not functioning correctly. |
SYFOG-15 | The Sybase_RS Agent dashboards were not correctly displaying device usage data from the Sybase_MDA Agent . |
SYFOG-16 | Error information specific to the Sybase database version was being incorrectly displayed. |
SYFOG-17 | After clearing user block information, the information was also cleared from the 1 hour viewing period. |
SYFOG-18 | The default value for DatabaseErrorLogDetails was changed to <what?> |
n/a | Changes in agent startup parameter (ASP) values no longer require the agent to be deactivated and reactived for the change to take effect. |
n/a | 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. |
n/a | The Sybase Open Client is no longer required. |
The following is a list of issues known to exist at the time of this release.
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:
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. |
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. |
PR-070055 |
The Cache_Efficiency Rule does not have a property named dcache_name. |
PR-070038 |
The view list includes an extra database name in some of the views. |
SDB-414 |
Excluding databases can only be done by populating the Exclude DBs list manually in the Sybase_MDA agent properties. |
Defect ID |
Known Issue |
N/A |
Roles mechanism. To view the new Sybase dashboards, a user must have the minimum privileges of:
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. |
Defect ID |
Known Issue |
n/a |
Due to architectural changes in the Cartridge for Sybase 5.7.5.40, legacy cartridge versions cannot be upgraded to version 5.7.5.40. 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. |
Review the information below prior to installing the Cartridge for Sybase.
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
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
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.
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.
For the Foglight Cartridge for Sybase 5.7.5.40 to operate properly, the Foglight Management Server must be running 5.7.5. The Foglight Agent Manager (FglAM) must be version 5.7.0.
Recommended Sybase Configuration
The values below are minimum requirements for the given paramters:
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 |
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, |
Yes |
No |
Windows 2003 64-bit |
12.5.3 to 15.2, |
No |
Yes |
Windows 2008 |
12.5.3 to 15.2, |
Yes |
Yes |
Windows 2008 R2 64-bit |
Not supported |
No |
Yes |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center