Using OMS DEBUG mode to troubleshoot OEM 12c problems
This time, I want to show you how to troubleshoot OEM problems by enabling DEBUG mode in the OMS. The virtual machine (VM) running my sandbox installation of OEM 12c 12.1.0.4 crashed during the night. After restarting the VM and all the OEM components, I wasn’t able to login using the SYSMAN account. The error from the console was not very explicit, just, “Authentication failed. If problem persists, contact your system administrator.”
In order to get more details about the error, I decided to enable DEBUG mode for the OMS and reproduce the error. This is what I did to enable DEBUG mode.
$ cd /u01/app/oracle/oms/oms/bin
$ ./emctl set property -name log4j.rootCategory -value "DEBUG, emlogAppender, emtrcAppender" -module logging
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
SYSMAN password:
Property log4j.rootCategory has been set to value DEBUG, emlogAppender, emtrcAppender for all Management Servers
OMS restart is not required to reflect the new property value
After enabling DEBUG mode, I reproduced the error several times using the console. I also wrote down the approximate time of the error, just to easy the search in the log file. Searching in the emoms.trc file located under /em/EMGC_OMS1/sysman/log/, found an ORA-14400 error. The MOS note 1493151.1, explains how to fix the issue by adding a new audit partition.
$ cd /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log/
$ view emoms.trc
java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition
The final step is to disable the DEBUG mode for your OMS, otherwise the log files can grow real big and the performance could be affected.
$ ./emctl set property -name log4j.rootCategory -module LOGGING -value "WARN, emlogAppender, emtrcAppender"
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
SYSMAN password:
Property log4j.rootCategory has been set to value WARN, emlogAppender, emtrcAppender for all Management Servers
OMS restart is not required to reflect the new property value
I hope this information is useful to you next time you are troubleshooting an OEM 12c issue.
In order to get more details about the error, I decided to enable DEBUG mode for the OMS and reproduce the error. This is what I did to enable DEBUG mode.
$ cd /u01/app/oracle/oms/oms/bin
$ ./emctl set property -name log4j.rootCategory -value "DEBUG, emlogAppender, emtrcAppender" -module logging
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
SYSMAN password:
Property log4j.rootCategory has been set to value DEBUG, emlogAppender, emtrcAppender for all Management Servers
OMS restart is not required to reflect the new property value
After enabling DEBUG mode, I reproduced the error several times using the console. I also wrote down the approximate time of the error, just to easy the search in the log file. Searching in the emoms.trc file located under /em/EMGC_OMS1/sysman/log/, found an ORA-14400 error. The MOS note 1493151.1, explains how to fix the issue by adding a new audit partition.
$ cd /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log/
$ view emoms.trc
java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition
The final step is to disable the DEBUG mode for your OMS, otherwise the log files can grow real big and the performance could be affected.
$ ./emctl set property -name log4j.rootCategory -module LOGGING -value "WARN, emlogAppender, emtrcAppender"
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
SYSMAN password:
Property log4j.rootCategory has been set to value WARN, emlogAppender, emtrcAppender for all Management Servers
OMS restart is not required to reflect the new property value
I hope this information is useful to you next time you are troubleshooting an OEM 12c issue.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/35489/viewspace-1874138/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle 12c OEM Cloud Control OMS安裝OracleCloud
- Troubleshoot an ORA-7445 Error Using the ORA-7445 Lookup ToolError
- windows下部署12c oms agent 及清除agentWindows
- Oracle 12c Rac Set Archive ModeOracleHive
- oracle OEM中 Accessibility Mode disable解決辦法Oracle
- How to debug release mode program in visual studio
- 使用_smu_debug_mode瞭解undo tablespace
- Connect SQL Server from Linux Client using Windows Authentication and troubleshoot stepsSQLServerLinuxclientWindows
- _smu_debug_mode在AUM下的應用
- OEM GC11G OMS不能發現主機的問題解決GC
- rpm包 手工安裝OEM 12c agent
- Oracle 12c: Recover tables using RMANOracle
- 【GC】OEM Grid Control 11gR1部署之OMS部分GC
- Oracle 12c OEM Cloud Control AGENT 安裝OracleCloud
- Using silent mode to install GC 10.2.0.1 and upgrade GC to 10.2.0.5 by Using an Existing Database onGCDatabase
- git - problemsGit
- OMS
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 3Cloud
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 2Cloud
- EM 12c Cloud Control - Agent Unreachable : Received Key Mismatch from OMS - 1Cloud
- EM 12c 修改 EMGC_OMS1的 java heap size (JVM大小) - 2GCJavaJVM
- EM 12c 修改EMGC_OMS1的 java heap size (JVM大小) - 1GCJavaJVM
- Week 11 Problems
- Week 4 Problems
- Oracle 12C Transport a Database to a Different Platform Using Backup SetsOracleDatabasePlatform
- Debug a Server–Side Rendered SAP Spartacus Storefront Using Chrome Dev ToolsServerIDEChromedev
- EM 12c推送Agent出錯 - OMS_HOST and EM_UPLOAD_PORT is not availableAI
- Using Silent Mode to Install Oracle Enterprise Manager Grid Control 10.2.0.1.1 Using an Existing DaOracle
- EM Cloud Control 12c OMS 及 OMA 都需要部署Plug-in的原因 - 2Cloud
- EM Cloud Control 12c OMS 及 OMA 都需要部署Plug-in的原因 - 1Cloud
- Install 11.2/12.1 DB/Client in Silent Mode without Using Response File _885643.1client
- How to Troubleshoot Grid Infrastructure Startup IssuesASTStruct
- 12C Duplicating a Database to a Remote Host by Using Backup-based DuplicationDatabaseREM
- Seed Database (pdb$seed) - Read Write OR Read Only Mode in Oracle Database 12cDatabaseOracle
- Oracle Database Link ProblemsOracleDatabase
- 【OEM】OEM安裝維護
- 配置OMS筆記筆記
- Using Silent Mode to Install Oracle Enterprise Manager Grid Control 10.2.0.1.1Oracle