12
Oracle9i XML Database Developer's Guide - Oracle XML DB

This chapter lists additions and corrections to Oracle9i XML Database Developer's Guide - Oracle XML DB, Release 2 (9.2).

This chapter contains the following topic:

• Documentation Corrections

Documentation Corrections

The following are corrections to the Oracle9i XML Database Developer's Guide - Oracle XML DB document:

• In Chapter 5, "Structured Mapping of XMLType", the entry in Table 5-5, VARCHAR2(4000) if mapUNboundedStringToLob="true" should read VARCHAR2(4000) if mapUNboundedStringToLob="false".

• In Chapter 5, "Structured Mapping of XMLType", the entry in Table 5-6, RAW(2000) if mapUNboundedStringToLob="true" should read RAW(2000) if mapUNboundedStringToLob="false".

• In Chapter 10, "Generating XML Data from the Database", the syntax diagram 10-7 should not include the ORDER BY clause. ORDER BY is not supported in the SQLX function XMLAgg() in this release.

• In Chapter 18, "Oracle XML DB Resource Security", privilege name "linkto" should read "link-to" and privilege name "unlinkfrom" should read "unlink-from".

• In Chapter 21, "Managing Oracle XML DB Using Oracle Enterprise Manager", privilege name "linkto" should read "link-to" and privilege name "unlinkfrom" should read "unlink-from".

• In Appendix A, "Installing and Configuring Oracle XML DB", the following explanation for using FTP and HTTP protocols with Oracle XML Database is missing from the "Installation" section:

  Oracle XML Database installation, includes a dynamic protocol registration that actually registers FTP and HTTP services with the local Listener. You can perform start, stop, and query with "lsnrctl". For example:

          start: lsnrctl start 
          stop: lsnrctl stop 
          query: lsnrctl status 
  
  

  To change the FTP/HTTP port number, update the tags <ftp-port> and <http-port> in the file, /xdbconfig.xml in Oracle XML Database Repository. See Appendix A, "Installing and Configuring Oracle XML DB" and Chapter 19, "Using FTP. HTTP, and WebDav Protocols" for descriptions of how to update /xdbconfig.xml. After updating the port numbers dynamic protocol registration will automatically stop FTP/HTTP service on old port numbers and start them on new port numbers if the local Listener is up. Otherwise, restart the Listener after updating the port numbers. If Listener is running on a non-standard port (not 1521), in order for the protocols to register with the correct Listener the initialization parameter file must contain a local_listener entry that references a TNSNAME entry. This in turn points at the correct Listener.

  After editing the initialization parameter you must regenerate the SPFILE entry using create SPFILE.