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.
Main Topics
Browse All TopicsWe 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>/
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,hea
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
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?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: MikeOM_DBAPosted on 2009-08-03 at 11:51:34ID: 25007273
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.
Select allOpen in new window