If a DP4 multiple resilience configuration is used in which there is no local database and more than server is accessed by default (you have multiple -use or -mustuse command tails), then 4.6xx applications may load maps incorrectly.
This problem arises if the databases on the two servers do not contain identical map information. For example if two databases initially contain different maps and the same MAPPOST file is then posted two both databases, then although the maps are visually identical when inspected with MAPEDIT, the controls in the map will most likely have been allocated different internal numbers on the two servers. Because AUXDISTR fetches data from any server indiscriminately it may happen that when loading the map, the map table information is read from one server, but the controls are then looked up on the other database and are therefore loaded incorrrectly.
The problem only arises with the -nolocal command tail, because otherwise maps will all be loaded from the local copy of the database.
There are two possible work-arounds for this problem:
Make sure databases on all servers start from a common ancestor and that any subsequent map changes are applied in step with each other on all servers. The easiest way to do this is probably to use the "split" database facility, so that you can simply use exactly the same programs database on all servers
Use only one -use or -mustuse command tail on AUXDISTR, and create suitable @NETWORK records for tables that should be updated on more than one server.