This discussion is archived
2 Replies Latest reply: Jan 18, 2013 5:49 AM by Kalyan Pasupuleti-Oracle RSS

Schema validation errors with WebLogic domain

886629 Newbie
Currently Being Moderated
I am trying to start-up a WebLogic 10.3 domain and I keep getting these errors:

Schema validation errors while parsing C:\bea10\user_projects\domains\main\config\config.xml - Invalid xsi:type qname: 'ext:database-authenticatorType' in element realm@http://www.bea.com/ns/weblogic/920/domain>
Schema validation errors while parsing C:\bea10\user_projects\domains\main\config\config.xml - C:\bea10\user_projects\domains\main\<unknown>:15:9: error: failed to load java type corresponding to t=database-authenticatorType@http://www.bea.com/ns/weblogic/90/security/extension>
Schema validation errors while parsing C:\bea10\user_projects\domains\main\config\config.xml - Invalid xsi:type qname: 'ext:license-authenticatorType' in element realm@http://www.bea.com/ns/weblogic/920/domain>
Schema validation errors while parsing C:\bea10\user_projects\domains\main\config\config.xml - C:\bea10\user_projects\domains\main\<unknown>:19:9: error: failed to load java type corresponding to t=license-authenticatorType@http://www.bea.com/ns/weblogic/90/security/extension>
0362> <Server failed. Reason: [Management:141245]Schema Validation Error in C:\bea10\user_projects\domains\main\config\config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>


This only started happening today. The same domain was working fine yesterday. Anybody know what these errors mean?

Edited by: 883626 on Sep 6, 2011 3:13 PM
  • 1. Re: Schema validation errors with WebLogic domain
    985623 Newbie
    Currently Being Moderated
    Did you find a solution to this problem? It's happening for me now.

    Cheers
  • 2. Re: Schema validation errors with WebLogic domain
    Kalyan Pasupuleti-Oracle Expert
    Currently Being Moderated
    Hi,

    you can try these options.


    1.- Save a backup of the 10.3.0.0 domain.

    2.- Look for the config.xml of the 10.3.0.0 domain under DOMAIN_HOME/config/config.xml

    3.- Comment out (or remove) the lines containing security providers configuration from the 10.3.0.0 config.xml. e.g.:

    <sec:authentication-provider xsi:type="ext:database-authenticatorType">
    <sec:name>myrealmDatabaseAuthenticator</sec:name>
    <sec:control-flag>REQUISITE</sec:control-flag>
    </sec:authentication-provider>
    <sec:authentication-provider xsi:type="ext:license-authenticatorType">
    <sec:name>myrealmLicenseAuthenticator</sec:name>
    <sec:control-flag>REQUISITE</sec:control-flag>
    </sec:authentication-provider>

    4.- Save the file.

    5.- Proceed with the Upgrade Domain Wizard (make sure a full backup has been made).

    6.- Put the extracted lines back in upgraded domain's config.xml

    7.- Change all URIs showing:
    http://www.bea.com/ns/weblogic/90/security/extension
    to this:
    http://xmlns.oracle.com/weblogic/security/extension

    8.- Save the changes and run normally.


    Regards,
    Kal

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points