If the license can be issued during the grace period, the issue is logged and Replication Server starts. The log entry looks similar to this:
I. 2005/11/24 22:11:43. SySAM: Using licenses from: /opt/sybase/SYSAM-2_0/licenses I. 2005/11/24 22:11:44. SySAM: Checked out graced license for 1 <license_name> (2005 .1114) will expire Sat Dec 24 22:10:31 2005. I. 2005/11/24 22:11:44. SySAM: Failed to obtain 1 license(s) for <license_name> feature from license file(s) or server(s). I. 2005/11/24 22:11:44. SySAM: Cannot find license file.
Replication Server continues to operate normally until the issue causing the license failure is fixed, or until the grace period expires. The error message indicates the date and time the grace period is scheduled to end. The error log entry is repeated with increasing frequency while Replication Server operates in the grace period until you fix the issue causing the license failure. When the issue is fixed, Replication Server automatically acquires the license and moves from grace period mode into normal mode. If Replication Server cannot obtain the license before the grace period expires, Replication Server stops running.
If you obtain a Replication Server license from a network
license server, Replication Server periodically executes a heartbeat
with the network license server. A successfully acquired license
could be invalidated during the heartbeat; for example, if the license
has an expiration date or the network license server was restarted
and other Replication Server instances acquired all available licenses
before this instance could reacquire a license. If this happens, Replication
Server enters a grace period. This information is written in the error
log, and is similar to the information written to the error log
when you initially start the product.