DB2 Satellite Edition enables mobile, or pervasive, computing where occasionally connected computers have locally persistent data that is easily updated and synchronized with corporate data at a central site.
Status information about each production satellite is retained in a central database known as the satellite control database. The status information includes problem reporting. The Satellite Administration Center is used to review the status information from the satellite control database.
If a problem has been reported then test satellites, model offices, and script files called batches are used to remotely administer satellites and to troubleshoot satellite problems.
Within a satellite environment, test satellites are used to test the group batches that set up and maintain the database definition that supports the end-user application. How to define a satellite as a test satellite is described in the online help available from the Satellite Administration Center.
In addition, the satellite environment has a model office which is a special member of the test satellites in a group. Typically, you have one model office for each version of the end-user application that you have deployed in the group. There are several reasons for having model offices:
Model offices are key to solving problems within a satellite environment. Test satellites can be created that are copies of the model office. These test satellites can then be used to reproduce and solve any problems or to prevent problems through the testing of group batches before they are deployed to production satellites.
You can find details about troubleshooting in a satellite environment in the Administering Satellites Guide and Reference manual.
Replication is a major feature of the satellite environment. Problems encountered in a satellite environment may involve replication. See Chapter 9, Troubleshooting Replication for information on troubleshooting replication problems.