What are the known issues for the SAP ASE (Sybase) cartridge?
Sybase_RS Agent related known issues
|
Issue ID
|
Known issue
| ||||||
|
SYFOG-100 |
Monitor the Sybase Backup Server log file for MDA and RS agents is supported with a local Foglight Agent Manager. Workaround: There is currently no workaround for this issue. For more information refer to KB 4308470. | ||||||
|
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.
| ||||||
|
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-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-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-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. | ||||||
|
PR-063489 |
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. | ||||||
|
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-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-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-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. | ||||||
|
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 an expected behavior. |
Sybase_MDA Agent related known issues
|
Issue ID
|
Known issue
|
|
SYFOG-100 |
Monitor the Sybase Backup Server log file for MDA and RS agents is supported with a local Foglight Agent Manager. Workaround: There is currently no workaround for this issue. For more information refer to the KB. |
|
CR-0147037 |
The EngineSummary Table shows intermittent negative values for cpu_busy_pct. Workaround: There is currently no workaround for this issue. |
|
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-0230499 |
The RS_Latency_Graph view has an incomplete view label. Workaround: Expected Sybase behavior. |
|
CR-0230847 |
The Agent Version and Stored Procedures Version fields are blank. 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-0231131 |
Data for UsersBlocked view gets displayed in UsersBlocking view. 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-0231209 |
Received exception: position beyond end of string from BenchMarkTimes. Workaround: There is currently no workaround for this issue. |
|
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. |
|
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-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. |
|
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 Dashboard related known issues
|
Issue ID
|
Known issue
| ||||||||||||||||||||||
|
FOM-978 |
Some collection data might not be displayed in the following dashboards when monitoring SAP ASE 15.7.
| ||||||||||||||||||||||
|
SYFOG-123 |
Lots of data are not synchronized in the FMS Federator. NOTE: SAP ASE cartridge does not support Federation.
| ||||||||||||||||||||||
|
SDB-407 |
Sybase reports are only be accessible by those Foglight users whose accounts include the Sybase Admin role. | ||||||||||||||||||||||
|
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. |