My Oracle Support Banner

EM 13c: omspatcher status -addomsstatus failed as Invalid command (Doc ID 2968561.1)

Last updated on MARCH 04, 2024

Applies to:

Enterprise Manager Base Platform - Version 13.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

The addomsstatus command failed with below error.

Successfully completed Primary OMS patching. The EM console will be accessible, however, to fully monitor and utilize all features you must wait until all other additional OMSs are patched.

Run '<Middleware_Home>/OMSPatcher/omspatcher status -addomsstatus' for multioms patching status

While executing the addomsstatus command failed as below

<Middleware_Home>/OMSPatcher/omspatcher status -addomsstatus
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation. All rights reserved.

OMSPatcher version : 13.9.5.14.0
OUI version : 13.9.4.0.0
Running from : <Middleware_Home>
Log file location : <Middleware_Home>/cfgtoollogs/omspatcher/opatch2023-07-17_22-40-31PM_1.log

The 'addomsstatus' parameter option in omspatcher utility is valid only for multi-OMS setup when applying RU16 or later RUs. Use this parameter to check the status of an additional OMS in a multi-OMS environment after applying an RU.

OMSPatcher failed with error code 2



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.