Enterprise Manager Generic (MOSC)

MOSC Banner

OEM 13.4 Creating standby failing at PeerAgentCommException: unable to contact peer agent

in Enterprise Manager Generic (MOSC) 1 commentAnswered ✓

Hello All,

I am creating standby using OEM 13.4 on exadata machines and its failing at the following - 

ERROR - Step - file copy from Primary to secondary -  Its trying to copy file multiple times but failed with NULL

Dispatching request: CopyFileFromPeerRequest (PUT_FILE (**************)

Reporting exception: oracle.sysman.emSDK.agent.client.exception.PeerAgentCommException: unable to contact peer agent

Also complains about the handshake error from Secondary to Primary agent.

I am suspecting its port 3874 issue, but any inputs suggestions are welcome and appreciated.

FYI - I am able to complete the standby creation process on Test exa and getting this issue on Prod exa.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center