Home » RDBMS Server » Enterprise Manager » core.hung* files (Oracle 10.2.0.4, Solaris 10)
core.hung* files [message #358276] Mon, 10 November 2008 08:24 Go to next message
deepmachine
Messages: 80
Registered: August 2008
Location: United States
Member
Hi,
I am getting core.hung files in my $ORACLE_HOME/<host>_<instance_name>/sysman/emd file. Each file is 37M and consuming the disk space.

I have to simply delete files from $ORACLE_HOME/<host>_<instance_name>/sysman/log folder everyday to reclaim the space.

Upon looking at the log file "emagent.log" I noticed that EMAgent(s) stop and restart every now and then on node-2 for both of my databases.

A sample of log file is pasted below:
2008-11-08 03:47:01 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-08 03:47:08 Thread-1 EMAgent started successfully (00702)
2008-11-08 08:09:50 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-08 08:09:56 Thread-1 EMAgent started successfully (00702)
2008-11-08 12:32:38 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-08 12:32:45 Thread-1 EMAgent started successfully (00702)
2008-11-08 16:55:27 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-08 16:55:33 Thread-1 EMAgent started successfully (00702)
2008-11-08 21:18:16 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-08 21:18:22 Thread-1 EMAgent started successfully (00702)
2008-11-09 01:41:05 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-09 01:41:12 Thread-1 EMAgent started successfully (00702)
2008-11-09 06:03:55 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-09 06:04:01 Thread-1 EMAgent started successfully (00702)
2008-11-09 10:26:43 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-09 10:26:50 Thread-1 EMAgent started successfully (00702)
2008-11-09 14:49:32 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-09 14:49:39 Thread-1 EMAgent started successfully (00702)
2008-11-09 19:12:21 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-09 19:12:28 Thread-1 EMAgent started successfully (00702)
2008-11-09 23:35:10 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-09 23:35:17 Thread-1 EMAgent started successfully (00702)
2008-11-10 03:58:01 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-10 03:58:08 Thread-1 EMAgent started successfully (00702)
2008-11-10 08:20:51 Thread-1 Starting Agent 10.1.0.6.0 from /u01/app/oracle/product/10.2.0/db (00701)
2008-11-10 08:20:58 Thread-1 EMAgent started successfully (00702)


While looking at the emagent.trc file, I came to know that the shared memory region is corrupt. What does this mean?
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:17:39 Thread-682 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:17:54 Thread-683 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:18:09 Thread-687 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:18:24 Thread-690 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:18:39 Thread-691 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:18:54 Thread-694 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:19:09 Thread-697 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:19:24 Thread-699 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:19:39 Thread-701 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial


I looked for "GIM-00105", but couldn;t find significant information.

Your help is appreciated. Thanks in advance!


[Updated on: Mon, 10 November 2008 08:35]

Report message to a moderator

Re: core.hung* files [message #358287 is a reply to message #358276] Mon, 10 November 2008 09:39 Go to previous messageGo to next message
tahpush
Messages: 961
Registered: August 2006
Location: Stockholm/Sweden
Senior Member

Check Metalink
Re: core.hung* files [message #434700 is a reply to message #358276] Thu, 10 December 2009 05:11 Go to previous messageGo to next message
azimathul9
Messages: 1
Registered: December 2009
Junior Member
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:18:54 Thread-694 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:19:09 Thread-697 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:19:24 Thread-699 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
2008-11-10 09:19:39 Thread-701 ERROR fetchlets.healthCheck: GIM-00105: Shared memory region is corrupted.
GIM-00092: OS failure occurred at: skgpmaterial
Re: core.hung* files [message #434711 is a reply to message #434700] Thu, 10 December 2009 05:27 Go to previous message
Michel Cadot
Messages: 59279
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
GIM-00105: Shared memory region is corrupted.
 *Document: NO
 *Cause:  Shared memory region was corrupted or inconsistent.
 *Action: Restart the Oracle RDBMS instance. If the problem persists,
          contact Oracle Support Services.

Regards
Michel
Previous Topic: DBSNMP login Issue
Next Topic: Oracle Options
Goto Forum:
  


Current Time: Tue Sep 30 18:10:30 CDT 2014

Total time taken to generate the page: 0.13300 seconds