Kbase P127060: Database started from Progress Explorer does not get registered with AdminServer (on Cluster)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/11/2007 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1E
OpenEdge 10.X
Windows 2003
SYMPTOM(s):
Database started from Progress Explorer does not get registered with AdminServer
Starting database using dbman shows the same problem
Using Clusters
Starting database from Cluster Manager works fine
"Start database in a Cluster mode" is ticked on in Progress Explorer
Removing "Start database in a Cluster mode" from Progress Explorer leads to a successful startup including registration on the AdminServer
Database has been enabled for Cluster by procluster command
CAUSE:
When procluster enable is run - database gets registered on Cluster Manager as cluster protected resource. At the same time a flag "Cluster enabled" is set on the master block.
Database in question has been recreated from scratch, without removing it from Cluster first (procluster disable) and re-adding it again (procluster enable). I.e. the newly created database did not have set "Cluster enabled" flag in the master block.
Therefore Progress Explorer/dbman could not fully complete the startup.
FIX:
When re-creating "Cluster enabled" db, first "procluster disable" it, then create a new copy of a database, then "procluster enable".