Kbase 21833: ProControl Warning: "TIMEOUT - Continue waiting?"
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/25/2002 |
|
SUMMARY:
When starting up a database using ProControl, you might see the following warning message:
TIMEOUT - Continue waiting?
While the message shows no error numbers, the warning relates to Progress error number (6387).
EXPLANATION:
ProControl has timed out while attempting to startup a database. This can happen due to one or both of the following reasons:
A) Due to the -B parameter.
With the database buffer pool, a certain amount of memory needs to
be allocated. (See Progress Knowledge Base Solution 20183 to
calculate the amount of memory.) Sometimes this allocation will
create a delay sufficient to produce the ProControl timeout. Since
the behavior will vary across machines, it can be a trial and
error process to determine the timeout limit.
B) Due to the BI cluster size.
In the case of the BI cluster size, it will only timeout the first
time after truncating the BI. After a truncation, hard disk space
needs to be allocated when the database is started up. If the BI
cluster size is large enough, it will also create a delay that can
result in a ProControl timeout. Again, this is machine dependent.
SOLUTION:
Decrease the database buffer pool size and/or the BI cluster size to prevent a timeout.
References to Written Documentation:
Progress Knowledge Base Solutions:
20183, "Calculating Effects of -B on Memory Allocation"
17645, "What Should My BI Cluster Size Be?"