Resolution:
For FT EMS servers, the primary server always maintains the lock on the store file until its process terminates.

When the Primary is up and running and the secondary server under FT mode is brought up, then the secondary tries to connect to the url that is in the "ft_active" parameter. If the connection is established with the primary then the secondary goes into standby mode. But, if the connection is not established the secondary server *assumes* that the primary is not up and tries to take on primary role and tries to lock the shared storage db file. In this case if it gets the lock then it successfully becomes the primary and if it cannot obtain the lock immediately, it alternates between attempting to obtain the lock (and become the primary server), and attempting to reconnect to primary (and resume as a backup server) every 10 seconds—until one of these attempts succeeds.  

File-Lock Manager is needed in order to make sure locks are only released when there is an absolute failure of the primary server. Without the File-Lock Manager, both the primary and secondary servers may write to the file at the same time and the db file corruption may happen.