Kbase P138204: A procopy of a database with AI and AI ARCHIVER enabled, will have AI disabled but AI ARCHIVER is st
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/08/2010 |
|
Status: Verified
SYMPTOM(s):
A procopy of a database with AI and AI ARCHIVER enabled, will have AI disabled but AI ARCHIVER is still enabled on the copy
AIMGT enabled and AI disabled after procopy
Database fails to start with error 13242
The after-image extent manager daemon cannot be started because after-imaging is not started for the database. (13242)
FACT(s) (Environment):
A restored probkup has neither the AI nor the AI Management enabled
CAUSE:
Bug# OE00178279
FIX:
WORKAROUNDS:
Depending on the intent of the procopy operation if:
A. The copy should be aiarchiver enabled, then:
1. add ai extents to the database:
$ prostrct add dbname add_ai.st
WHERE: example of add_ai.st
a . f 1024000
a . v 1024000
a .
2. Enable after-imaging:
$ rfutil dbname -C aimage begin
3. start the database with the appropriate startup parameters:
$ proserve dbname [+startup parameters] -bibufs 30 -aibufs 45 -aistall -aiarcdir <dirpath>,<dirpath> -aiarcinterval n -bithold 75000 -bistall
B. The copy should NOT be aiarchiver enabled, then
1. Disable AI Management:
$ rfutil dbname -C aiarchiver disable
3. start the database with the appropriate startup parameters:
$ proserve dbname [+startup parameters] -bibufs 30 -bithold 75000 -bistall