Why does the RepServer module have a Down (black) alarm condition even though the Sybase Rep Server is running?
This may be caused when the module cannot connect to the Sybase Rep Server. When the RSSD transaction log is full, the Sybase Rep Server does not accept logins or isql connections. As a result, the RepServer module shuts itself down. You can avoid this situation by monitoring the RSSD transaction log using both the RepServer module and the Sybase module. Thus, if your RSSD transaction log gets close to being full, you can be notified by the modules to take corrective action before your RepServer module shuts down. For example, use the RepServer to notify you when the transaction log is 45, 50, and 60% full as Info, Alert, and Critical alarms; and use Sybase to notify you when the transaction log is 70% full as a Critical alarm. 3.2 I followed the suggestion in Question 3.6 for monitoring the RSSD transaction log, but I still don’t receive an alarm notification from the RepServer module before that module shuts itself down. What should I do? This may be caused by the alarm thresholds be
This may be caused when the module cannot connect to the Sybase Rep Server. When the RSSD transaction log is full, the Sybase Rep Server does not accept logins or isql connections. As a result, the RepServer module shuts itself down. You can avoid this situation by monitoring the RSSD transaction log using both the RepServer module and the Sybase module. Thus, if your RSSD transaction log gets close to being full, you can be notified by the modules to take corrective action before your RepServer module shuts down. For example, use the RepServer to notify you when the transaction log is 45, 50, and 60% full as Info, Alert, and Critical alarms; and use Sybase to notify you when the transaction log is 70% full as a Critical alarm. 3.2 I followed the suggestion in Question 3.6 for monitoring the RSSD transaction log, but I still don’t receive an alarm notification from the RepServer module before that module shuts itself down. What should I do? This may be caused by the alarm thresholds be
Related Questions
- Why does the PrimeAlert for Oracle module have a Down (black) alarm condition with the message "Module Status is Not Accessible" even though the Oracle server is running?
- Why does the RepServer module have a Down (black) alarm condition even though the Sybase Rep Server is running?
- Why does the PrimeAlert for SQL Server module have a Down (black) alarm even though SQL Server is running?
