Foglight for Sybase 7.3.0 - Release Notes

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.

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.

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.