Category: XMLDB

June 24

Though also a recap on presentations of Oracle Open World 2006, where I pinpointed on XML and XMLDB sessions, now it is time to go a little bit further into these great new features that will be available in Oracle 11g regarding XMLDB functionality. One of the big steps forward to full exploitation of these features is the new Binary XML storage.

Until XMLDB one could make use of (C)LOB or varchar2 datatypes to store XML data, both have their limitations regarding storing XML. The introduction of the XMLType datatype / XMLDB features, formed the base of what has become full support of almost every W3C XML standard out there. This datatype allowed storing XML data via “Schema based” or “Schema Less” principles; with or without references to a XML Schema.

XML data can be stored / presented via the standard relational tables. This can be achieved for XMLType Views. If XML data is based on the XMLType data type then storage of XML data could result in Object Relational storage or CLOB storage. A mixture of the two is sometimes also possible and is called “Hybrid” storage. XML data can be stored in a column or as an XMLType table.

June 8

I noticed an new addition to the DBMS_XDB package a while ago named SETLISTENERLOCALACCESS that, despite it is part of a XMLDB package, was first seen by me on a APEX forum (it is not listed in the Oracle 10g manuals (eg. Oracle® Database PL/SQL Packages and Types Reference).

What does it do?

The manual (Oracle® Database Express Edition Installation Guide !) described it as follows:

4.4 Making Oracle Database XE Server Available to Remote Clients
After you install Oracle Database XE Server, its graphical user interface is only available from the local server, not remotely.

    Security Note:

    With remote HTTP access to Oracle Database XE, all information exchanged between the browser and the database is in clear text—that is, unencrypted—including database user names and passwords. If this is cause for concern, do not enable remote HTTP connection to the database.

Asking for an explanation on the XMLDB forum the following information was given:

June 6

On itself, this one is very simple, but to my surprise it still not very clear when I read the questions about this on the OTN XMLDB forum. Maybe this occurs because this isn’t mentioned on the OTN XMLDB FAQ thread, which isn’t read as much as it should be. A lot of really good examples of Mark (Drake) are described in more detail here, and the are definitely worth your time.

So how to enable the WebDAV, HTTP(s) and FTP(s) functionality via the protocol server?

Before Oracle database version 10.2 this is done default (HTTP on port 8080, FTP on port 2100). After (and in my opinion this is the correct behavior) port numbers are set to 0 (zero) and therefore this functionality is disabled.

The XMLDB Protocol Server functionality is configured and controlled via the xdbconfig.xml file. Updating this file via SQL statements is described in the following section.