Applies to:

Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]
Information in this document applies to any platform.

Symptoms

11.1.0.1 Agent fails to upload to OMS with following error message :

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors.

Cause

The repository URL is incorrect.

The REPOSITORY_URL and the EMD_URL for the Agent should use the same protocol : HTTP or HTTPS.
Furthermore, the REPOSITORY_URL should contain the correct OMS hostname, and the appropriate OMS port (HTTP or HTTPS port).

REPOSITORY_URL and EMD_URL used by the Agent can be seen from the /sysman/config/emd.properties or in the output of the
/bin/emctl status agent command.

From /sysman/config/emd.properties :

EMD_URL=http://agent.machine.com:3872/emd/main
REPOSITORY_URL=https://oms.machine.com:7799/em/upload

From /bin/emctl status agent :

Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /oracle/product/em/agent11g
Agent binaries : /oracle/product/em/agent11g
Agent Process ID : 811074
Parent Process ID : 983100
Agent URL : http://agent.machine.com:3872/emd/main/
Repository URL : https://oms.machine.com:7799/em/upload/
Started at : 2010-11-08 13:21:43
Started by user : oracle
Last Reload : 2010-11-08 13:21:43
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 68
Size of XML files pending upload(MB) : 33.09
Available disk space on upload filesystem : 16.71%
Last attempted heartbeat to OMS : 2010-11-08 13:37:20
Last successful heartbeat to OMS : unknown
---------------------------------------------------------------
Agent is Running and Ready

=> The REPOSITORY_URL is using HTTPS and the EMD_URL is using HTTP.

Both should be HTTPS if the agent was secured successfully.
=> Furthermore, the port specified in the REPOSITORY_URL is incorrect.
This is not the correct HTTPS upload port.

To check this, you need to get the OMS HTTPS upload secured port, launch this command on the OMS machine :

% cd /bin
./emctl status oms -details

The following output is shown :

Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : omsmachine.domain
HTTP Console Port : 7788
HTTPS Console Port : 7799
HTTP Upload Port : 4889
HTTPS Upload Port : 4900
OMS is not configured with SLB or virtual hostname
Agent Upload is unlocked.
OMS Console is unlocked.
Active CA ID: 1

The correct HTTPS upload port is 4900.
The correct HTTP upload port is 4889.

Solution

Important : This note only applies in the case described in the CAUSE section => REPOSITORY_URL is incorrect

1. Unsecure the Agent :

$/bin/emctl unsecure agent

Note : If it fails for any reason (OMS locked...), continue anyway with next steps.

2. Stop the Agent and Backup the /sysman/config/emd.properties file.

3. Check REPOSITORY_URL parameter

Ensure that the emctl unsecure agent command has changed (in case of success of the command)
- the protocol from HTTPS to HTTP
- the port was changed from the HTTPS upload secure port to the HTTP unsecured upload port.

To get the HTTP and HTTPS upload ports, you need to launch that command :

% cd /bin
./emctl status oms -details

The following output is shown :

Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : omsmachine.domain
HTTP Console Port : 7788
HTTPS Console Port : 7799
HTTP Upload Port : 4889
HTTPS Upload Port : 4900
OMS is not configured with SLB or virtual hostname
Agent Upload is unlocked.
OMS Console is unlocked.
Active CA ID: 1

The correct HTTPS upload port is 4900.
The correct HTTP upload port is 4889.

Important :
- If the unsecure agent command has failed for any reason in step 1,
or
- if the REPOSITORY_URL parameter does not reflect the attended HTTP protocol, and HTTP upload port's value

=> then proceed with the manual update (see step 4 ).
Otherwise, go on Step 5.

4. Update the /sysman/config/emd.properties file, so that :

- the same HTTP protocol is used for both properties EMD_URL and REPOSITORY_URL,
and
- appropriate HTTP upload port is specified in REPOSITORY_URL :

So, change REPOSITORY_URL parameter :

From
https://oms.machine.com:/em/upload
to

http://oms.machine.com:/em/upload

Examples :
1) HTTPS Upload port specified was not the correct port and HTTPS protocol is used in REPOSITORY_URL and not in EMD_URL :

Change REPOSITORY_URL From
https://oms.machine.com:7799/em/upload
to
http://oms.machine.com:4889/em/upload

2) Correct HTTPS upload secured port is used but, HTTPS is used in REPOSITORY_URL and not in EMD_URL property :

Change REPOSITORY_URL From
https://oms.machine.com:4890/em/upload
to
http://oms.machine.com:4889/em/upload

5. Check the OMS Hostname

Ensure that the OMS Hostname is well exactly the same as returned in the emctl status oms -details command in Console Server Host parameter.

For example, if the Console Server Host parameter has the hostname in the short format (without domain), then the REPOSITORY_URL parameter in emd.properties should also refer to the OMS hostname in the same manner.
If the OMS hostname is in the long format (with domain name), then it should be reflected in REPOSITORY_URL.

6. Check emdWalletSrcUrl parameter

Ensure that the emdWalletSrcUrl parameter contains well the correct OMS hostname (same check as step5), and the correct HTTPS upload port (collected in step 3 using emctl status oms -details command ):

emdWalletSrcUrl=https://oms.machine.com:/em/wallets/emd

Example :
emdWalletSrcUrl=https://oms.machine.com:4890/em/wallets/emd

7. Re-secure the agent, then test the status and the upload commands to ensure that everything is working well :

     $cd /bin
     $./emctl secure agent
     $./emctl upload
     $./emctl status agent

Note: For Windows platform, the commands are the same, launched from DOS Windows command window.

Note :
The same issue happens for 10g Agents. The solution is similar, please refer and apply the 10g note :
Document:422922.1 Agent Upload to OMS Fails if the OMS is Locked in Secure Mode and Agent is not Secured