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. | |
Memory leak on Windows platform. Workaround: This is a Sybase Open Client API issue and a case is currently open with Sybase. | |
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. | |
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. | |
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. | |
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. | |
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. | |
Workaround: There is currently no workaround for this issue. It will be fixed in a future server release. | |
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. | |
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. | |
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. |
The EngineSummary Table shows intermittent negative values for cpu_busy_pct. Workaround: There is currently no workaround for this issue. | |
Workaround: There is currently no workaround for this issue. It will be fixed in a future server release. | |
The RS_Latency_Graph view has an incomplete view label. Workaround: Expected Sybase behavior. | |
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:\>cd Program files\Quest Software\Foglight -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 | |
The agent parameter Exclusion list name is not the same as in Foglight 4. Workaround: There is currently no workaround for this issue. | |
The Agent Version and Stored Procedures Version fields are blank. Workaround: There is currently no workaround for this issue. | |
The SYBM_ASE_Availability view does not show the name of the Sybase server. Workaround: There is currently no workaround for this issue. | |
Data for UsersBlocked view gets displayed in UsersBlocking view. Workaround: There is currently no workaround for this issue. | |
UsersBlocking view shows incorrect data. Workaround: There is currently no workaround for this issue. | |
Received exception: position beyond end of string from BenchMarkTimes. Workaround: There is currently no workaround for this issue. | |
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. | |
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. | |
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. | |
Workaround: There is currently no workaround for this issue. |
Roles mechanism. To view the new Sybase dashboards, a user must have the minimum privileges of: Workaround: There is currently no workaround for this issue. It will be fixed in a future release. | |
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. | |
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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center