Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

BEA-300040 Igamot O error while writing node manager status with ORACLE OMS startup failure

2025-04-03 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/02 Report--

Today we are dealing with a startup exception in oms, an oracle optimization management tool. Before the oms problem is handled, a set of asm and db on the server where oms resides

The depletion of the audit directory file system inode caused abnormal downtime of asm and db. After cleaning the logs of the audit directory, asm and db started normally, but oms started abnormally.

1. Abnormal analysis of OMS startup

1. OMS startup exception message

[oracle@orcl bin] $. / emctl start oms

Oracle Enterprise Manager Cloud Control 12c Release 4

Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.

Starting Oracle Management Server...

Starting WebTier...

WebTier Successfully Started

Oracle Management Server Could Not Be Started

Check EM Server log file for details: / u01/app/oracle/oms/domains/GCDomain/servers/ORCL_OMS1/logs/ORCL_OMS1.out

Oracle Management Server is Down

[oracle@ orcl bin] $

2. View the ORCL_OMS1.out log

Mar 19, 2020 5:55:44 PM oracle.security.jps.internal.audit.AuditServiceImpl registerInternal

WARNING: Cannot register to audit service for component "JPS".

Mar 19, 2020 5:55:44 PM oracle.security.jps.internal.policystore.ldap.LdapPolicyStore initial

INFO: Container is not ready at the point null

3. According to the .out log prompt, it is consistent with the previous abnormal error reports of asm and db startup, and the excessive audit logs of the oracle database caused file system inode exhaustion.

Caused by the failure of other processes to write.

II. Problem handling

1. For oms, simply restarting oms cannot solve the problem, because the nodemanager process does not stop normally.

2. Use ps-ef | grep java to kill the oms-related java process kill-9 java_process_number

3. Try to start the oms process again and start it successfully

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report