Go to main content

Oracle® Solaris Cluster Data Service for Sybase ASE Guide

Exit Print View

Updated: July 2014, E39577–01
 
 

HA for Sybase ASE Logging and Security Issues

The following sections contain information about HA for Sybase ASE logging and security issues.

HA for Sybase ASE Logging Issues

HA for Sybase ASE logs messages to the file message_log in the /opt/SUNWscsyb/log directory. Although this file cannot exceed 512 Kbytes, HA for Sybase ASE does not delete old log files. The number of log files, therefore, can grow to a large number.

HA for Sybase ASE writes all of the error messages in the syslog file. HA for Sybase ASE also logs fault monitor history to the file restart_history in the log directory. These files can also grow to a large number.

As part of your regular file maintenance, check the following log files and remove files that you no longer need.

  • syslog

  • message_log

  • restart_history

HA for Sybase ASE Security Issues

HA for Sybase ASE requires that you embed the system administrator's password in a stop file. The /opt/SUNWscsyb/bin directory contains the template for the stop file, sybase_stop_servers. HA for Sybase ASE uses this file to log in to the Sybase ASE environment and to stop the Sybase ASE servers. Enable the sybase user to execute the stop file, but protect the file from general access. Give read, write, and execute privileges to only the following users.

  • sybase user

  • sybase group