Skip to Content

Enabling discovery of Sybase Dataservers

Dataservers that have /opt/sybase specified as their installation directory are automatically detected by BMC Database Automation without any configuration changes.

Warning

Note

BMC Database Automation only looks for Dataservers that have /opt/sybase specified as the installation directory, not in subdirectories. For example, BMC Database Automation does not automatically detect a Dataserver that was installed in /opt/sybase/Dataserver1 or /opt/sybase/Dataserver2.

If an entry is made in the /app/clarity/dagent/etc/sybase_instances.conf file on the agent for any directory containing a Sybase home, Sybase Dataservers outside of /opt/sybase can be discovered. For example, if a Dataserver is installed in /app/clarity/example, the following entry would have to be made in the sybase_instances.conf file:

HOME /app/clarity/example

If the file that is used to start the Sybase Dataserver (that is, the RUN file) has been moved outside the Sybase home, BMC Database Automation can be directed where to find the RUN file by using the /app/clarity/dagent/etc/sybase_instances.conf file. For example, if a Dataserver home is in /app/clarity/example but the RUN file that is used to start it has been moved to /home/sybase/startup/RUN_servername, the following entries must be made in the sybase_instances.conf file:

HOME /app/clarity/example
INSTANCE /home/sybase/startup/RUN_servername

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Database Automation 8.5