EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet

I ran into an issue where agent was not uploading the xmls to the OMS server. emctl upload fails with the error "EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..."

To resolve the issue try the following.
Check if the host is able to communicate with the OMS by using telnet as mentioned below. If you punch in "^]" escape sequence, you will receive Apache version that OMS is running currently on the port 4890.

$ telnet testsrvoms.msudhan.com 4890
Trying xx.xx.xx.xx...
Connected to testsrvoms.msudhan.com.
Escape character is '^]'.
^]

--

$ emctl secure agent agent
Oracle Enterprise Manager 10g Release 10.2.0.2.0.
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Agent successfully stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Done.
Check if HTTPS Upload URL is accessible from the agent... Done.
Configuring Agent for HTTPS in CENTRAL_AGENT mode... Done.
EMD_URL set in /agent10g/agent10g/sysman/config/emd.properties
Securing agent... Successful.
Agent successfully restarted... Done.

--

ORA-12547 while creating ASM instance using DBCA in 10gR2

ORA-12547 - TNS Lost Contact while creating ASM instance using DBCA.

Cause: Seems like Oracle Binaries were not relinked properly.

[oracle@testsrv01 ~]$ ldd `which oracle`
lddlibc4: cannot read header from `/oracle01/oracle/product/10.2.0/db_1/bin/oracle'
[oracle@testsrv01 ~]$

Fix: shutdown the listener and kill any stale processes referring to the executable of your ORACLE_HOME and

cd $ORACLE_HOME/bin
relink all

and restart the DBCA. It should go through

Need to Kill j000 process to shutdown the database after upgrade from 8.1.7.4 to 9.2.0.8.

This is a common problem after the upgrade. One important point to remember is to disable all the schedules for dbms jobs before kicking off the upgrade and enable the schedule after the uprade is over. Alternatively job_queue_processes parameter can be set to '0'.

You see following symptoms in the alert log.

-- Clip --

Active call for process 21244 user 'oracle' program 'oracle@hostname (J000)'
SHUTDOWN: waiting for active calls to complete.

-- End Clip --

Trace File of J000 process shows

-- Clip --

Unix process pid: 13302, image: oracle@hostname (J000)

*** SESSION ID:(95.9333) 2007-12-14 22:50:52.282
OPIRIP: Uncaught error 1089. Error stack:
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-00448: normal completion of background process

-- End Clip --


Reference - Metalik Note:342805.1