Chat now with support
Chat with Support

Foglight for Sybase 5.5.8.46 - Release Notes

New in this Release

New in this Release

Version 5.5.8.46 contains the following new features and updates:

  • Spinlocks screens:
    • Under Bufferpools > Data cache Spinlocks
    • Under Top Activity > Spinlocks
    • Max Spinlocks contention rule
      Note: data is available only for version ASE 15.7.0 and higher
  • Tables activities screens:
    • Under Databases > Top I/O Active Tables
    • Under Databases > Top Lock Activity Tables
  • Execution Times screen:
    • Under Top Activity > Execution Times
      Note: Execution Time data is available only for version ASE 15.7.0 SP100 and higher

For a list of issues fixed in this patch, see the issues listed in Resolved Issues.


Resolved Issues and Enhancements

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Issues Resolved in this Patch

Defect ID

Resolved Issue

SDB-807

ASE availability monitoring has been changed.
Backup Server monitoring can be disabled by tuning a new ASP entry located in the “Availability Monitoring” ASP list. The entry name is “SybaseBackupServerStatus”.


Known Issues

Known Issues

The following is a list of issues known to exist at the time of this release.

Sybase_RS Agent

Defect ID

Known Issue

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

Sybase_MDA Agent

Defect ID

Known Issue

SDB-544 On the Top Activity dashboard, on the Top Procedures tab, the SQL Execution Statistics dialog box now provides the Compile Date. If a stored procedure is recompiled, this field might not provide any value (that is, it might be empty).
Workaround: There is currently no workaround for this issue.

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.

SU-2113 When the Sybase_MDA agent connects, the system generates the following error: "WARN - The scheduled task named <task name> from group <group name> failed to acquire the agent lock. It was not executed."
Workaround: Edit the Agent Manager user permissions so that the agent has access to the interfaces file located in the Sybase Home directory.

Sybase Dashboards

Defect ID

Known Issue

N/A

Under some circumstances, the time range is set to a range that occurs in the past. This is indicated by the time range icon that appears inside a red rectangle.

Workaround: To switch to real time, click the time range icon.

N/A

Roles mechanism: to view the new Sybase dashboards, the user must have the minimum privileges of:

  • Foglight Operator

  • Sybase Administrator

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.

SDB-407 Sybase reports are only be accessible by those Foglight users whose accounts include the Sybase Admin role.

Upgrade

Defect ID

Known Issue

SDB-657 When upgrading the Cartridge for Sybase to version 5.5.8.39 or higher, you might encounter the following error message: One or more of the selected agents require upgrade. To resolve this issue, update the Sybase account for Foglight by manually running the scripts.
Workaround: Ignore this message. It is benign.

 

 


Third Party Known Issues

Third Party Known Issues

There are no third party issues known to exist at the time of this release.

 

 


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating