OpenEdge Explorer can start a replication target database but loses connection to manage the database after it is started.

« Go Back

Information

Title	OpenEdge Explorer can start a replication target database but loses connection to manage the database after it is started.

URL Name	openedge-explorer-can-start-a-replication-target-database-but-loses-connection-to-manage-the-database-after-it-is-started

Article Number	000114020

Environment	Product: OpenEdge Version: 11.6, 11.7 OS: All supported platforms Other: OE Replication

Question/Problem Description

OpenEdge Explorer can start a replication target database but loses connection to manage the database after it is started.
OEE shows database is running after selecting the start button.
OEE shows not running after selecting the stop button but in reality the replication target database is still running.

Steps to Reproduce

Clarifying Information

Error Message	admserv.log: Database Abnormal communication failure for config: target.defaultconfiguration (8490) Database In crash handler for config com.progress.juniper.admin.MProservJuniper@330a19cc. (8486) Database log: BROKER 0: (8854) Error creating Admin Server status message. BROKER 0: (8849) Invalid request message -98 received from Admin Server. BROKER 0: (8850) Unrecoverable error in connection to Admin Server, running unmanaged.

Error Message

admserv.log:
Database Abnormal communication failure for config: target.defaultconfiguration (8490)
Database In crash handler for config com.progress.juniper.admin.MProservJuniper@330a19cc. (8486)

Database log:
BROKER 0: (8854) Error creating Admin Server status message.
BROKER 0: (8849) Invalid request message -98 received from Admin Server.
BROKER 0: (8850) Unrecoverable error in connection to Admin Server, running unmanaged.

Defect Number	Defect PSC00359691 / OCTA-3736

Enhancement Number

Cause

The AdminServer request that is sent to the target database broker is not coded to correctly return the current database status.

Resolution

Upgrade to OpenEdge 11.7.4, 12.0 or later where the function to check that the plug-in is running was changed to appropriately set the response in order that the replication database remains managed by the AdminServer.

Workaround

While the OpenEdge Management will not correctly control the target, the target database is still controllable by command line tools such as dsrutil, proshut, etc.

Alternatively start OpenEdge Replication enabled databases unmanaged through the commandline.

Examples:
proserve source -B 10000 -S 4500 -L 1000000 -spin 16000 -pica 8192 -bibufs 30 -aibufs 45 -aistall -DBService replserv
proserve target -S 4501 -B 10000 -L 1000000 -spin 1 -bibufs 50 -Mf 180 -DBService replagent

Notes

Progress Articles:

OEE: Managed Replication database fails with an Advanced Enterprise RDBMS license
11.7.3.005: "Error handling message from mprosrv" exceptions on Replication Enabled databases

Keyword Phrase

Last Modified Date	11/20/2020 6:52 AM