Collection Status : Disabled by Upload Manager & EMD upload error: uploadXMLFiles Skipped:: OMS version not checked yet

I was getting “Collection Status : Disabled by Upload Manager” on one of my EM targets. Now, I prefer to have monitoring and DBA tasks done the old school way, with scripts and all. But we have EM deployed for all targets and this is something that I had to fix.

I started by doing a “emclt upload” and see what it gave. I got the error “EMD upload error: uploadXMLFiles Skipped:: OMS version not checked yet.” . So I went back to MOS to see if  there was any help there. Note 1086343.1 is a good reference.

Upon looking at the emagent log and trace files, I saw that there were connection problems to the OMS repository. Turns out that the targets.xml file (which has details on the various monitored components on any host) was messed up.

To create a new targets.xml file, I took backups and ran the following:

emctl stop agent  --> stop the agent
agentca -d        --> force a discovery of the targets on the host

This took a while, but created a new targets.xml which has all details. I Edited the file to have only the databases that I wanted EM to monitor and removed the rest. The targets.xml is by default created without the password for the connect user (DBSNMP). So  add these two lines for each target (DB). make sure that encrypted is set to FALSE. On the next agent startup, these will be automatically encrypted (username & pwd)

<Property NAME="password" VALUE="password" ENCRYPTED="FALSE"/>

Once this was done, I started the agent up using emctl start agent and all was good.

Mount NTFS drives in OEL6

download the *.tgz file from

export MAKE=’/usr/bin/gmail -i’
make install

fdisk -l to see your device handle will be like /dev/sd

mkdir -p /mnt/newmount1

mount -t ntfs-3g /dev/sda /mnt/newmount1

2012 in review

The stats helper monkeys prepared a 2012 annual report for this blog.

Here’s an excerpt:

600 people reached the top of Mt. Everest in 2012. This blog got about 7,200 views in 2012. If every person who reached the top of Mt. Everest viewed this blog, it would have taken 12 years to get that many views.

Click here to see the complete report.

OPATCH_JAVA_ERROR = OPatch Exception While Trying to Check for Mini Patchset

We were applying a pre req patch before upgrade from 12.1.1 to 12.1.3. After sourcing the environment , I did OPATCH lsinventory and it gave expected output. After that when we applied OPATCH apply, it errored out with the message
OPATCH_JAVA_ERROR=OPatch Exception While Trying to Check for Mini Patchset

Looking in My Oracle Support did not give much clue. The Note ID 971783.1 OPATCH_JAVA_ERROR=OPatch Exception While Trying to Check for Mini Patchset’ while applying patch using opatch This note suggested removing the ‘&’ and ‘<‘ character from the bug description section in the /etc/config/inventory file. However, my inventory file did not have any such characters except the XML tags, which I couldn’t remove.

Our Solution

It was then that I noticed that the patch was unzipped into a path which had a space in the folder name. We renamed the folder to a simpler name, without spaces and the patch proceeded normally.