The Sybase SAP ASE agent is installed, but data does not appear in the panels and the logs indicate that collections are failing due to permission errors.
The Sybase SAP ASE agent user was not configured with the required permissions.
One cause is that the Sybase SAP ASE agent user account already existed in the sybsystemprocs database before running the setup procedures. This often happens if the login was created manually for a previous test, POC, or earlier setup attempt.
In the rapsAdmin.sql script, the logic for granting CREATE PROCEDURE to the user in sybsystemprocs is handled by the sp_fgl_addgrant procedure, which is called from within sp_fgl_adduser only when the user is being created in a database for the first time:
if ( @userExists = 0 )begin-- ... code to add group if needed ...-- ... code to add user ...if(@dbName = 'sybsystemprocs')beginexec sybsystemprocs..sp_fgl_addgrant @fogUserend-- ... other code ...end
The grant is only performed when the user is being created for the first time in sybsystemprocs. If the user already exists, the script does not check or re-grant CREATE PROCEDURE. This is why an explicit grant is needed if the user was pre-created.
Note:
While this is one cause, other permission or configuration issues may also prevent the agent from collecting data. Always review the agent logs for specific error messages to identify the root cause in your environment.
1. Create a Foglight login account in the Sybase database (if it does not already exist).
For example:
sp_addlogin 'svcfgadmin', 'foglight', sybsystemprocs
go
2. Grant the mon_role role to the account:
grant role mon_role to svcfgadmingo
3. Run the rapsAdmin.sql script as the sa user.
This script creates the required stored procedures for user and permission management.
4. Run the sp_fgl_adduser procedure as the sa user:
sp_fgl_adduser 'svcfgadmin', 'foglightGroup'go
This command creates a group named foglightGroup and a user named svcfgadmin in each database. In the sybsystemprocs database, it grants the CREATE PROCEDURE permission to the user account if the user is being created for the first time.
Note:
If the login (e.g., svcfgadmin) already existed in the sybsystemprocs database before running sp_fgl_adduser, the procedure will not re-grant CREATE PROCEDURE. In this case, you must manually grant the permission:
use sybsystemprocsgogrant create procedure to svcfgadmingo
5. Restart the agent.
6. (If errors persist) Clean up temp tables:
If there are errors in the log file, stop the agent and manually delete any fgl_ tables from the temp database in case they were created with the wrong schema:
drop table fgl_blocker_SQLTextgodrop table fgl_missed_SQLTestgodrop table fgl_processesgodrop table fgl_sy2_deltatablegodrop table fgl_waitinfogo