Foglight for Sybase 5.9.7.23 - Release Notes

FOG-2780

No data in DB Administration after upgrading FMS but not db cartridge

FOG-2582

Error message in Database Groups after upgrade from 5.9.5 to 6.0.0

FOG-2546

sp_fgl_dbspace procedure failed ,reason=Arithmetic overflow

FOG-2955

ValidationMdaRoleProcessor Failed

FOG-2997

Sybase AgentErrorLog rule not looking at timezones properly

FOG-3034

Sybase Agent Fires Repeatedly and Erroneously

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.

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