A Installing and Configuring Oracle XML DB

Installing or Reinstalling Oracle XML DB From Scratch

You can perform a new installation of Oracle XML DB with or without Database Configuration Assistant (DBCA). If Oracle XML DB is already installed, complete the steps in "Reinstalling Oracle XML DB".

Installing a New Oracle XML DB With Database Configuration Assistant

Oracle XML DB is part of the seed database and installed by Database Configuration Assistant (DBCA) by default. No additional steps are required to install Oracle XML DB. However, if you select the Advanced database configuration, then you can configure Oracle XML DB tablespace and FTP, HTTP, and WebDAV port numbers.

By default DBCA performs the following tasks during installation:

• Creates an Oracle XML DB tablespace for Oracle XML DB Repository

• Enables all protocol access

• Configures FTP at port 2100

• Configures HTTP/WebDAV at port 8080

The Oracle XML DB tablespace holds the data stored in Oracle XML DB repository, including data stored using:

• SQL, for example using RESOURCE_VIEW and PATH_VIEW

• Protocols such as FTP, HTTP, and WebDAV

You can store data in tables outside this tablespace and access the data through the repository by having REFs to that data stored in the tables in this tablespace.

Installing a New Oracle XML DB Manually Without Database Configuration Assistant

After the database installation, you must run the following SQL scripts in rdbms/admin connecting to SYS to install Oracle XML DB after creating a new tablespace for Oracle XML DB repository. Here is the syntax for this:

catqm.sql <XDB_password> <XDB_TS_NAME> <TEMP_TS_NAME>
#Create the tables and views needed to run XML DB

For example:

catqm.sql change_on_install XDB TEMP

Reconnect to SYS again and run the following:

catxdbj.sql          #Load xdb java library

Reinstalling Oracle XML DB

To reinstall Oracle XML DB follow these steps:

1. Remove the dispatcher by removing the XML DB dispatcher entry from the init.ora file as follows:

   dispatchers="(PROTOCOL=TCP) (SERVICE=<sid>XDB)"

   If the server parameter file is used, run the following command when the instance is up and while logged in as SYS:

   ALTER SYSTEM RESET dispatchers scope=spfile sid='*';

2. Drop user XDB and tablespace XDB by connecting to SYS and running the following SQL script:

   @?/rdbms/admin/catnoqm.sql
   ALTER TABLESPACE <XDB_TS_NAME> offline;
   DROP TABLESPACE <XDB_TS_NAME> including contents;

3. Re-create tablespace XDB.

4. Execute catnoqm.sql.

5. Execute catqm.sql.

6. Execute catxdbj.sql.

7. Install Oracle XML DB manually as described in "Installing a New Oracle XML DB Manually Without Database Configuration Assistant".

Upgrading Oracle XML DB From Release 9.2 to 10g Release 1 (10.1)

All Oracle XML DB upgrade tasks are handled automatically when you use Database Upgrade Assistant to upgrade your database from any version of Oracle9i release 2 to Oracle Database 10g release 1 (10.1).

Top Level Tag <xdbconfig>

A top level tag, <xdbconfig> is divided into two sections:

• <sysconfig> This keeps system-specific, built-in parameters.

• <userconfig> This allows users to store new custom parameters.

The following describes the syntax:

<xdbconfig> 
    <sysconfig> ... </sysconfig> 
    <userconfig>  ...  </userconfig> 
</xdbconfig>

<sysconfig>

The <sysconfig> section is further subdivided as follows:

<sysconfig> 
    General parameters
      <protocolconfig> ... </protocolconfig> 
</sysconfig>

It stores several general parameters that apply to all Oracle XML DB, for example, the maximum age of an access control list (ACL), whether Oracle XML DB should be case sensitive, and so on.

Protocol-specific parameters are grouped inside the <protocolconfig> tag.

<userconfig>

The <userconfig> section contains any parameters that you may want to add.

<protocolconfig>

The structure of the <protocolconfig> section is as follows:

<protocolconfig> 
  <common> ... </common> 
  <httpconfig> ... </httpconfig> 
  <ftpconfig> ... </ftpconfig> 
</protocolconfig>

Under <common> Oracle Database 10g stores parameters that apply to all protocols, such as MIME type information. There are also HTTP and FTP specific parameters under sections <httpconfig> and <ftpconfig> respectively.

<httpconfig>

Inside <httpconfig> there is a further subsection, <webappconfig> that corresponds to Web-based applications. It includes Web application specific parameters, for example, icon name, display name for the application, list of servlets in Oracle XML DB, and so on.

Get Configuration, cfg_get()

The cfg_get() function returns a copy of the configuration as an XMLType:

DBMS_XDB.CFG_GET() RETURN SYS.XMLTYPE

Update Configuration, cfg_update()

The cfg_update() function updates the configuration with a new one:

DBMS_XDB.CFG_UPDATE(newconfig SYS.XMLTYPE)

cfg_update() is auto-commit.

BEGIN 
DBMS_XDB.CFG_UPDATE(UPDATEXML(UPDATEXML 
    (DBMS_XDB.CFG_GET(), 
        /xdbconfig/descendant::ftp-port/text()',   '2121'), 
        '/xdbconfig/descendant::http-port/text()', 
         19090')) 
END; 
/

Refresh Configuration, cfg_refresh()

The cfg_refresh() function updates the configuration snapshot to correspond to the latest version on disk at that instant:

DBMS_XDB.CFG_REFRESH()

Typically, cfg_refresh() is called in one of the following scenarios:

• You have modified the configuration and now want the session to pick up the latest version of the configuration information.

• It has been a long running session, the configuration has been modified by a concurrent session, and you want the current session to pick up the latest version of the configuration information.

• 
  

  See Also: Oracle XML API Reference