Salesforce

Database fails to start multi-user post CONV1011, error 13242

« Go Back

Information

 
TitleDatabase fails to start multi-user post CONV1011, error 13242
URL NameDatabase-fails-to-start-multi-user-post-CONV1011-error-13242-000063361
Article Number000175321
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: CONV1011
Question/Problem Description
Database fails to start multi-user post CONV1011, error 13242
Error 13242 trying to start database after successful CONV1011 Aiarchiver enabled database
Aiarchiver still enabled after successful CONV1011 of an AI Management enabled source database
AI is disabled as part of the CONV1011 routine but not AIMGT
Restored database fails to start multi-user with error 13242
Restored database can be accessed single-user
Steps to Reproduce
Clarifying Information
CONV1011 succeeds without error:
After-imaging must be disabled before database conversion. (1292)
After image logging has been turned off for <dbname>. (6601)
VST Table Deletion has begun. Please standby. (6876)
VST Table Deletion has completed successfully. (6885)
Conversion completed, database is now in 11 format.

PROUTIL -C describe shows AIMGT still enabled on the PROREST database:
Database Features

   ID   Feature                            Active  Details
  ----  ---------------------------------  ------  -------
     8  After Image Mangement/Archiver     Yes
Error MessageThe after-image extent manager daemon cannot be started because after-imaging is not started for the database. (13242)
Defect NumberDefect PSC00340771 / OCTA-3248
Enhancement Number
Cause
The conv1011 Major Version database migration utility, disables AI but leaves AIMGT enabled. The AI extent manager daemon cannot be started until after-imaging is started for the database.  Usually, only once after-imaging is started the AI Archiver feature can be enabled for the database to manage AI extent archiving.
Resolution
Upgrade to OpenEdge 11.7.5 or later where conv1011 disables after-imaging, AIMGT and Replication (when enabled)
Workaround
Post CONV1011: Depending on the intent of the CONV1011 operation if:

A.  The converted database should be aiarchiver enabled, then:
 
1. Enable after-imaging:
$  rfutil dbname -C mark backedup
$  rfutil dbname -C aimage begin


3. Start  the database with the appropriate startup parameters:

$ proserve dbname [+startup parameters] -aibufs 45 -aistall -aiarcdir <dirpath1>,<dirpath2> -aiarcinterval n 


B.  The converted database should NOT be aiarchiver enabled, then

1. Disable the AI Archiver: 
$  rfutil dbname -C aiarchiver disable

2. Start  the database with the appropriate startup parameters:

$ proserve dbname [+startup parameters] 

Pre CONV1011: Disable AI, which disables dependent features at the same time.

$   rfutil dbname -C aimage end
Notes
Keyword Phrase
Last Modified Date1/6/2020 4:59 PM

Powered by