While trying to add an additional OMS to the current OEM 13.3 GCDomain using the provisioning console there’s an error in the Install homes step. The error contains the following message: Caused by: oracle.sysman.oii.oiif.oiifb.OiifbEndIterateException: oracle.sysman.oii.oiif.oiifb.OiifbEndIterateException: SEVERE:Values for the following variables could not be obtained from the command line or response file(s): MYORACLESUPPORT_USERNAME(MyOracleSupportUsername) Silent install… Continue reading Unable to Extend OEM 13.3 Domain to Add an Additional OMS
I recently had an issue in OEM 12c while creating a Metric Extension that was returning more than 5000 records. In OEM 12c versions 184.108.40.206 and 220.127.116.11 there a flood control mechanism in order to limit the maximum number of rows for a metric. You can also verify this in the agent_inst/sysman/log/gcagent.log file:2018-10-08 13:38:50,330 [66:F119EDFE:GC.Executor.1… Continue reading OEM 12c/13c Metric Extension – Collection Result Maximum Flood Control
There’s an issue in EBS 12.2 and database 18.104.22.168 versions related to Materialized Views. While executing ADOP (prepare, apply, finalize or cutover) phases, the cycle could fail due to an ORA-600 : internal error code, arguments: [kqllod:no stub for dependency parent] error.After working with Oracle, they provided information about BUG 27883586 related to MView Refresh or… Continue reading EBS ADOP Phase Failing Due to ORA-600 Error
I recently had an issue with an OEM agent 22.214.171.124 version running on Solaris. Looks like there’s a Java related bug which causes the agent to consume high amounts of CPU in the box. But the interesting part is this only happens when Listeners are being monitored. If you blackout the Listener targets this stops.If… Continue reading OEM 12c Agent Crashing on Solaris
How many times we have calls from users complaining about their process that failed due to an ORA-01555 error?We know that if the queries are not well tuned and they modify a lot of data, the image held in the UNDO Tablespace could not be consistent with the real data. But have you ever seen… Continue reading ORA-01555 query duration 0 seconds with Dataguard
Over the weekend one of the databases hung due to the flash recovery area was 100% full. I noticed one J001 process consuming significant CPU and I/O resources. Turns out this process was the automatic segment advisor job that runs on the weekend maintenance window.The SQL executed was something like:CREATE TABLE .dbms_tabcomp_temp_uncmpTABLESPACE NOLOGGINGASSELECT /*+ FULL(.)… Continue reading Compression Advisor killed my database!