On this page:

Your Rating:
16 rates
You can monitor any version of Sybase IQ with Database Visibility.

Connection Details

Database TypeThe database type that you want to monitor.
Database AgentThe Database Agent that manages the collector.
NameThe name you want to identify the collector by.
Hostname or IP AddressThe hostname or IP address of the machine that your database is running on.
Listener PortThe TCP/IP address of the port on which your database communicates with the Database Agent
Custom JDBC Connection StringThe JDBC connection string generated by the database agent. You can also specify a custom connection string, which is useful for setting custom authentication options.
UsernameThe name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for Sybase IQ.
PasswordThe password of the user who is connecting to and monitoring the database through the Database Agent.

Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type.


  • All connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector. If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API.

  • You cannot convert a custom cluster collector to a standalone collector. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector. However, note that deleting the custom cluster collector will delete all its historical data.
Connection PropertiesClick to add a new JDBC connection property or edit an existing property for relational databases.
CyberArkClick to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file. 
Logging EnabledClick to enable verbose mode logging, which logs all communications between the Controller and the Collector. Enable only during troubleshooting because logging consumes a lot of disk space. If you have enabled logging, you can click the logging icon in the Log column of the Collector Administration window to view the log file. The log files are located in the <db_agent_home>\agent directory and have the format <CollectorName>_out.log and <CollectorName>_err.log.

User Permissions for Sybase IQ

To monitor with a non-DBA account, you need the following:

  • User account with SERVER OPERATOR system privilege. 
  • Execution privileges on several procedures which can be granted as follows:

    grant execute on sp_iqconnection to DBMon_Agent_User
    grant execute on sp_iqtransaction to DBMon_Agent_User
    grant execute on sp_iqcontext to DBMon_Agent_User
    grant execute on sp_iqstatus to DBMon_Agent_User
    grant execute on sp_iqcolumn to DBMon_Agent_User
    grant execute on sp_iqindex to DBMon_Agent_User

    where DBMon_Agent_User is the user name under which you run the Database Visibility Agent.

  • Grant DBA authority to DBMon_Agent_User as follow:

    grant DBA to DBMon_Agent_User
  • No labels