Adding a secondary Batch server in Version 5.1
There are instances where Primary has been running without a Secondary Batch Server. When attaching a new Secondary to a formerly single server/Primary configuration the user will see various indications of an issue. The primary will show primary then the condition will change. The primary and secondary never go to a primary/secondary state. Eventually both machines go to a client state. This indicates both batch servers do not recognize each other as their redundant partner.Symptoms:
The fix is to reboot the primary after loading the secondary. This is mentioned in the book, but in the event of adding a secondary when the site is already in production the reboot is over looked. Many times the plant is in full production and the Primary cannot be rebooted. In this case the primary never gets various ODBC links it needs to recognize the secondary.
When rebooting the user should shutdown the secondary first. Reboot the primary and let the system return to normal with the "P" indication in the tool bar representing the batch server is now in the Primary state. Only then should the secondary be restarted and allowed to go online. At that point the two servers should synch.