This discussion is archived
3 Replies Latest reply: Nov 9, 2012 7:48 AM by sbarber_uk RSS

EM12c Agent getting DISK FULL status

David Ooi Newbie
Currently Being Moderated
Hi Everyone
I been getting collection DISK FULL in one of our agent even though the agent path still have 90% of freespace.

Oracle Enterprise Manager 12c Cloud Control
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Agent Version :
OMS Version :
Protocol Version :
Agent Home : /opt/oracle/agent/agent12c/agent_inst
Agent Binaries : /opt/oracle/agent/agent12c/core/
Agent Process ID : 585
Parent Process ID : 431
Agent URL : https://server:3880/emd/main/
Repository URL : https://OMSserver:4901/empbs/upload
Started at : 2012-06-28 16:30:18
Started by user : processoemagent
Last Reload : (none)
Last successful upload : 2012-11-07 04:16:59
Last attempted upload : 2012-11-07 04:16:59
Total Megabytes of XML files uploaded so far : 2,425.38
Number of XML files pending upload : 4,901
Size of XML files pending upload(MB) : 2.94
Available disk space on upload filesystem    : 90.09%
*Collection Status                            : [DISK_FULL]*
Last attempted heartbeat to OMS : 2012-11-08 19:52:30
Last successful heartbeat to OMS : 2012-11-08 19:52:30

Agent is Running and Ready

When i edit the gcagent.log for more detail , i found the warning message as below
*2012-11-07 04:19:36,179 [233:E22D17A1:GC.Executor.0 ( File Status)] WARN - Upload system can't accept inbound message; can't purge*
*2012-11-07 04:19:36,205 [233:E22D17A1] WARN - Upload failure File Status*
oracle.sysman.gcagent.upload.UploadException: Upload system full - can't accept more data
at oracle.sysman.gcagent.upload.UploadManager.send(
at oracle.sysman.gcagent.upload.UploadManager.send(
at oracle.sysman.gcagent.upload.UploadManager.send(
at oracle.sysman.gcagent.upload.UploadManager.uploadToDataChannel(
at oracle.sysman.gcagent.metadata.impl.collection.CollectionItem$CollectionItemTask.uploadIndividually(
at oracle.sysman.gcagent.metadata.impl.collection.CollectionItem$
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler$ReschedulingHelper$
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler$ReschedulingHelper$
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall(
at oracle.sysman.gcagent.task.TaskFutureImpl$
at java.util.concurrent.FutureTask$Sync.innerRun(
at oracle.sysman.gcagent.task.TaskFutureImpl.run1(
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
at java.util.concurrent.ThreadPoolExecutor$
at oracle.sysman.gcagent.util.system.GCAThread$

How do i clear the DISK FULL status?

  • 1. Re: EM12c Agent getting DISK FULL status
    mnazim Expert
    Currently Being Moderated
    First Please check the space in your machine
  • 2. Re: EM12c Agent getting DISK FULL status
    David Ooi Newbie
    Currently Being Moderated
    Here is the diskspace

    Filesystem Size Used Avail Use% Mounted on
    8.6G 743M 7.4G 9% /
    5.7G 2.0G 3.4G 38% /usr
    4.8G 419M 4.1G 10% /var
    4.8G 768M 3.8G 17% /var/log
    3.8G 164M 3.5G 5% /tmp
    3.8G 2.5G 1.2G 68% /opt
    3.8G 694M 3.0G 19% /home
    /dev/sdb1 99M 33M 61M 35% /boot
    tmpfs 37G 268M 37G 1% /dev/shm
    *9.9G 1000M 8.9G 10% /opt/oracle/agent*

    10% used 8.9G still available

    Edited by: David Ooi on 09-Nov-2012 04:31
  • 3. Re: EM12c Agent getting DISK FULL status
    sbarber_uk Newbie
    Currently Being Moderated
    I have had this issue before, it might not be [DISK FULL]. It is a generic message that has been fixed in EM12cR2.

    We limit the maximum size of the upload area.

    UploadMaxDiskUsedPct default is 98%
    UploadMaxNumberXML default = 5000

    2% of 5000 is 100 or 5000 - 100 = 4900 (hence at 4901 your in violation of the number of files)


  • Correct Answers - 10 points
  • Helpful Answers - 5 points