After you patch your Oracle Fusion Middleware environment, some applications still show the version number from previous releases. For example, after you patch Oracle WebLogic Server 10.3.4 to the latest release, the version number is still shown as 10.3.4.
If you are running Fusion Middleware products that use the Metadata Services schema (MDS) and your Fusion Middleware products are older than 11g Release 1 (126.96.36.199.0), the schema version number for the MDS schema in Enterprise Manager will be the previous release number, even if you have updated the MDS schema to 11g Release 1 (188.8.131.52.0).
After you patch your existing Oracle Business Intelligence (BI) software to 11g Release 1 (184.108.40.206.0), some Oracle BI components (for example, Oracle BI Publisher or Oracle RTD) will still show the version number from your previous release when viewed using Oracle Enterprise Manager.
In 11g Release 1 (220.127.116.11.0), the odi-sdk-ws application was updated to introduce a version number. If you are upgrading the odi-sdk-ws application to 11g Release 1 (18.104.22.168.0) from any previous release, this version number must be added to the config.xml file prior to starting the Administration server or Managed Servers in the domain.
The work arounds are to either use the Internet Explorer browser, or manually modify the INSTANCE_HOME/config/OHS/instance_name/httpd.conf\\config\\OHS\\instance_name\\httpd.conf file and change the ServerName entry to include the port number. For example: 153554b96e