Schema extension problem

Hi,
I have installed a new domain with NSM. The 'NSM Schema Utility' is showing:
Screenshot.png
But in the NSM Admin I have the message: "Schema Not Extended"
Can I verify with for ex. the mmc 'Active Directory Schema' if the all required extensions are done? Or is it only a problem with the NSMA which doesn't detect correctly the extension?
Best regards,
Christian

Christian,
What's the domain and forest functional level in this domain?
-- NFMS Support Team
On 3/7/2014 5:36 AM, goebelch wrote:
>
> Hi,
> I have installed a new domain with NSM. The 'NSM Schema Utility' is
> showing:
>
> 5042
>
> But in the NSM Admin I have the message: "Schema Not Extended"
>
> Can I verify with for ex. the mmc 'Active Directory Schema' if the all
> required extensions are done? Or is it only a problem with the NSMA
> which doesn't detect correctly the extension?
>
> Best regards,
>
> Christian
>
>
> +----------------------------------------------------------------------+
> |Filename: Screenshot.png |
> |Download: https://forums.novell.com/attachment...achmentid=5042 |
> +----------------------------------------------------------------------+
>

Similar Messages

Schema extension with unique value

I would like to know if it's possible to perform a schema extension to add a new field to active directory and then require that the value entered into the new field be unique between all users.
For example say I want to track computer to user assignment by adding a field to record the computers serial number. I want to make sure that the same computer is not assigned to 2 people so when I enter the serial number I would like AD to make sure it's
a unique value between all other users.
If this is possible any links to documentation on how it would be done would be much appreciated.
Thanks for the help

Hello,
why not using the already existing attributes that are empty on the account proeprties?
Be aware that changing the schema can result in loss of the domain if done wrong. If you still like to change the schema built a lab BEFORE doing this on production and test everything in detail in the domain to be sure not problems occur.
Additional keep in mind that own schema changes may result in problems when updating the schema with new versions from Microsoft.
http://technet.microsoft.com/en-us/library/cc961737.aspx
http://technet.microsoft.com/en-us/library/bb727064.aspx
http://technet.microsoft.com/en-us/magazine/2008.05.schema.aspx
http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/f899e538-c197-497c-beb3-c9968c681867/
http://blogs.technet.com/b/isingh/archive/2007/02/18/adding-custom-attributes-in-active-directory.aspx
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Xml schema validation problem

Hi All
How to tackle this xml schema validation problem
i am using the sample code provided by ORacle technet for xml
schema validation in the Oracle database(817).
The sample code works perfectly fine.
Sample as provided by http://otn.oracle.com/tech/xml/xdk_sample/archive/xdksample_093001.zip.
It works fine for normal xml files validated against
xml schema (xsd)
but in this case my validation is failing . Can you let me know why
I have this main schema
Comany.xsd
===========
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.company.org"
xmlns="http://www.company.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="Person.xsd"/>
<xsd:include schemaLocation="Product.xsd"/>
<xsd:element name="Company">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
<xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
================
which includes the following 2 schemas
Product.xsd
============
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="ProductType">
<xsd:sequence>
<xsd:element name="Type" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==============
Person.xsd
===========
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="PersonType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="SSN" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
=================
now when i try to validate a xml file against Company.xsd
it throws an error saying unable to find Person.xsd.
no protocol error
Now where do i place these 2 schemas(.xsd files) Person & product
so that the java schemavalidation program running inside Oracle
database can locate these files
Rgrds
Sushant

Hi Jinyu
This is the java code loaded in the database using loadjava called by a wrapper oracle stored procedure
import oracle.xml.parser.schema.*;
import oracle.xml.parser.v2.*;
import java.net.*;
import java.io.*;
import org.w3c.dom.*;
import java.util.*;
import oracle.sql.CHAR;
import java.sql.SQLException;
public class SchemaUtil
public static String validation(CHAR xml, CHAR xsd)
throws Exception
//Build Schema Object
XSDBuilder builder = new XSDBuilder();
byte [] docbytes = xsd.getBytes();
ByteArrayInputStream in = new ByteArrayInputStream(docbytes);
XMLSchema schemadoc = (XMLSchema)builder.build(in,null);
//Parse the input XML document with Schema Validation
docbytes = xml.getBytes();
in = new ByteArrayInputStream(docbytes);
DOMParser dp = new DOMParser();
// Set Schema Object for Validation
dp.setXMLSchema(schemadoc);
dp.setValidationMode(XMLParser.SCHEMA_VALIDATION);
dp.setPreserveWhitespace (true);
StringWriter sw = new StringWriter();
dp.setErrorStream (new PrintWriter(sw));
try
dp.parse (in);
sw.write("The input XML parsed without errors.\n");
catch (XMLParseException pe)
sw.write("Parser Exception: " + pe.getMessage());
catch (Exception e)
sw.write("NonParserException: " + e.getMessage());
return sw.toString();
This is the code i used initially for validating a xml file against single xml schema (.xsd) file
In the above code could u tell how to specify the second schema validation code for the incoming xml.
say i create another Schemadoc for the 2nd xml schema.
something like this with another parameter(CHAR xsd1) passing to the method
byte [] docbytes1 = xsd1.getBytes();
ByteArrayInputStream in1 = new ByteArrayInputStream(docbytes1);
XMLSchema schemadoc1 = (XMLSchema)builder.build(in1,null);
DOMParser dp = new DOMParser();
How to set for the 2nd xml schema validation in the above code or can i combine 2 xml schemas.
How to go about it
Rgrds
Sushant

Active Directory schema extensions

Hi
We are in a process of implementing SAP LDAP sync to manage users from MS Active Directory. SAP requires schema extension generated by RSLDAPSCHEMAEXT program to be applied to Active Directory so that report RSLDAPSYNC_USER can be identify SAP users in MS AD.
The MS AD team says that any non miscrosoft schema extensions are not supported as OIDs of the schema might conflict with other applications / patches.
Are the MS AD schema extensions generated by SAP program RSLDAPSCHEMAEXT supported / certified by Microsoft.
Harsh

Hi Harsh,
I would like to point you also to SAP Note 888848 - Notes on schema enhancement with RSLDAPSCHEMAEXT.
It especially states that:
..."The text document generated by RSLDAPSCHEMAEXT was supplied and validate as part of a certification process by the directory vendor."...
that means in this case by Microsoft.
If you decide not to use the schema extension that has been supplied by Microsoft you can use attributes that are already existing in your Active Directory as Juergen already pointed out.
As an example Microsoft Exchange Server creates several additional attributes such as extensionattribute1, ... , extensionattribute15 as part of the installation process. These attributes might be an option for you if you do not want to use the schema extension suggested by RSLDAPSCHEMAEXT.
Please have in mind that the filter attribute that you will use to determine the SAP username should be indexed since this will reduce the synchronization time.
Best Regards,
André

Schema extension

I am trying to install Server Management and Monitoring Services on a test
network.
On the first screen, I have chosen extend schema.
Then when I go to install Management and Monitoring Services, it checks
the schema and returns this error. The selected tree does not have the
required schema extension. Error Code 1.
What am I missing? How do I correct it?
Thanks for your help!

> Have a look at TID 10084926, think this will still apply to the current
> install
>
> Ron
>
> <[email protected]> wrote in message
> news:e_Jaf.904$[email protected]..
> >I am trying to install Server Management and Monitoring Services on a
test
> > network.
> >
> > On the first screen, I have chosen extend schema.
> >
> > Then when I go to install Management and Monitoring Services, it checks
> > the schema and returns this error. The selected tree does not have the
> > required schema extension. Error Code 1.
> >
> > What am I missing? How do I correct it?
> >
> > Thanks for your help!
>
>
Running the install with the NO_SCHEMA_CHECK allowed me to install server
management.
I am still curious why it does't recognize the extended schema. What
ramifications does that have down the road?

AD Schema Extension Updates?

Hi,
I was wondering whether anyone had any idea if Apple have any plans to update the AD schema extensions to support Apple Computer Groups rather than just Computer Lists? Lists are pretty old and the extra flexibility that comes with Computer Groups would be welcomed.
Thanks in advance.
Bobby

As I understand it, the main roadblock is that the Active Directory connector (essentially a directory service plug-in that translates AD-speak to Apple's internal format) doesn't computer groups, just computer lists. This could be added in future versions of the AD connector (I have no idea if there are any plans for this), but even then if you built computer groups in AD, they'd only work with Mac clients that had the newer version of the connector...
BTW, I've never seen much difference between computer groups vs. lists (probably because I don't use either one very much). What extra flexibility are you wishing for?

Ldap schema extension to control which users / group are imported

Hello,
would like to have your opinion:
would it be a good idea to implement ldap schema extensions to control
which users / group are imported and controlled from ldap in a ldap
mastered installation?
e.g. we could implement the following schema extension for users:
attributetype ( 1.3.6.1.4.1.<iana-org-id>.1.1 NAME ( 'BogusisBeehiveUser' )
     DESC ''
EQUALITY booleanMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
SINGLE-VALUE )
# BogusinetOrgPerson
# The BogusinetOrgPerson is derived from inetOrgPerson
objectclass     ( 1.3.6.1.4.1.<iana-org-id>.1
NAME 'BogusinetOrgPerson'
     DESC 'RFC2798: Internet Organizational Person, plus Bogus Extensions'
SUP inetOrgPerson
STRUCTURAL
     MAY (
          BogusisBeehiveUser )
Then we could control the inclusion in beehive by simply switching
BogusisBeehiveUser on or off.

sure; that's pretty much what is talked about in the Install Guide for LDAP Integration under the "inclusion and exclusion" section, about here:
http://download.oracle.com/docs/cd/E14897_01/bh.100/e14830/ldap.htm#CHDEFFJF
that doesn't go into the specifics of how you might want to design your objectClass schemas, though, as beehive is agnostic to that.
If you don't want to provision all users that match a certain existing rule (like everyone under dn=foo, or everyone where userType=employee), then adding a new attribute and building the profile inclusion rule around it is a valid thing to do.
richard

Console Extension Problem

It seems like exception occurs due to WLS console extension problem. I
captured the errors and attaching it here.
The application is working fine on WLS 8.1, the exception occurs only when i deploy
the application on WLS 7.0. The application components are extending administration
console and displaying there. During this time, it is trying to invoke servlet(ServletStupImpl)
and failing over there.
Please check the attached file and reply me ASAP.
Regards
Senthil
[Console Extension error.txt]

What is the the platform the server is running on, and what browser you are using when the problem occurs?
Are there any exceptions in the Java console for the applet?

OAM - AD schema extensions cleanup

I'm uninstalling an OAM install that is using Active Directory on Windows 2003. Reading the OAM documentation it doesn't seem to be any cleanup scripts for AD. I have removed the oblix configuration but what is the easiest way to cleanup the OAM schema extensions from AD?

You're finding yourself up against on of AD's technical constraints here: once the schema goes in, it cannot be removed.
You could go through the ob schema and disable the various objectclasses and attributes (could probably write some ldif to do that) but, as far as I know, that's the best you can do.
Perhaps take the question to an AD forum and ask about sneaky ways to clean up schema?
Mark

Active Directory Schema Extension for Directory Synchronization - ADFS 3.0, Office 365

Hi Team,
We are in a situation with extending the schema for one customer so that these additional exchange attributes may be utilized. They have a single data center where the Primary Domain Controller resides and have multiple remote sites each of which have Additional
Domain Controllers installed.
As recommended by Microsoft, I am going to extend the Active Directory Schema with Exchange Setup so that I can leverage targetaddress attribute from Local AD to set primary email address when directory synchronization happens.
My Query: Do I have to extend the AD Schema with Exchange from each of these ADC's? Or the changes I make on any of them will replicate over the others also?
Note: The customer will be using ADFS 3.0 'Single Sign On' with Office 365 and does NOT have any On-Premise Exchange deployment.

My Query: Do I have to extend the AD Schema with Exchange from each of these
ADC's? Or the changes I make on any of them will replicate over the others also?
Schema extension is done against the Schema Master. Once done, it gets replicated to other DCs with the AD forest.
For more details about Schema Extension by Exchange, you can refer to that: http://www.resdevops.com/2013/02/13/extend-ad-schema-to-allow-greater-office-365-management/
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

SCCM 2012 AD schema extension

Hi all,
we were in the process of installing SCCM 2012 R2 in our lab, we have extended the schema & schema extension creates classes & attributes we just wanted to know where we can find these Classes & attributes in AD. where we can see it being created
in AD.
We have seen the successful schema extension in the log files but we also wanted to get the details from AD side.
Please suggest.
Thanks,
Pranay.

This has all the details
But in summary:
Attributes and Classes Added by the Configuration Manager Schema Extensions
When you extend the Active Directory schema for ConfigMgr 2012, the following attributes and classes are added to Active Directory Domain Services:
Attributes:
cn=mS-SMS-Assignment-Site-Code
cn=mS-SMS-Capabilities
cn=MS-SMS-Default-MP
cn=mS-SMS-Device-Management-Point
cn=mS-SMS-Health-State
cn=MS-SMS-MP-Address
cn=MS-SMS-MP-Name
cn=MS-SMS-Ranged-IP-High
cn=MS-SMS-Ranged-IP-Low
cn=MS-SMS-Roaming-Boundaries
cn=MS-SMS-Site-Boundaries
cn=MS-SMS-Site-Code
cn=mS-SMS-Source-Forest
cn=mS-SMS-Version
Classes:
cn=MS-SMS-Management-Point
cn=MS-SMS-Roaming-Boundary-Range
cn=MS-SMS-Server-Locator-Point
cn=MS-SMS-Site
The Active Directory schema extensions might include attributes and classes that are carried forward from previous versions of the product but not used by ConfigMgr 2012. For example:
o Attribute: cn=MS-SMS-Site-Boundaries
o Class: cn=MS-SMS-Server-Locator-Point

EDirectory Schema extensions best practices / Mac OS X 10.5

Hello all,
I am integrating Mac OS X clients into my eDirectory environment, and part of my process is to extend the eDirectory schema with the relevant Mac-specific attributes. Is there an easy method to extending the schema, or do I need to manually add each individual attribute that is not already stored in an importable ldif file? Also, are there any best practices to follow when performing this work?
Thanks for the help!

Are these the extensions published by Apple? If so I think they have
fairly good documentation on their site where you got them from. If not,
well, we're going to need to know where you did get them from and what
they are actually doing.
And again, we need to move this to the novell.support.native-file-access
forum, where it belongs. Schema extensions are nothing to do with
netware.communications. Thanks
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)
Opinions expressed above are not
necessarily those of Novell Inc.

JWSDP and complex type extension problem

Hy,
We got a problem with JAX-RPC reference implementation. It seems it doesn't support inheritance beetween complex types as web services parameters or return value. A Parse exception happens when client code deserializes base class members. Does anyone know about this problem ? We don't have it with Apache Axis implementation (on client side). In our case, server code always runs in C++ with gSOAP.
And the stacktrace :
deserialization error: unexpected XML reader state. expected: END but found: START: longitude
Here our wsdl file :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="Service"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/"
targetNamespace="urn:ass"
xmlns:tns="urn:ass"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:WAT="urn:ass/WAT.xsd"
xmlns:ifg="urn:ass">
<types>
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ass/WAT.xsd"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:WAT="urn:ass/WAT.xsd"
xmlns:ifg="urn:ass">
<complexType name="Date">
<sequence>
<element name="time" type="xsd:long" minOccurs="1" maxOccurs="1"/>
</sequence>
</complexType>
<complexType name="DateStruct">
<all>
<element name="inst" type="WAT:Date" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="IcaoCode">
<sequence>
<element name="s" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
<element name="isAlphaNum" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
</sequence>
</complexType>
<complexType name="IcaoCodeStruct">
<all>
<element name="inst" type="WAT:IcaoCode" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="Ident">
<sequence>
<element name="Id" type="xsd:int" minOccurs="1" maxOccurs="1"/>
<element name="Name" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
<element name="Text" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
<complexType name="IdentStruct">
<all>
<element name="inst" type="WAT:Ident" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="Latitude">
<sequence>
<element name="s" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
<complexType name="LatitudeStruct">
<all>
<element name="inst" type="WAT:Latitude" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="Longitude">
<sequence>
<element name="s" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
<complexType name="LongitudeStruct">
<all>
<element name="inst" type="WAT:Longitude" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="Notam">
<sequence>
<element name="Id" type="xsd:int" minOccurs="1" maxOccurs="1"/>
<element name="Text" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
<complexType name="NotamStruct">
<all>
<element name="inst" type="WAT:Notam" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="Pib">
<sequence>
<element name="Id" type="xsd:int" minOccurs="1" maxOccurs="1"/>
<element name="Name" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
<complexType name="PibStruct">
<all>
<element name="inst" type="WAT:Pib" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="AirField">
<sequence>
<element name="longitude" type="WAT:Longitude" minOccurs="1" maxOccurs="1"/>
<element name="latitude" type="WAT:Latitude" minOccurs="1" maxOccurs="1"/>
<element name="codeICAO" type="WAT:IcaoCode" minOccurs="1" maxOccurs="1"/>
</sequence>
</complexType>
<complexType name="AirFieldStruct">
<all>
<element name="inst" type="WAT:AirField" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
<complexType name="SunTime">
<complexContent>
<extension base="WAT:AirField">
<sequence>
<element name="sunriseTime" type="WAT:Date" minOccurs="1" maxOccurs="1"/>
<element name="sunsetTime" type="WAT:Date" minOccurs="1" maxOccurs="1"/>
<element name="heuresCalculees" type="xsd:int" minOccurs="1" maxOccurs="1"/>
<element name="heuresExistent" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="SunTimeStruct">
<all>
<element name="inst" type="WAT:SunTime" minOccurs="1" maxOccurs="1"/>
<element name="coderet" type="xsd:int" minOccurs="1" maxOccurs="1"/>
</all>
</complexType>
</schema>
</types>
<message name="getSuntimeRequest">
<part name="req" type="xsd:string"/>
</message>
<message name="SunTimeStruct">
<part name="inst" type="WAT:SunTime"/>
<part name="coderet" type="xsd:int"/>
</message>
<portType name="ServicePortType">
<operation name="getSuntime">
<documentation>Service definition of function ifg__getSuntime</documentation>
<input message="tns:getSuntimeRequest"/>
<output message="tns:SunTimeStruct"/>
</operation>
</portType>
<binding name="ServiceBinding" type="tns:ServicePortType">
<SOAP:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getSuntime">
<SOAP:operation soapAction=""/>
<input>
<SOAP:body use="encoded" namespace="urn:ass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<SOAP:body use="encoded" namespace="urn:ass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="Service">
<documentation>gSOAP 2.1.10c generated service definition</documentation>
<port name="ServicePort" binding="tns:ServiceBinding">
<SOAP:address location="http://location/Service.cgi"/>
</port>
</service>
</definitions>

Try using the -f:searchschema feature of wscompile when generating the client stubs from your WSDL file.

Schema validation problem in oracle 11g

Hi,
I am facing the following problem.
The Issue.xsd contains two elements (element1, element2) described as below. It contains two types
1. simpleType - MyStringType
2. complexType - MyType, an extension of MyStringType
Oracle XML DB can able to validate element2(simpleType), but not element1(complexType).
---------------------Issue.xsd File ------------------
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="ConfigRoot" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="ConfigRoot" elementFormDefault="qualified">
     <xsd:element name="ConfigRoot" xdb:defaultTable="CONFIG_TBL_ISSUE">
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element name="element1" type="MyType"/>
                    <xsd:element name="element2" type="MyStringType"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     <xsd:simpleType name="MyStringType">
          <xsd:restriction base="xsd:string">
               <xsd:pattern value="\d{2}([\W])\d{2}([\W])\d{2}"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="MyType">
          <xsd:simpleContent>
               <xsd:extension base="MyStringType">
                    <xsd:attribute name="id" type="xsd:integer"/>
               </xsd:extension>
          </xsd:simpleContent>
     </xsd:complexType>
</xsd:schema>
--------------------- XML File -----------------
<?xml version="1.0" encoding="UTF-8"?>
<ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <element1 id="1">19-12-222</element1>
     <element2>19-12-555</element2>
</ConfigRoot>
Though the schema is registered as binary, oracle could not able to validate the element1. The XML gets properly validated in the XML editors.

"Issue.xsd"
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="ConfigRoot" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="ConfigRoot" elementFormDefault="qualified">
<xsd:element name="ConfigRoot" xdb:defaultTable="CONFIG_TBL_ISSUE">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="element1" type="MyType"/>
<xsd:element name="element2" type="MyStringType"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="MyStringType">
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{2}(\W)\d{2}(\W)\d{2}"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="MyType">
<xsd:simpleContent>
<xsd:extension base="MyStringType">
<xsd:attribute name="id" type="xsd:integer"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>
"Issue.xml"
<?xml version="1.0" encoding="UTF-8"?>
<ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<element1 id="1">19-12-222</element1>
<element2>19-12-555</element2>
</ConfigRoot>
[oracle@srv01-18-102 20081010]$ sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Oct 10 14:46:09 2008
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
PL/SQL Release 11.1.0.7.0 - Production
CORE    11.1.0.7.0      Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - Production
SQL> create user otn identified by otn account unlock;
User created.
SQL> -- The Quick and Dirty way regarding granting privileges
SQL> grant dba, xdbadmin to otn;
Grant succeeded.
SQL> connect otn/otn
Connected.
SQL> create directory "XMLDIR_SCHEMA" as '/home/oracle/OTN/20081010';
Directory created.
SQL> -- Issue.xsd and Issue.xml are created and copied to the directory /home/oracle/OTN/20081010, on which I have read, write access as Linux user "oracle" (the oracle software owner)
SQL> BEGIN
2 DBMS_XMLSCHEMA.registerSchema(
3 SCHEMAURL => 'Issue.xsd',
4 SCHEMADOC => bfilename ('XMLDIR_SCHEMA', 'Issue.xsd'),
5 GENTYPES => FALSE,
6 OWNER => USER,
7 OPTIONS => 3);
8 end;
9* /
PL/SQL procedure successfully completed.
SQL> select * from tab;
TNAME                          TABTYPE CLUSTERID
CONFIG_TBL_ISSUE               TABLE
SQL> set long 100000000
SQL> desc "CONFIG_TBL_ISSUE"
Name                                      Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "Issue.xsd" Element "ConfigRoot") STORAGE BINARY
SQL> set pages 5000
SQL> select dbms_metadata.get_ddl('TABLE','CONFIG_TBL_ISSUE',user) from dual;
DBMS_METADATA.GET_DDL('TABLE','CONFIG_TBL_ISSUE',USER)
CREATE TABLE "OTN"."CONFIG_TBL_ISSUE" OF "SYS"."XMLTYPE"
XMLTYPE STORE AS BASICFILE BINARY XML (
TABLESPACE "USERS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10
NOCACHE LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))
XMLSCHEMA "Issue.xsd" ELEMENT "ConfigRoot" ID 4768 DISALLOW NONSCHEMA PCTFREE 10
PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
INSERT INTO "CONFIG_TBL_ISSUE"
VALUES
(XMLTYPE(bfilename('XMLDIR_SCHEMA','Issue.xml'),NLS_CHARSET_ID('AL32UTF8')));
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
2 VALUES
3 (XMLTYPE(bfilename('XMLDIR_SCHEMA','Issue.xml'),NLS_CHARSET_ID('AL32UTF8')))
4 ;
(XMLTYPE(bfilename('XMLDIR_SCHEMA','Issue.xml'),NLS_CHARSET_ID('AL32UTF8')))
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00333: literal "19-12-555" is not valid with respect to the pattern
SQL> -- TESTING EXCEPTIONS
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
2 VALUES
3 (XMLTYPE(
4   '<?xml version="1.0" encoding="UTF-8"?>
5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
6   <element1 id="1">01-11-11</element1>
7   <element2>02-11-11</element2>
8   </ConfigRoot>
9 '));
1 row created.
SQL> rollback;
Rollback complete.
SQL> -- ELEMENT 1 and 2 ARE WRONG (correct response)
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
2 VALUES
3 (XMLTYPE(
4   '<?xml version="1.0" encoding="UTF-8"?>
5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
6   <element1 id="1">01-11-111</element1>
7   <element2>02-11-111</element2>
8   </ConfigRoot>
9 '));
(XMLTYPE(
ERROR at line 3:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00333: literal "02-11-111" is not valid with respect to the pattern
SQL> -- ELEMENT 1 is WRONG (OOPS)
SQL> INSERT INTO "CONFIG_TBL_ISSUE"
2 VALUES
3 (XMLTYPE(
4   '<?xml version="1.0" encoding="UTF-8"?>
5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
6   <element1 id="1">01-11-111</element1>
7   <element2>02-11-11</element2>
8   </ConfigRoot>
9 '));
1 row created.
SQL> rollback;
Rollback complete.
SQL> -- ELEMENT 2 is WRONG (correct response)
SQL> SQL> INSERT INTO "CONFIG_TBL_ISSUE"
2 VALUES
3 (XMLTYPE(
4   '<?xml version="1.0" encoding="UTF-8"?>
5   <ConfigRoot xsi:schemaLocation="ConfigRoot Issue.xsd" xmlns="ConfigRoot" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
6   <element1 id="1">01-11-11</element1>
7   <element2>02-11-111</element2>
8   </ConfigRoot>
9 '));
INSERT INTO "CONFIG_TBL_ISSUE"
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LSX-00333: literal "02-11-111" is not valid with respect to the patternIt looks like if, if I interpret the XML schema correctly, that it doesn't comply to the extension "myStringType" of the restriction base "MyType". I am not absolutely sure if this is correct behavior or not, because of the nesting. If it should comply to the extend and therefore also should comply to the restriction pattern then this would mean that you discovered a bug.
If it is a bug or not, I think you should create a service request for this, asking Oracle Support for help.
Grz
Marco

Schema extension [extend] and ldap v3 conformance [proprietary]

Hi,
am I still conform to ldap v3 spec when I extend the schema with my own attributes and object classes (with the iplanet console 5.1)?
So, does ldap v3 only define the object classes and attributes or an extension mechanism too?
Regards
Kristian

The first example was almost correct !
The error message: "javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001C6, problem 2001 (NO_OBJECT), data 0, best match of: 'CN=Schema,CN=Configuration,DC=ric,DC=com'; " simply indicates a naming error.
If you follow the logic of your code, you are trying to create an attribute with the distinguished name:[code]CN=fooattr,CN=Schema,CN=Configuration,DC=ric,DC=com,CN=Schema,CN=Configuration,DC=ric,DC=comIf you are wondering why, it is because you are attempting to create the subcontext from the schema naming context.schema.createSubcontext("CN=fooattr," + dn,attr);You can correct this by changing your code toschema.createSubcontext("CN=fooattr",attr); or toctx.createSubcontext("CN=fooattr," + dn,attr);One other error, you are missing one of the mandatory attributes; namely oMSyntax.attrs.put("oMSyntax","2");You can find details on the Active Directory Schema at http://technet2.microsoft.com/WindowsServer/en/library/97cae647-d996-48ff-b478-c96193abeadb1033.mspx
A simple way of checking the mandatory attributes for any object class is to look at the values of the systemMustContain attribute of the objectClass definition. In the case of attributeSchema, the systemMustContain attribute includes: schemaIDGUID (automagically generated), oMSyntax, ldapDisplayName, isSingleValued, cn, attributeSyntax and attributeID
Another reference that is helpful is a table of Attribute Syntax definitions at http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/dsbe_ext_dghb.mspx
The only words of advice for extending the schema are:
1. Test, Test, Test, before deploying in production
2. Do not ever reuse attributeID's or make up your own! If you are extending the schema get your own OID from an appropriate standards authority, or they may be obtained from Microsoft. Refer to http://msdn2.microsoft.com/en-us/library/ms677621.aspx or http://msdn2.microsoft.com/en-us/library/ms677620.aspx

Schema extension problem

Similar Messages

Maybe you are looking for