Re: Cloud Control Issue

Hi Scott,

There is a document in MOS that looks like it is related to this issue. Doc ID 1944859.1
EM 13c, 12c: Agent Crashes or Restarts with 'Out Of Memory Error' 'target.interaction.execution.SeverityLogWriter' Reported in Heapdump (Doc ID 1944859.1)

Hope it helps.
CAUSE A collection is generating a large number of alerts in a very short time span causing the out of memory error. In this case, it was found to be related to Database target collection:

*oracle_database,ORCL,UserAudit,DB_User,1412689923926,Metric_Threshold_Alert,UNDEFINED,Discard State*

SOLUTION The above metric collection causing the excessive number of alerts must be investigated at the target level.

As an immediate relief, the following workaround can be used:

1. Set the following parameter on the EM Agent: $/AGENT_INST/bin/emctl setproperty agent -allow_new -name _traceSeverityForTypes -value noTypes
2. Restart the agent:

$/AGENT_INST/bin/emctl stop agent
$/AGENT_INST/bin/emctl start agent

Regards,
Osman DİNÇ
InsaneDba
https://insanedba.blogspot.com/

Scott Canaan <dmarc-noreply_at_freelists.org>, 9 Oca 2024 Sal, 22:16 tarihinde şunu yazdı:

> We are in the process of migrating our databases from Red Hat 7 to Red Hat
> 8. When the new VMs are set up, the cloud control agent runs fine. As
> soon as we configure the database and listener for the new server, it
> crashes. It will start, but won’t stay up. The only thing I can find in
> the log is:
>
>
>
> Agent is going down due to an OutOfMemoryError
>
> ----- 2024-01-09 13:28:25,329::2923::Checking status of EMAgent : 1951180
> -----
>
> ----- 2024-01-09 13:28:25,329::2923::EMAgent exited at 2024-01-09
> 13:28:25,329 with return value 57. -----
>
> ----- 2024-01-09 13:28:25,329::2923::EMAgent will be restarted because of
> an Out of Memory Exception. -----
>
> ----- 2024-01-09 13:28:25,330::2923::EMAgent is Thrashing. Exiting loop.
> -----
>
> ----- 2024-01-09 13:28:25,330::2923::Commiting Process death. -----
>
> ----- 2024-01-09 13:28:25,330::2923::writeAbnormalExitTimestampToAgntStmp:
> exitCause=OOM : restartRequired=0 -----
>
> ----- 2024-01-09 13:28:25,330::2923::Exited due to Thrash. -----
>
>
>
> In working with the sys admin, he said that it’s our problem and has no
> idea where to look and which parameter needs to be changed, let alone what
> to change it to.
>
>
>
> Where do we look to figure this out?
>
>
>
> *Scott Canaan ‘88*
>
> *Sr Database Administrator *Information & Technology Services
> Finance & Administration
>
>
> *Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
>
> *srcdco_at_rit.edu <srcdco_at_rit.edu>* | c: (585) 339-8659
>
> *CONFIDENTIALITY NOTE*: The information transmitted, including
> attachments, is intended only for the person(s) or entity to which it is
> addressed and may contain confidential and/or privileged material. Any
> review, retransmission, dissemination or other use of, or taking of any
> action in reliance upon this information by persons or entities other than
> the intended recipient is prohibited. If you received this in error, please
> contact the sender and destroy any copies of this information.
>
>
>

--
http://www.freelists.org/webpage/oracle-l