Unable to upload EM repository configuration workaround when Oracle EMCA configuration Dbcontrol

System environment:

Windows Server R2 Ent. 64bit

When configuring Dbcontrol with EMCA, it prompts: "Critical: Error uploading configuration data to the repository", which is caused by IPV6. The network card configuration in the IPv6 disabled still not, and then query the data to know the need to modify the Hosts file under drivers/etc/.

Failure phenomena:

C:\USERS\ADMINISTRATOR&GT;EMCA-config Dbcontrol DBEMCA starts at .-9-4  One:Wuyi: -EM Configuration Assistant,11.2.0.0.2Official Edition Copyright (c)2003,2005, Oracle. All rights reserved. Enter the following information: Database SID:ORCL listener Oracle_home [E:\app\Administrator\product\11.2.0\dbhome_2]:sys User's password: dbsnmp password for User: Sysman user's password: e-mail address of notification (optional): Notification of outgoing (SMTP) server (optional):-----------------------------------------------------------------The following settings have been specified for the database Oracle_home ..... E:\app\Administrator\product\11.2.0\dbhome_2 The local hostname ... ...... BT-The DB Listener Oracle_home ....... .....  E:\app\Administrator\product\11.2.0\dbhome_2 Listener port number ....... .....1521database SID ... e-mail address of the ORCL notification ....... ............ Notification of the outgoing (SMTP) server ..... .....-----------------------------------------------------------------whether to continue? [Yes (Y)/No (N)]: y .-9-4  One:Wuyi: WuOracle.sysman.emcp.EMConfig Perform info: Logging this action to E:\app\Administrator\cfgtoollogs\emca\orcl\emca_2017_09_04_ 11_51_26.log.  .-9-4  One: the:xxoracle.sysman.emcp.EMReposConfig uploadconfigdatatorepository Info: Uploading configuration data to the EM data archive (this operation may take some time) ... .-9-4  One: -: -Oracle.sysman.emcp.EMReposConfig invoke information: For more information, see E:\app\Administrator\cfgtoollogs\emca\orcl\emca_repos_ Config_< dates >log files in the. Log.  .-9-4  One: -: -oracle.sysman.emcp.EMReposConfig invoke severity: An error occurred while uploading configuration data to the repository  .-9-4  One: -: -Oracle.sysman.emcp.EMConfig perform critical: Error uploading configuration data to the repository for more information, see E:\app\Administrator\cfgtoollogs\ Log files in the Emca\orcl\emca_2017_09_04_11_51_26.log. The configuration could not be completed. For more information, see log files in E:\app\Administrator\cfgtoollogs\emca\orcl\emca_2017_09_04_11_51_26.log. 

This opens the cmd Command window to ping the local hostname, which appears as follows:

C:\users\administrator>ping bt-db is pinging BT-db [::1  bytes of data: From::1 Reply: Time <1ms from::1 reply: Time <1ms::1  Ping statistics:    2 2 0 (0 lost), estimated time to round trip (in milliseconds):    = 0ms, maximum = 0ms, average = 0ms

Modify the Hosts file to add a line of content:

10.13. 16.34    Bt-db

Then, by pinging the local host name, verify that the host has not been accessed by means of IPv6.

C:\users\administrator>ping bt-db is pinging BT-db [10.13.16.34] has +bytes of data: from10.13.16.34The reply: byte = +Time <1ms ttl= -from10.13.16.34The reply: byte = +Time <1ms ttl= -10.13.16.34Ping Statistics: packets: Sent=2, received =2, missing =0(0%lost), estimated time to round trip (in milliseconds): Shortest= 0ms, maximum = 0ms, average = 0ms

Finally, reconfigure the Dbcontrol repository.

C:\USERS\ADMINISTRATOR&GT;EMCA-config Dbcontrol DBEMCA starts at .-9-4  One: $: -EM Configuration Assistant,11.2.0.0.2Official Edition Copyright (c)2003,2005, Oracle. All rights reserved. Enter the following information: Database SID:ORCL listener Oracle_home [E:\app\Administrator\product\11.2.0\dbhome_2]:sys User's password: dbsnmp password for User: Sysman password for User: Sysman user's password: e-mail address of notification (optional): Notification of outgoing (SMTP) server (optional):-----------------------------------------------------------------The following settings have been specified for the database Oracle_home ..... E:\app\Administrator\product\11.2.0\dbhome_2 The local hostname ... ...... BT-The DB Listener Oracle_home ....... .....  E:\app\Administrator\product\11.2.0\dbhome_2 Listener port number ....... .....1521database SID ... e-mail address of the ORCL notification ....... ............ Notification of the outgoing (SMTP) server ..... .....-----------------------------------------------------------------whether to continue? [Yes (Y)/No (N)]: y .-9-4  One: $: $Oracle.sysman.emcp.EMConfig Perform info: Logging this action to E:\app\Administrator\cfgtoollogs\emca\orcl\emca_2017_09_04_ 11_57_20.log.  .-9-4  One: $: $oracle.sysman.emcp.EMReposConfig uploadconfigdatatorepository Info: Uploading configuration data to the EM data archive (this operation may take some time) ... .-9-4  One: -: Aoracle.sysman.emcp.EMReposConfig Invoke info: The configuration data was uploaded successfully  .-9-4  One: -: theoracle.sysman.emcp.util.DBControlUtil configuresoftwarelib information: The Software Library has been configured successfully.  .-9-4  One: -: theOracle.sysman.emcp.EMDBPostConfig configuresoftwarelibrary Info: Provisioning profile is being deployed ... .-9-4  One: -: -Oracle.sysman.emcp.EMDBPostConfig configuresoftwarelibrary Info: Provisioning file deployment was successful.  .-9-4  One: -: -Oracle.sysman.emcp.util.DBControlUtil securedbconsole Info: Protecting Database Control (This operation may take some time) ... .-9-4  One: -: tooracle.sysman.emcp.util.DBControlUtil securedbconsole Information: Database Control has been successfully protected.  .-9-4  One: -: toOracle.sysman.emcp.util.DBControlUtil startoms Info: Starting Database Control (This operation may take some time) ... .-9-4  One: -: -oracle.sysman.emcp.EMDBPostConfig performconfiguration Info: Database Control started successfully .-9-4  One: -: -oracle.sysman.emcp.EMDBPostConfig performconfiguration Information:>>>>>>>>>>> the Database Control URL is https://bt-db:1158/em <<<<<<<<<<< .-9-4  One: -: +oracle.sysman.emcp.EMDBPostConfig Invoke Warning:WARNING ************************The management repository is placed in safe mode, in which Enterprise Manager data is encrypted. The encryption key has been placed in file E:/app/administrator/product/11.2.0/dbhome_2/bt-db_orcl/Sysman/config/the Emkey.ora. Be sure to back up this file, because if this file is lost, the encrypted data will not be available. ***********************************************************configuration of Enterprise Manager completed successfully EMCA end .-9-4  One: -: +

The following content refers to other user's troubleshooting experience:

Find an explanation for this problem on OTN:

cause
The Windows machine was in a Active Directory and is using IPV6. When the short hostname is pinged, it's resolved via the fully qualified hostname to an IPV6 (ISATAP) address eg:-


Ping Machine1

Pinging machine1.uk.oracle.com [fe80::f1bb:2ed:4d5a:1732] with + bytes of data:
Reply from Fe80::f1bb:2ed:4d5a:1732:time<1ms

Dbconsole 11.2 is built around Grid Control 10.2.0.4 and so are not IPV6 compliant. Grid Control 11.1.0.1 is IPV6 compliant. The version of Dbconsole which is built around Grid Control 11.1.0.1 would be IPV6 compliant. (the version which dbconsole is built round are shown in the output of Emctl status agent).



Solution
ADD entries into the host file, to force IPv4 style resolution:-

1) Edit the windows\system32\drivers\etc\hosts file

2) Add an entry for the format:-

<ipaddress> <fully qualified hostname> <short hostname>

eg.

138.3.146.333 machine1.uk.oracle.com machine1

Now while pinging the short hostname, the IPv4 style IPAddress is returned.

Simple Explanation:

2008 by default with IPV 6 protocol resolution, ping hostname, it is resolved to IPV6 (ISATAP) address through full hostname

Example: Ping www.swsport.com

Dbconsole 11.2 Controls 10.2.0.4 around the grid, so IPV6 compatibility is not supported. Grid Control 11.1.0.1 is IPV6 compatible: (which dbconsole built-in version of the output emctl the status agent).

This means that the operating system uses IPV 6 to resolve the address, and your EM does need to IPV 4 to resolve the address. Workaround: Forcibly use IPV4 to resolve addresses

Unable to upload EM repository configuration workaround when Oracle EMCA configuration Dbcontrol