Instead, you must create that represent the XML data of interest, and then use those virtual columns to define the constraints that you need.
This approach applies only to XML data that is stored as binary XML.
Figure 3-1 shows a simple drag and drop operation for copying the contents of the data.
It is equivalent to the IANA registered standard UTF-8 encoding, which supports all valid XML characters.
The technique is as follows: data as you would create virtual columns using any other type of data, but using a slightly different syntax.
In particular, you cannot specify any constraints in association with the column definition.
This chapter also further explains Oracle XML DB concepts introduced in Chapter 1, "Introduction to Oracle XML DB".
An error is raised if you try to load a schema-based XML document that contains characters that are not legal in the determined encoding.
Each entity in an XML document may use a different encoding for its characters.
Entities that are stored in an encoding other than UTF-8 or UTF-16 must begin with an XML declaration containing an encoding specification indicating the character encoding in use.
The easiest way to make these XML documents available to Oracle Database is to load them into Oracle XML DB Repository.
You can load XML documents from a local file system into Oracle XML DB Repository using protocols such as Web DAV, from Windows Explorer or other tools that support Web DAV.