asked on

Oracle dbconsole generating core.hung files

We are having problems with Oracle dbconsole for a 10.2.0.4 database on Sun Solaris 10 64-bit platform. Core files starting with the name core.hung are being generated in the $ORACLE_HOME/<server_sid>/sysman/emd directory. Each of these core.hung files are around 30+MB in size and are being generated every 15 minutes or so and causing our system to run out of disk space. Here are excerpts from the emagent.trc file:

emagent.trc
2009-08-01 07:37:01 Thread 2016 ERROR upload: nmehursf_logError:lfiflu failed
2009-08-01 07:37:01 Thread 2016 ERROR upload: rawdata.dat rename failed
2009-08-01 07:37:01 Thread 2016 ERROR upload: rawdata.dat deleted, it will not be merged
2009-08-01 07:37:01 Thread 2016 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
2009-08-01 07:37:01 Thread 2016 ERROR engine: [oracle_database,SID01,health_check]:
nmeegd_GetMetricData failed : Instance Health Check initialization failed due to one of the following causes: the owner of the EM agent process is not same as the owner of the Oracle instance processes; the owner of the EM agent process is not part of the dba group; or the database version is not 10g (10.1.0.2) and above.
2009-08-01 07:37:01 Thread 2016 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
2009-08-01 07:37:01 Thread 2016 ERROR util.files: ERROR: nmeufos_new: failed in lfiopn on file: /<ORACLE_HOME>/<server_sid>/sysman/emd/agntstmp.txt.error - 24 (Too many open files)

We have disabled all HealthChecks and the owner of the EM process is the same as the database instance processes.

This problem is affecting our production environment. Has anyone encountered similar problems with dbconsole? What steps can we do to eliminate the core.hung files from being generated?

MikeOM_DBA

Th core.hung means that the process of writing a core dump, itself generated another core dump.
Besides finding a cause and solution to your other errors, you may want to set the following parameters to control the core dump size:
GIM-00105
Check this BUG :- 6439387.

background_core_dump =partial
max_dump_file_size={some small size, maybe 2M?}

Open in new window

dvrobins

ASKER

Thanks for the suggestion, that may alleviate our space problems by extending the time it takes to fill up the storage device while we're trying to solve the underlying issue.

ASKER CERTIFIED SOLUTION

dvrobins

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial