Kbase P8213: Cannot start database through Progress Explorer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/12/2005 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
SYMPTOM(s):
Cannot start database through Progress Explorer
Error 8619 when trying to re-start database from Progress Explorer
** This process terminated with exit code 1. (8619)
Progress Explorer being used to start databases
Database has not been started from outside the Progress Explorer
All databases start up initially in Progress Explorer
When stopping a database in Progress Explorer, can't re-start it
Progress Explorer Properties After-image Writer check box not used
CAUSE:
The "green_start_button" appears to be able to be ready to use before, in fact, it is able to be used.
Firstly, because Progress Explorer uses java, which runs silent, the "green_start_button" becomes enabled before the stop process has actually completed.
Secondly, when starting a database, it takes "time" to initialise shared memory (-B value amoungst other lesser startup parameter contributors).
FIX:
SYSTEM RESOURCES ISSUE:
By checking the database status with:
dbman dbname -query # Note, this is a Progress 9.x utility
and if this shows that the database has infact stopped, you have found the "problem" and will be able to start the database again from Progress Explorer.
The time delay between trying to start the first time and running the query is sufficient to allow the database to shut down. This is merely a resources issue, don't try to start the database immediately after stopping it. (ie: as soon as the "green button" becomes available)
Look at TASK MANAGER -> Performance
When you stop the database, Physical Memory (K):
Available: increases
File Cache: decreases
and vice versa when you start another process. If Available = 0 it means that the system is swapping, indicative of overuse of system. Look into increasing CPU Speed, RAM, and if Enterprise License, more processors to introduce -spin.