 |
Real Time eXecutives,
Inc.
|
Technical Tips
Changing the Dead Time Timers
If you are unable to access data from a database because the database "Newest
Time" reports an old time, then changing the configuration settings for your Database “Dead
Time Timers” should fix the problem.
The following procedure outlines what is involved in this.
- On the RTXHDB server
- Stop the scheduler
- Execute the hdbview32.exe program to get the Window
- Click on the “Access” button and change your access to Level-3, (you will need to supply a password for this, the default is Administration)
- Select a Database from the pull-down list. (To begin with, select the one
(1) second database). You will get the Window
- Click on the “Subsets” button, you will get a Window similar to the following (except it should have many more lists)
If you look down this list, you will be able to find a list, which has a “Newest Time” corresponding approximately to the value you see in the Variables
Add-in for the Hour Database.
- Select a Subset and double click on it to get a Window similar to the following
- Ensure that the “Use Dead Time Timer” checkbox is checked and that you have a non-zero value in the
"Dead Time Timer" field. The value you should use represents a number of timeslots. Since each list updates the database every minute, a value corresponding to 10 minutes would be a reasonable number to put in here. The values for each database list would then be
| 1Second | 600 |
| 2Second | 300 |
| 10Second | 60 |
| 1Minute | 10 |
- Click OK.
- Check all of your other base subsets to make sure that the "Dead Time Timer" is set correctly. (Base subsets are the subsets whose data is obtained directly from the IA or
WEStation; non-Base subsets are those that have been propagated from another database.)
- Check all of the rest of your base subsets in other databases in the same way.
- Remember to Reschedule your events on the scheduler
You will probably not see any difference to your propagated databases until data has been propagated into them from some other database. When this occurs, the hdbprop32.exe program will examine the Base collection lists and if any of those are presumed to be dead, it will mark the corresponding collection list in the
propagated target database as dead.
