Oracle $ cd /u01/app/oracle/agent/agent12c/binīut as you might have guessed by now, this didn’t help at all. u01/app/oracle/agent/agent12c/sysman/emd We concluded that they were communicating, so that was another theory to discard… Then, we tried something that used to work in 11g: move the upload, state directories, and then bounce the agent, clearing the state. Verifykey: Successfully Completed communication with agent Oracle Enterprise Manager Cloud Control 12c Release 2Ĭopyright (c) 1996, 2012 Oracle Corporation. We checked from the server where the agent resided to see if it was responding. The next thing we did was to check if the agent was communicating with the OMS. emctl upload agentīut with our luck, that neither helped nor changed anything. So the first thing we did was to bounce the agent and clear its state. It goes to say that before the maintenance, both showed as up. We performed maintenance in a 2-node cluster and both instances came up fine, but one of the instances in OEM’s Cluster Database target was showing a pending status. The other day we had a situation with an OEM 12cR2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |