Sybase Agent Collection Failure Due to Missing Temporary Tables or Stored Procedures (4379536)

• Sybase agent fails to collect metrics (e.g., EngineSummary, Connection Usage)

• Alarms such as Connection_Usage do not fire despite being enabled

• Foglight agent logs show errors such as:

FrameworkQueryException: tempdb..fgl_sy2_deltatable not found.

• Commonly impacted metrics include: num_con_pct, num_con_used, num_con_free

The Sybase agent depends on temporary tables and stored procedures that are dynamically created when the agent starts. These include:

• Tables: fgl_sy2_deltatable, fgl_processes, fgl_missed_SQLText, tmpscc

• Procedures: sp_fgl_enginesummary1 and others prefixed with sp_fgl_

If these are missing, corrupted, or improperly owned (e.g., created by a user with sa_role), the agent fails to collect data.

Step 1: Deactivate the Sybase Agent

1. Navigate to the affected Sybase agent in the Foglight UI.

2. Click Deactivate to stop the agent cleanly.

Step 2: Cleanup Residual Database Objects

Log in to the monitored Sybase instance and run the following commands:

-- Remove temporary tables (use tempdb)
use tempdb
go
drop table fgl_sy2_deltatable
drop table fgl_processes
drop table fgl_missed_SQLText
drop table tmpscc
go

-- Remove stored procedures (use sybsystemprocs or relevant db)
use sybsystemprocs
go
drop procedure sp_fgl_enginesummary1
go
-- Drop other sp_fgl_ procedures if present

Step 3: Verify Agent User Permissions

Ensure that the monitoring user (used by the Sybase agent) has only the mon_role. This avoids improper persistence or ownership of agent objects.

Step 4: Reactivate the Agent

1. Go back to the Foglight UI.

2. Click Activate to restart the agent.

3. Monitor the agent log for confirmation that stored procedures and temporary tables are recreated:

Installing new stored procedures
Collection EngineSummary started successfully

Step 5: Validate Collection and Alerts

1. Navigate to the agent.

2. Confirm metrics.

3. If necessary, lower thresholds temporarily to test alert triggering.

Prevention

• Always use a monitoring user with only mon_role

• Avoid using sa_role for agent users

• Ensure objects are cleaned up and recreated after Sybase restarts

Additional Information

• If the monitored instance was restarted, temporary objects may be lost. Reactivation of the agent is required.

• If stored procedures persist, it may indicate they were created with sa privileges.