지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Sybase 7.3.0 - Release Notes

Foglight ® for SAP ASE 7.3.0

Foglight ® for SAP ASE 7.3.0

Welcome to Foglight for SAP ASE

Foglight ® for SAP ASE enables Foglight to monitor SAP ASE database systems. The cartridge monitors database resource utilization for capacity planning, problem determination, and trend analysis, in both real-time and historical time.

These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 7.3.0 release of Foglight for SAP ASE. Review all sections before starting the installation.

Resolved issues and enhancements

Resolved issues and Enhancements have been published in the Foglight for Databases 7.3 Release Notes document. Please review that for more specific information.

Known issues

Sybase_RS Agent

 

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-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:

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.

셀프 서비스 도구
지식 기반
공지 및 알림
제품 지원
소프트웨어 다운로드
기술 설명서
사용자 포럼
비디오 자습서
RSS 피드
문의처
라이센싱 지원가져오기
기술 지원
모두 보기
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택