Failed to Validate the XML Content, 'SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's....

Файл, в котором надо менять согласно решения - лежит тут:

C:\oracle\middleware\Oracle_ODI1\oracledi\client\odi\bin

SYMPTOMS

On : 11.1.1.6.0 version, Product installation

When starting the SOA server you get the warning below in the logs

2012-09-21 14:17:44,482 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' WARN oracle.jps.common Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: line 2 column 272.

2012-09-21 14:17:53,549 JMX FRAMEWORK Runtime MBeanServer MBean registration thread WARN oracle.jps.common Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: line 2 column 272 of file:/u01/app/oracle/admin/soa_domain/mserver/soa_domain/config/fmwconfig/mbeans/../jps-config.xml.

CHANGES

 You have recently upgraded from SOA 11.1.1.5 to SOA 11.1.1.6 and started seeing the error after the upgrade

CAUSE

During the upgrade the file jps-config.xml was not altered to contain the correct schemaLocation attribute for the root element jpsConfig.
A correct schemaLocation attribute for SOA version 11.1.1.6 should be set to
"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd jps-config-11_1.xsd"

see below

<?xml version="1.0" encoding="UTF-8" standalone='yes'?>
<jpsConfig xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd jps-config-11_1.xsd" schema-major-version="11" schema-minor-version="1">

In your case you have a SOA 11.1.1.6 upgraded from SOA 11.1.1.5, where the file soa_domain/aserver/soa_domain/config/fmwconfig/jps-config.xml exhibits no file name in the schemaLocation attribute of root element jpsConfig:

<?xml version="1.0" encoding="UTF-8" standalone='yes'?>
<jpsConfig xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd" schema-major-version="11" schema-minor-version="1">

Analyzing and comparing the soa_domain/aserver/soa_domain/config/fmwconfig/jps-config.xml file from two pristine installations, one of version 11.1.1.5 and one of version 11.1.1.6, we can conclude the following:

1. SOA 11.1.1.5 has the schemaLocation defined as

"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"

2. SOA 11.1.1.6 has the schemaLocation defined as

"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd jps-config-11_1.xsd"

3. Thus the file name is not needed in SOA 11.1.1.5
4. Further, editing your SOA 11.1.1.6 jps-config.xml file to contain the file name in the schemaLocation attribute of element jpsConfig does eliminate the warning.

SOLUTION

1. Edit file soa_domain/aserver/soa_domain/config/fmwconfig/jps-config.xml
2. Change attribute schemaLocation of root element jpsConfig
from

"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"

 to

"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd jps-config-11_1.xsd"

3. Save
4. Restart the server
5. Confirm you no longer see the warning in the log files