Salesforce

AdminServer cannot start Replication enabled databases error 10356

« Go Back

Information

 
TitleAdminServer cannot start Replication enabled databases error 10356
URL Nameadminserver-cannot-start-replication-enabled-databases-10356
Article Number000140617
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
Databases enabled for Replication fail to start through the OE Console (or dbman): (10356)
Replication enabled databases cannot be started by the AdminServer

When Replication enabled databases are started with DBMAN (or through the OEE Console), the admserv.log "Command" line, is missing
  • "-DBService, replserv"
  • "-DBService, replagent"
The admserv.log file shows no evidence of the Replication Plugin being loaded (Plugin.Replication)
Steps to Reproduce
Clarifying Information
Advanced Enterprise RDBMS license is not installed
OpenEdge Replication or OpenEdge Replication Plus license is listed under Configured Products
Replication enabled databases start unmanaged from the command line with proserve 
prorepl.jar is in the classpath
Error MessageAccess to database <dbname> not allowed. The database is enabled for site replication but either replication is not running, or this process is not authorised to open a replication enabled database. (10356)
Removed shared memory with segment_id: <shmid> (16869)
Defect Number
Enhancement Number
Cause
The AdminService doesn't load the Replication Plugin.  As a result, the replication enabled database cannot be opened by the AdminServer.

During the install, a replication.delta file is created,
During the install tailoring phase, mergeprop is used to update the information from the replication.delta file into the AdminServerPlugins.properties file.

Without this information in the AdminServerPlugins.properties file, the Replication Plugin is not loaded when the AdminServer is started.
Without the Replication Plugin, the AdminServer cannot start replication enabled databases, which is why the database fails to start without the required "-DBService" parameter.

The exact cause this install tailoring failed is not known at this time.
Resolution
Use mergeprop to add the entries from DLC/proerties/delta/replication.delta file to add these entries to the AdminServerPlugins.properties file.
Verify the the correct directory to the prorepl.jar from this install are referenced in the [PluginPolicy.Replication] classpath

PROENV> mergeprop -action update -delta DLC/properties/merged/replication.delta -type plugin -target DLC/properties/AdminServerPlugins.properties
Once complete, mergeprop will create a backup of the current AdminServerPlugins.properties.

The AdminServer will need to be restarted in order for the Replication Plugin to be loaded.  Shutting down the AdminServer with the -keepservers property, will leave your ubrokers and databases running:
 
$  proadsv -stop -keepservers
 
When the AdminServer is restarted, these Replication Plugin will initialize:
 
[AdminServer] Added ServerPlugin: Plugin.Replication (7431) 
[AdminServer] Installing plugin: Plugin.Replication (7432) 
[AdminServer] Plugin.Replication: Plugin installed. (ADMMsg002) (7440)
[AdminServer] Starting plugin Plugin.Replication. (7434) 
[AdminServer] Started plugin Plugin.Replication. (7435) 

Replication enabled databases will now start through the OE Console (or dbman) 
Workaround
Notes
Keyword Phrase
Last Modified Date4/26/2021 5:52 PM

Powered by