The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
|
SDB-839 |
Allow support in encryption database mode, the DB agent now supports Sybase when Encryption is enabled on the database. |
|
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. |
|
SYFOG-35 |
Add charset field in ASP, so connection from the DB agent to the database can take place if special charset (as Chinese) is needed. |
|
SYFOG-36 |
Added seconds to milliseconds measurement to the Sybase Benchmark times collection. |
|
SYFOG-39 |
Sybase_RS agent can now perform in Linux environment, and reads interfaces file. |
|
SYFOG-40 |
UserBlocked collection sometimes fails after instance stop/start. |
|
SYFOG-41 |
The agent falls back to IP if the hostname it connects to fails to respond. |
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 SAP ASE 5.9.3.10, legacy cartridge versions cannot be upgraded to version 5.9.3.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. Both FglAMs may be installed on the same FMS. |
Before installing Foglight for SAP ASE, ensure your system meets the following minimum hardware and software requirements:
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 SAP ASE, 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 SAP ASE 5.9.3.10 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 SAP ASE 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 |
Version 5.9.3.10 allows remote monitoring, hence Supported Platforms are the same as the FglAM supported platform list. Refer to the Foglight System Requirements and Platform Support Guide for the supported platforms.
Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.
Foglight for SAP ASE is covered by the base Foglight license that allows cartridges to be installed.
To activate a trial or a purchased commercial license:
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center
