Kbase P126232: Replication enabled database cores when started multi-user
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/1/2010 |
|
Status: Verified
SYMPTOM(s):
replication enabled database does not start multi-user
multi user start-up session stops after the 13870 message in the database lg file
Database Service Manager - IPC Queue Size (-pica) : 6.0 KBytes (13870)
proserve of replication enabled database crashes with protrace file
Stack trace from _mprosrv.exe reads:
dbut_firstByte
FACT(s) (Environment):
All Supported Operating Systems
Fathom Replication
CHANGE:
The database control area has been rebuilt for either the source or the target database with the prostrct builddb utility.
CAUSE:
When the database control area has been rebuilt for either the source or the target database, the prostrct builddb utility does only minimal validation of the resulting control area and is not able to fully reconstruct all the control information needed by replication.
Amongst others, it will disable the after-imaging flag in the master block if enabled i.e. in dbname.d1. Replication keeps recovery information in a blob in the .db file. The database code cannot recreate this information since it is replication specific.
By rebuilding the control area, effectively the database has been disabled for replication. This utility should never be used in a replication environment before disablesitereplication and then only when all other avenues have been exhausted.
FIX:
The replication baseline will need to be re-established. It is not the intent of this Solution to fully describe the steps involved. These should be fully documented in the site Disaster recovery plans based on the individual environment requirements and version possibilities.
A. If souce database control area was rebuilt: remove the [source | target].repl.recovery files, re-enable replication on source database, take a new full backup of source then restore this backup to target and finally enable replication on target database.
B. If target database control area was rebuilt: remove the target.repl.recovery files, take a new full backup of source then restore this backup to target and finally enable replication on target database.
C. There may be extraneous circumstances in the production environment which lead to the perceived need for the control area to be rebuilt. Other recovery options may include:
a.) go to backup
b.) dump out database single user