Oracle® HTML DB

Installation Guide

Release 1.6

Part No. B14498-02

March 2005

Oracle HTML DB Installation Guide, Release 1.6

Part No. B14498-02

Copyright © 2004, 2005, Oracle. All rights reserved.

Primary Author:  Terri Winters

Contributors:  Christina Cho, Joel Kallman, Sergio Leunissen, Raj Mattamal, Scott Spendolini, and Jason Straub

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Contents

Title and Copyright Information

Send Us Your Comments

Preface

Audience

Documentation Accessibility

Structure

Related Documents

Conventions

1 Oracle HTML DB Installation Overview

Overview of the Installation Process

Understanding the Installation Process

Upgrading from a Previous Version of Oracle HTML DB

2 Oracle HTML DB Installation Requirements

Oracle Database Requirement

Checking the shared_pool_size of the Target Database

Oracle HTTP Server Requirement Disk Space Requirements Oracle XML DB Requirement Oracle Text Requirement
3 Installing the Software

Recommended Pre-installation Tasks

Installing the Oracle HTML DB Software

4 Oracle HTML DB Post-installation Tasks

Required Post-installation Tasks

Copying the Images Directory

Copying the Images Directory When Upgrading

Copying the Images Directory in New Installation

Configuring Oracle HTTP Server When Upgrading

Oracle HTTP Server Release 9.0.3

Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g

Configuring Oracle HTTP Server in a New Installation

Oracle HTTP Server Release 9.0.3

Modifying the Oracle9i wdbsvr.app File

Modifying the Oracle9i httpd.conf File

Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g Installing Oracle HTML DB in Other Languages Obfuscating PlsqlDatabasePassword Parameter

Obfuscating Passwords in a New Installation

Obfuscating Passwords if Upgrading

Logging in to Oracle HTML DB

Accessing the Oracle HTML DB Login Page

A Oracle HTML DB Troubleshooting

Reviewing a Log of an Installation Session

Cleaning Up After a Failed Installation

After a Failed Upgrade Installation

After a Failed New Installation

Images Displaying Incorrectly in Oracle HTML DB
Index

Send Us Your Comments

Oracle HTML DB Installation Guide Release 1.6

Part No. B14498-02

Oracle welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision.

- Did you find any errors?

- Is the information clearly presented?

- Do you need more information? If so, where?

- Are the examples correct? Do you need more examples?

- What features did you like most about this manual?

If you find any errors or have any other suggestions for improvement, please indicate the title and part number of the documentation and the chapter, section, and page number (if available). You can send comments to us in the following ways:

- Electronic mail: infodev_us@oracle.com

- FAX: (650) 506-7227. Attn: Server Technologies Documentation Manager

- Postal service:

Oracle Corporation

Server Technologies Documentation Manager

500 Oracle Parkway, Mailstop 4op11

Redwood Shores, CA 94065

USA

If you would like a reply, please give your name, address, telephone number, and electronic mail address (optional).

If you have problems with the software, please contact your local Oracle Support Services.

Preface

This guide explains how to install and configure Oracle HTML DB release 1.6.

This Preface contains these topics:

- Audience

- Documentation Accessibility

- Structure

- Related Documents

- Conventions

Audience

Oracle HTML DB Installation Guide is intended for anyone responsible for installing Oracle HTML DB.

To use this manual, you must have administrative privileges on the computer where you installed your Oracle Database and familiarity with object-relational database management concepts.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure

This document contains:

Chapter 1, "Oracle HTML DB Installation Overview"

Provides an overview of installing Oracle HTML DB and describes issues to consider before installing.

Chapter 2, "Oracle HTML DB Installation Requirements"

Describes the requirements for installing Oracle HTML DB.

Chapter 3, "Installing the Software"

Describes how to install Oracle HTML DB release 1.6.

Chapter 4, "Oracle HTML DB Post-installation Tasks"

Describes tasks that you need to complete after you install the software.

Appendix A, "Oracle HTML DB Troubleshooting"

Contains information on troubleshooting installation issues.

Related Documents

For more information, see these Oracle resources:

- Oracle Database Release Notes for your operating environment

- Oracle Database Installation Guide for your operating environment

- Oracle Database Concepts

- Oracle HTTP Server Administrator's Guide

- Oracle9i Application Server Administrator's Guide

- Oracle HTML DB User's Guide

- Oracle HTML DB 2 Day Developer

For information about Oracle error messages, see Oracle Database Error Messages. Oracle error message documentation is available only in HTML. If you only have access to the Oracle Documentation CD, you can browse the error messages by range. Once you find the specific range, use your browser's "find in page" feature to locate the specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.

Many of the examples in this book use the sample schemas, which are installed by default when you select the Basic Installation option with an Oracle Database installation. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.

Printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://otn.oracle.com/membership/

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/documentation/

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

- Conventions in Text

- Conventions in Code Examples

- Conventions for Windows Operating Systems

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention

Meaning

Example

Bold

Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.

When you specify this clause, you create an index-organized table.

Italics

Italic typeface indicates book titles or emphasis.

Oracle Database Concepts
Ensure that the recovery catalog and target database do not reside on the same disk.

UPPERCASE monospace (fixed-width) font

Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, Recovery Manager keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.

You can specify this clause only for a NUMBER column.
You can back up the database by using the BACKUP command.

Query the TABLE_NAME column in the USER_TABLES data dictionary view.

Use the DBMS_STATS.GENERATE_STATS procedure.

lowercase monospace (fixed-width) font

Lowercase monospace typeface indicates executable programs, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names and connect identifiers, user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values.
Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.

Enter sqlplus to start SQL*Plus.
The password is specified in the orapwd file.

Back up the datafiles and control files in the /disk1/oracle/dbs directory.

The department_id, department_name, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect as oe user.

The JRepUtil class implements these methods.

lowercase italic monospace (fixed-width) font

Lowercase italic monospace font represents placeholders or variables.

You can specify the parallel_clause.
Run old_release.SQL where old_release refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention

Meaning

Example

[ ]

Anything enclosed in brackets is optional.

DECIMAL (digits [ , precision ])

{ }

Braces are used for grouping items.

{ENABLE | DISABLE}

|

A vertical bar represents a choice of two options.

{ENABLE | DISABLE}
[COMPRESS | NOCOMPRESS]

...

Ellipsis points mean repetition in syntax descriptions.
In addition, ellipsis points can mean an omission in code examples or text.

CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM employees;

Other symbols

You must use symbols other than brackets ([ ]), braces ({ }), vertical bars (|), and ellipsis points (...) exactly as shown.

acctbal NUMBER(11,2);
acct    CONSTANT NUMBER(4) := 3;

Italics

Italicized text indicates placeholders or variables for which you must supply particular values.

CONNECT SYSTEM/system_password
DB_NAME = database_name

UPPERCASE

Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. Because these terms are not case sensitive, you can use them in either UPPERCASE or lowercase.

SELECT last_name, employee_id FROM employees;
SELECT * FROM USER_TABLES;
DROP TABLE hr.employees;

lowercase

Lowercase typeface indicates user-defined programmatic elements, such as names of tables, columns, or files.
Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.

SELECT last_name, employee_id FROM employees;
sqlplus hr/hr
CREATE USER mjones IDENTIFIED BY ty3MU9;

Conventions for Windows Operating Systems

The following table describes conventions for Windows operating systems and provides examples of their use.

Convention

Meaning

Example

Choose Start > menu item

How to start a program.

From the Start menu, select Programs, then Oracle - HOME_NAME, then Configuration and Management Tools, then Database Configuration Assistant.

File and directory names

File and directory names are not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (|), and dash (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the filename begins with \\, then Windows assumes it uses the Universal Naming Convention.

c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32

C:\>

Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this manual.

C:\oracle\oradata>

Special characters

The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documentation for more information on escape and special characters.

C:\> exp HR/HR TABLES=emp QUERY=\"WHERE job='REP'\"

HOME_NAME

Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore.

C:\> net start OracleHOME_NAMETNSListener

ORACLE_HOME and ORACLE_BASE

In releases prior to Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a top level ORACLE_HOME directory. The default for Windows NT was C:\orant.
This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level ORACLE_HOME directory. There is a top level directory called ORACLE_BASE that by default is C:\oracle\product\10.1.0. If you install the latest Oracle release on a computer with no other Oracle software installed, then the default setting for the first Oracle home directory is C:\oracle\product\10.1.0\db_n, where n is the latest Oracle home number. The Oracle home directory is located directly under ORACLE_BASE.

All directory path examples in this guide follow OFA conventions.

Refer to Oracle Database Installation Guide for 32-Bit Windows for additional information about OFA compliances and for information about installing Oracle products in non-OFA compliant directories.

Go to the ORACLE_BASE\ORACLE_HOME\rdbms\admin directory.

1 Oracle HTML DB Installation Overview

This chapter provides an overview of installing Oracle HTML DB and describes issues to consider before installing.

This chapter contains these topics:

- Overview of the Installation Process

- Understanding the Installation Process

- Upgrading from a Previous Version of Oracle HTML DB

Overview of the Installation Process

The installation process consists of four parts:

1. Plan your installation: This chapter offers an overview of the steps required to install Oracle HTML DB.

2. Verify installation requirements: Chapter 2, "Oracle HTML DB Installation Requirements" describes the minimum requirements that your system must meet before you install the software.

3. Install the software: Use the following sections to install Oracle HTML DB:

- Chapter 3, "Installing the Software" describes how to install the software.

- Appendix A, "Oracle HTML DB Troubleshooting" provides installation troubleshooting advice.

4. Complete postinstallation tasks: Chapter 4, "Oracle HTML DB Post-installation Tasks" describes recommended and required postinstallation tasks.

Understanding the Installation Process

Oracle HTML DB is a browser based development environment that enables non-programmers to create database-centric Web applications. Oracle HTML DB provides developers with the productivity of a desktop database, but with the security, reliability, and performance of the Oracle database.

Installing Oracle HTML DB is a two step process:

1. Install the database objects that make up Oracle HTML DB in an Oracle database (Oracle9i release 2 (9.2.0.3) or later).

2. Configure an Oracle HTTP Server release 9.0.3 or higher with mod_plsql to connect to the Oracle database where Oracle HTML DB is installed.

Upgrading from a Previous Version of Oracle HTML DB

If you have version 1.5.0.00.33 or 1.5.1.00.12 of Oracle HTML DB, running this installation will upgrade your Oracle HTML DB instance to version 1.6. This installation will create Oracle HTML DB 1.6 database objects in a new schema and migrate the application metadata to the new version.

2 Oracle HTML DB Installation Requirements

This chapter describes the requirements for installing Oracle HTML DB, release 1.6.

This chapter contains these topics:

- Oracle Database Requirement

- Oracle HTTP Server Requirement

- Disk Space Requirements

- Oracle XML DB Requirement

- Oracle Text Requirement

Oracle Database Requirement

Oracle HTML DB version 1.6 requires either Oracle9i release 2 (9.2.0.3) or later, or Oracle Database 10g release 1 (10.1).

Checking the shared_pool_size of the Target Database

Oracle HTML DB requires the shared_pool_size of the target database to be at least 100 MB.

To check the shared_pool_size of the target database:

1. Start the database:

SQL> STARTUP

2. If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):

SQL> SHOW PARAMETER PFILE;

This command displays the name and location of the server parameter file or the initialization parameter file.

3. Determine the current values of the shared_pool_size parameter:

SQL> SHOW PARAMETER SHARED_POOL_SIZE

4. If the system is using a server parameter file, set the value of the SHARED_POOL_SIZE initialization parameter to at least 100 MB:

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='100M' SCOPE=spfile;

5. If the system uses an initialization parameter file, change the values of the SHARED_POOL_SIZE parameter to at least 100 MB in the initialization parameter file (initsid.ora).

6. Shut down the database:

SQL> SHUTDOWN

7. Restart the database:

SQL> STARTUP

Oracle HTTP Server Requirement

Oracle HTML DB requires Oracle HTTP Server in order to run. Your system must have one of the following:

- Oracle HTTP Server release 9.0.3 or higher with mod_plsql

- Oracle HTTP Server 10g Release 1

- Oracle Application Server 10g

Disk Space Requirements

Verify that the file system where the Oracle HTML DB distribution will be unzipped contains at least 400MB of free disk space for the installation.

Oracle XML DB Requirement

Oracle XML DB must be installed in the Oracle database that you want to use. If you are using a preconfigured database created either during an installation or by Database Configuration Assistant (DBCA), Oracle XML DB is already installed and configured.

See Also:

Oracle XML DB Developer's Guide for more information about manually adding Oracle XML DB to an existing database

Oracle Text Requirement

Oracle Text must be installed in order to utilize the search capability in Oracle HTML DB online help. By default, Oracle Text is installed as part of Oracle Database.

In addition, make sure that the default language preferences for Oracle Text have been installed. To install the Oracle Text default language, run the approriate drdeflang.sql script (for example, drdefus.sql for US English) from the following directory:

ORACLE_BASE\ORACLE_HOME\ctx\admin\defaults

See Also:

Oracle Text Application Developer's Guide for more information on Oracle Text

3 Installing the Software

This chapter describes how to install Oracle HTML DB release 1.6.

This chapter contains these topics:

- Recommended Pre-installation Tasks

- Installing the Oracle HTML DB Software

Recommended Pre-installation Tasks

If you plan to install Oracle HTML DB, Oracle recommends you complete the following steps to back up the database before beginning the installation:

1. Shut down Oracle databases.
Shut down any existing Oracle Database instances with normal or immediate priority. On RAC systems, shut down all instances on each node.

If Automatic Storage Management (ASM) is running, shut down all databases that use ASM, then shut down the ASM instance on each node of the cluster.

2. Stop all processes.
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.

3. Back up the Oracle Database installation.
Oracle recommends that you create a backup of your Oracle Database installation before you install Oracle HTML DB.

4. Start the Oracle Database instance that contains the target database.
After backing up the system, you must start the Oracle instance that contains the target Oracle Database. Do not start other processes such as the listener or Oracle HTTP Server.

Note:

If you are connecting to a remote database, then start the listener.

Installing the Oracle HTML DB Software

To install Oracle HTML DB release 1.6 you must download and unzip the file htmldb_1.6.0.zip on a computer where you can connect to the target database using SQL*Plus as the SYS user.

See Also:

PL/SQL User's Guide and Reference for more information about SQL*Plus

To install Oracle HTML DB release 1.6:

1. Download the file htmldb_1.6.0.zip.

2. Unzip htmldb_1.6.0.zip as follows, preserving directory names:

- UNIX and Linux: unzip htmldb_1.6.0.zip

- Windows: Double click the file htmldb_1.6.0.zip in Windows Explorer

3. Change your working directory to htmldb.

4. Connect to SQL*Plus as the SYS user as SYSDBA.

5. Run htmldbins.sql passing the following six arguments in the order shown:

@htmldbins password tablespace_htmldb tablespace_files tablespace_temp images connect

Where:

- password is the password for the Oracle HTML DB administrator account, the HTML DB schema owner, and the HTML DB files schema owner.

The HTML DB schema owner is the user or schema into which Oracle HTML DB database objects will be installed. The HTML DB files schema owner is the user or schema where uploaded files are maintained in Oracle HTML DB.

- tablespace_htmldb is the name of tablespace for the Oracle HTML DB application user.

- tablespace_files is the name of tablespace for the Oracle HTML DB files user.

- tablespace_temp is the name of the temporary tablespace.

- images is the virtual directory for Oracle HTML DB images. To support future Oracle HTML DB upgrades, define the virtual image directory as /i/.

- connect is the Oracle Net connect string to the database. If this is a local install, use none or NONE.

The following examples demonstrate running htmldbins.sql and passing these arguments when the target database is Oracle Database 10g release 1 (10.1):

Local installation:

sqlplus "sys/syspass as sysdba" @htmldbins password SYSAUX SYSAUX TEMP /i/ none

Using a connect string:

sqlplus "sys/syspass@10g as sysdba" @htmldbins password SYSAUX SYSAUX TEMP /i/ 10g

4 Oracle HTML DB Post-installation Tasks

This chapter describes tasks that you need to complete after you install the software.

This chapter contains these topics:

- Required Post-installation Tasks

- Copying the Images Directory

- Configuring Oracle HTTP Server When Upgrading

- Configuring Oracle HTTP Server in a New Installation

- Installing Oracle HTML DB in Other Languages

- Obfuscating PlsqlDatabasePassword Parameter

- Logging in to Oracle HTML DB

Note:

Within the context of this document, the Oracle home directory (ORACLE_HOME) is the location where Oracle HTTP Server is installed.

Required Post-installation Tasks

Before proceeding with other tasks described in this chapter, you need to start all processes such as TNS listener and Oracle HTTP Server that were stopped before installing Oracle HTML DB.

See Also:

"Recommended Pre-installation Tasks"

Copying the Images Directory

Whether you are loading a new installation or upgrading from a previous release, you must copy the images directory from the top level of the unzipped htmldb_1.6.0.zip file to the location on the file system containing the Oracle home for Oracle HTTP Server.

Copying the Images Directory When Upgrading

If you are upgrading from a previous version of Oracle HTML DB, you should rename the existing images directory for Oracle HTML DB to reflect the release number (for example, images_1_5). By renaming the images directory, you have the option reverting to it later on.

To locate images directory on the file system, review the following files for the text alias /i/:

- Oracle9i HTTP Server Release 2, see the httpd.conf file

- Oracle HTTP Server 10g, see the marvel.conf file

- Oracle Application Server 10g, see the marvel.conf file

Copying the Images Directory in New Installation

On a Windows system, you can copy the htmldb\images directory using Windows Explorer or execute a command such as the following from a command prompt:

xcopy /E /I htmldb\images ORACLE_BASE\ORACLE_HOME\Apache\Apache\images

On UNIX or Linux based systems, you can copy the htmldb/images directory by executing a command such as the following:

cp -rf htmldb/images ORACLE_BASE/ORACLE_HOME/Apache/Apache

Configuring Oracle HTTP Server When Upgrading

If you are upgrading Oracle HTML DB from release 1.5.0.00.33 or 1.5.1.00.12 and the password you provided during your initial installation differs from the one you specified while executing the htmldbins.sql script, you need to modify the file that contains the Database Access Descriptors (DADs). The following sections describe the parameter you need to modify depending upon the type of Oracle HTTP Server in your environment.

Topics in this section include:

- Oracle HTTP Server Release 9.0.3

- Oracle HTTP Server 10g Release 1 or Oracle Application Server10g

Note:

Only perform the tasks that follow if the password you provided during your initial installation differs from the one you specified while executing the htmldbins.sql script.

Oracle HTTP Server Release 9.0.3

If you are upgrading Oracle HTML DB and are running Oracle HTTP Server release 9.0.3 or higher, you must modify the parameter password in the wdbsvr.app file.

To modify the parameter password in the wdbsvr.app file:

1. Use a text editor and open the wdbsvr.app file.

- For UNIX and Linux based systems, the file is located at:

ORACLE_BASE/ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app

- For Windows based systems, the file is located at:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app

2. Find the DAD settings for Oracle HTML DB by searching for the following:

DAD_htmldb

3. Edit value next to the parameter password to match the password you provided while executing the htmldbins.sql script.

4. Save your changes.

5. Stop and restart Oracle HTTP Server.

- For UNIX and Linux based systems, execute the following commands:

ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl stop
ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl start

Note that if the Oracle HTTP Server is listening on a port less than 1024, the these commands must be executed as a privileged user (such as root).

- For Windows based systems:

- Stop Oracle HTTP Server - From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Stop HTTP Server.

- Restart Oracle HTTP Server - - From the Start menu, select Oracle - OraHome, Oracle HTTP Server, and Start HTTP Server.

See Also:

Oracle HTTP Server Administration Guide

Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g

If you are upgrading Oracle HTML DB and are running Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g, you must modify the parameter PlsqlDatabasePassword in the marvel.conf file.

To modify the parameter PlsqlDatabasePassword in the marvel.conf file:

1. Use a text editor and open the marvel.conf file:

- For UNIX and Linux based systems, the file is located at:

ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/marvel.conf

- For Windows based systems, the file is located at:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\marvel.conf

2. Find the DAD settings for Oracle HTML DB by searching for the following:

/pls/htmldb

3. Modify the value of the parameter PlsqlDatabasePassword to match the password you provided while executing the htmldbins.sql script.

4. Save your changes.

5. For Oracle Application Server 10g, execute the following commands:

- For UNIX and Linux based systems:

ORACLE_BASE/ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs

6. Stop and restart Oracle HTTP Server.

- For UNIX and Linux based systems, execute the following commands:

ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server
ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server

See Also:

"Obfuscating PlsqlDatabasePassword Parameter" and Oracle HTTP Server Administration Guide

Configuring Oracle HTTP Server in a New Installation

Oracle HTML DB must have access to Oracle HTTP Server with mod_plsql. The instructions that follow explain how to configure three different versions of Oracle HTTP Server with mod_plsql.

Topics in this section include:

- Oracle HTTP Server Release 9.0.3

- Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g

Oracle HTTP Server Release 9.0.3

The wdbsvr.app file contains information about Database Access Descriptors (DADs). A DAD is a set of values that specify how the Oracle HTTP Server component modplsql connects to the database server to fulfill an HTTP request. You create a DAD to specify how to connect to an Oracle HTML DB instance.

Modifying the Oracle9i wdbsvr.app File

To create the DAD you modify the file wdbsvr.app and add an entry for Oracle HTML DB.

To modify the wdbsvr.app file:

1. Use a text editor and open the wdbsvr.app file:

- For UNIX and Linux based systems, the file is located at:

ORACLE_BASE/ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\cfg\wdbsvr.app

2. Add an entry for Oracle HTML DB using the following syntax. Only change the settings indicated in italics.

[DAD_htmldb]
connect_string = localhost:1521:orcl
password = htmldb
username = htmldb_public_user
default_page = htmldb
document_table = wwv_flow_file_objects$
document_path = docs
document_proc = wwv_flow_file_mgr.process_download
reuse = Yes
enablesso = No
stateful = STATELESS_RESET
nls_lang = American_America.AL32UTF8

Where:

- connect_string refers to the host ID, port number, and Oracle9i database where Oracle HTML DB was installed. Use the format host:port:sid.

If the Oracle9i version of Oracle HTTP Server you want to use is installed in the same Oracle home as the database you specified for use with Oracle HTML DB, leave this parameter blank.

- password is the HTML DB password you passed as the first argument to the htmldbins.sql script.

- nls_lang refers to the language setting. It must match the NLS settings of the database. For example:

American_America.AL32UTF8

If either the territory portion or the language portion of the NLS settings contain a space, you must wrap the value in double quotes, like the following example:

nls_lang = "ENGLISH_UNITED KINGDOM.AL32UTF8"

You can find information about your database's NLS settings by querying the view NLS_DATABASE_PARAMETERS as shown in the following example:

SELECT parameter,value
FROM nls_database_parameters
WHERE PARAMETER IN ('NLS_CHARACTERSET','NLS_LANGUAGE','NLS_TERRITORY');

3. Leave the remaining settings, including the username setting, as they appear in the previous example.

4. Save and exit the wdbsvr.app file.

Modifying the Oracle9i httpd.conf File

You need to modify the httpd.conf file to include an alias that points to the file system path where you copied the images directory.

See Also:

""Copying the Images Directory When Upgrading" and "Installing the Oracle HTML DB Software"

To modify httpd.conf to include an alias that points to the location of the images directory:

1. Use a text editor and open the httpd.conf file

- For UNIX and Linux based systems, the file is located at:

ORACLE_BASE/ORACLE_HOME/Apache/Apache/conf/httpd.conf

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\httpd.conf

2. Add an alias entry that points to the file system path where you copied the images directory. The following examples assume you specified the image directory alias as /i/when you ran the htmldbins.sql script.

- Windows based system example:

Alias /i/ "C:\oracle\ora92\Apache\Apache\images/"

Note you must include the forward slash (/) at the end of the path.

- UNIX and Linux based system example:

Alias /i/ "/home/oracle/OraHome1/Apache/Apache/images/"

3. Save and exit the httpd.conf file.

4. Stop and restart Oracle HTTP Server.

- For UNIX and Linux based systems, execute the following commands:

ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl stop
ORACLE_BASE/ORACLE_HOME/Apache/Apache/bin/apachectl start

Note that if the Oracle HTTP Server is listening on a port less than 1024, the these commands must be executed as a privileged user (such as root).

- For Windows based systems:

- Stop Oracle HTTP Server - From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Stop HTTP Server.

- Restart Oracle HTTP Server- From the Start menu, select Programs, Oracle - OraHome, Oracle HTTP Server, and Start HTTP Server.

See Also:

Oracle HTTP Server Administration Guide

Oracle HTTP Server 10g Release 1 or Oracle Application Server 10g

You need to modify the dads.conf file to include an alias that points to the file system path where you copied the images directory.

See Also:

""Copying the Images Directory When Upgrading" and "Installing the Oracle HTML DB Software"

To modify the dads.conf file to include an alias that points to the location of the images directory:

1. Use a text editor and open the dads.conf file:

- For UNIX and Linux based systems, the file is located at:

ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/dads.conf

- For Windows based systems, the file is located at:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.conf

2. Add an alias entry that points to the file system path where you copied the images directory.
Note you need to use the alias you specified in the fifth positional argument to htmldbins.sql. The following examples assume you specified the image directory alias as /i/.

- Windows based system example:

Alias /i/ "C:\oracle\ora101\Apache\Apache\images/"

Note you must include the forward slash (/) at the end of the path.

- UNIX and Linux based system example:

Alias /i/ "/home/oracle/OraHome1/Apache/Apache/images/"

3. Add an DAD entry for Oracle HTML DB using the following syntax. Replace the values PlsqlDatabasePassword, PlsqlDatabaseConnectString, and PlsqlNLSLanguage with values appropriate values for your environment.

<Location /pls/htmldb>
SetHandler pls_handler
Order deny,allow
Allow from all
AllowOverride None
PlsqlDatabaseUsername      HTMLDB_PUBLIC_USER
PlsqlDatabasePassword      htmldb
PlsqlDatabaseConnectString localhost:1521:htmldbdv ServiceNameFormat
PlsqlDefaultPage           htmldb
PlsqlDocumentTablename     wwv_flow_file_objects$
PlsqlDocumentPath          docs
PlsqlDocumentProcedure     wwv_flow_file_mgr.process_download
PlsqlAuthenticationMode    Basic
PlsqlNLSLanguage           AMERICAN_AMERICA.AL32UTF8
</Location>

If either the territory portion or the language portion of the NLS settings contain a space, you must wrap the value in double quotes, like the following example:

PlsqlNLSLanguage     "ENGLISH_UNITED KINGDOM.AL32UTF8"

4. Save and exit the dads.conf file.

5. (Oracle Application Server only) Execute the following commands:

- For UNIX and Linux based systems:

ORACLE_BASE/ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs

6. Stop and restart Oracle HTTP Server.

- For UNIX and Linux based systems, execute the following commands:

ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
ORACLE_BASE/ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server
ORACLE_BASE\ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server

See Also:

"Obfuscating PlsqlDatabasePassword Parameter" and Oracle HTTP Server Administration Guide

Installing Oracle HTML DB in Other Languages

The Oracle HTML DB interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle HTML DB can be installed with one or more of these translated versions. At runtime, each user's Web browser language settings determine the specific language version.

The translated version of Oracle HTML DB should be loaded into a database that has a character set that can support the specific language. If you attempt to install a translated version of Oracle HTML DB into a database that does support the character encoding of the language, the installation may fail or the translated Oracle HTML DB instance may appear corrupt when run. The database character set AL32UTF8 supports all the translated versions of Oracle HTML DB.

You can manually install translated versions of Oracle HTML DB using SQL*Plus. The installation files are encoded in UTF8.

Note:

Regardless of the target database character set, to install a translated version of Oracle HTML DB you must set the character set value of the NLS_LANG environment variable to AL32UTF8 prior to starting SQL*Plus.

The following examples illustrates valid NLS_LANG settings for loading Oracle HTML DB translations:

American_America.AL32UTF8
Japanese_Japan.AL32UTF8

To install a translated version of Oracle HTML DB:

1. Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:

- Bourne or Korn shell:

NLS_LANG=American_America.AL32UTF8
export NLS_LANG

- C shell:

setenv NLS_LANG American_America.AL32UTF8

- For Windows based systems:

set NLS_LANG=American_America.AL32UTF8

2. Start SQL*Plus and connect to the target database as SYS.

3. Execute the following statement:

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;

4. Execute the appropriate language specific script. For example:

@load_de.sql

The installation scripts are located in subdirectories identified by a language code in the unzipped distribution /htmldb/builder. For example, the German version is located in /htmldb/builder/de and the Japanese version is located in /htmldb/builder/ja. Within each of these directories, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).

Obfuscating PlsqlDatabasePassword Parameter

The PlsqlDatabasePassword parameter specifies the password for logging in to the database. You can use the the dadTool.pl utility to obfuscate passwords in the dads.conf file.

You can find the dadTool.pl utility in the following directory:

- For UNIX and Linux based systems:

ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf

- For Windows based systems:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf

Obfuscating Passwords in a New Installation

In a new installation, the PlsqlDatabasePassword parameter is found in the dads.conf file. To obfuscate passwords in a new installation, run the dadTool.pl utiity by following the instructions in the dadTool.README file.

Obfuscating Passwords if Upgrading

If you have upgraded from a previous release, the DAD information is in the file marvel.conf. Before you can run the the dadTool.pl utiity, you must copy the DAD entry from the marvel.conf file to the dads.conf file.

To obfuscate passwords when upgrading:

1. Use a text editor and copy the entry for /pls/htmldb from the marvel.conf file into the dads.conf file.

- For UNIX and Linux based systems, these files are located in:

ORACLE_BASE/ORACLE_HOME/Apache/modplsql/conf/dads.conf

- For Windows based systems, these files are located in:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.conf

2. Run dadTool.pl by following the instructions in the dadTool.README file.

3. Copy the entry for /pls/htmldb from the dads.conf file back into marvel.conf.

4. Remove the entry for /pls/htmldb from the dads.conf file.

Logging in to Oracle HTML DB

You open the Oracle HTML DB home page in a Web browser. To view or develop Oracle HTML DB applications, the Web browser must support Java Script and the HTML 4.0 and CSS 1.0 standards. The following browsers meet this requirement:

- Netscape Communicator 7.0 or later

- Microsoft Internet Explorer 5.5 or later

- Mozilla 1.2 or later

Accessing the Oracle HTML DB Login Page

To log in to Oracle HTML DB, open the following URL in a Web browser:

http://hostname:port/pls/database_access_descriptor/

Where:

- hostname is the name of the system where Oracle HTTP Server is installed.

- port is the is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from either of the following files:

- ORACLE_BASE\ORACLE_HOME\install\portlist.ini

- ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\httpd.conf

- database_access_descriptor describes how Oracle HTTP Server connects to the database server so that it can fulfill an HTTP request. The default value is htmldb.

See Also:

ORACLE_BASE\ORACLE_HOME\Apache\modplsql\conf\dads.readme for more information on database access descriptors

The Oracle HTML DB Login page appears.

In the Oracle HTML DB development environment, users log in to a shared work area called a workspace. Users are divided into three primary roles:

- Developer

A developer can create and edit applications.

- Workspace administrator

A Workspace administrator performs administrator tasks specific to their workspace such as managing user accounts, monitoring workspace activity, and viewing log files.

- Oracle HTML DB administrator

An Oracle HTML DB administrator is a superuser that manages the entire hosted instance. To perform these tasks, an Oracle HTML DB administrator logs into the Oracle HTML DB Administration Services application.

If you are a developer, an administrator must grant you access to a workspace. If you are an Oracle HTML DB administrator, you need to:

- Log into Oracle HTML DB Administration Services. Oracle HTML DB Administration Services is a separate application for managing an entire Oracle HTML DB instance.

- Specify a provisioning mode. In Oracle HTML DB Administration Services you need to determine how the process of creating (or provisioning) a workspace will work in your development environment.

- Create a Workspace. A workspace is a shared work area within the Oracle HTML DB development environment that has a unique ID and name. An Oracle HTML DB administrator can create a workspace manually or have users submit requests.

- Log in to a Workspace. Once you create a workspace in Oracle HTML DB Administration Services, return to the Oracle HTML DB Login page and log in to that workspace.

See Also:

"Managing an Oracle HTML DB Hosted Service" in Oracle HTML DB User's Guide for more information on logging in to and using the Oracle HTML DB Administration Services application

A Oracle HTML DB Troubleshooting

This appendix contains information on troubleshooting.

This chapter contains these topics:

- Reviewing a Log of an Installation Session

- Cleaning Up After a Failed Installation

- Images Displaying Incorrectly in Oracle HTML DB

Reviewing a Log of an Installation Session

The htmldbins.sql script creates a log file in the htmldb directory using the naming convention installYYYY-MM-DD_HH24-MI-SS.log. In a successful installation, the log file contains the following text:

Thank you for installing Oracle HTML DB.
Oracle HTML DB is installed in the FLOWS_010600 schema.

If the log file contains a few errors, it does not mean that your installation failed. Note that acceptable errors are noted as such in the log file.

Cleaning Up After a Failed Installation

In a successful installation the following banner displays at the end of the installation:

Thank you for installing Oracle HTML DB.
Oracle HTML DB is installed in the FLOWS_010600 schema.

To reinstall, you need to drop either one or two database schemas depending upon the installation type.

After a Failed Upgrade Installation

In the case of a failed upgrade installation, you should first revert Oracle HTML DB to release 1.5 and then remove the schemas associated with release 1.6.

To revert Oracle HTML DB to release 1.5:

1. Execute the following command in SQL*Plus:

a. Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.

b. Execute the following:

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010500;
exec flows_010500.wwv_flow_upgrade.switch_schemas
('FLOWS_010600','FLOWS_010500');

To remove the release 1.6 schema:

1. Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.

2. Execute the following commands:

DROP user FLOWS_010600 CASCADE;

After a Failed New Installation

To remove schemas after a failed new installation:

1. Start SQL*Plus and connect the database where Oracle HTML DB is installed as SYS or SYSTEM.

2. Execute the following commands:

drop user FLOWS_010600 cascade;
drop user FLOWS_FILES cascade;

Images Displaying Incorrectly in Oracle HTML DB

In "Configuring Oracle HTTP Server in a New Installation", you added an alias entry that points to the file system path where you copied the images directory. If images in Oracle HTML DB do not display correctly, you may have more than one defintion of the /i/ alias. To address this issue:

- If possible, rename the first instance of /i/ to a different alias name.

- Alternatively, copy the images from the ORACLE_BASE\ORACLE_HOME\marvel\images directory to the directory defined by the first /i/ alias.

Index
C  D  G  H  I  L  M  N  O  P  R  S  T  U  X

C

configuring

Oracle Application Server 10g (new installation), 4.4.2

Oracle Application Server 10g (upgrade), 4.3.2

Oracle HTTP Server (new installation), 4.4

Oracle HTTP Server 10g (new installation), 4.4.2

Oracle HTTP Server 10g (upgrade), 4.3.2

D

dadTool.pl utility, 4.6

database requirement

Oracle HTML DB, 2.1

shared_pool_size, 2.1.1

disk space

requirements, 2.3

documentation

on administration and tuning, Preface

on migrating and upgrading from previous release, Preface

related, Preface

G

getting started

HTML DB, 4.7

H

HTML DB

getting started, 4.7

htmldb_1.6.0.zip, 3.2 htmldbins.sql, 3.2 HTTP Server

pre-installation tasks, 3.1

requirement, 2.2

I

images

copying in new installation, 4.2.2

copying when upgrading, 4.2.1

installation

overview, 1.1

planning, 1.1

process, 1.2

requirements, 1.1, 2

steps, 3.2

installing

failures, A.2

htmldb_1.6.0.zip, 3.2

Oracle Internet Directory, Preface

other languages, 4.5

installing software, 3.2

L

l, 3.1

listener

stopping, 3.1

log file, A.1

M

marvel.conf

modifying, 4.3.2

N

new installation

configuring Oracle Application Server 10g, 4.4.2

configuring Oracle HTTP Server, 4.4

configuring Oracle HTTP Server 10g Release 1, 4.4.2

configuring Oracle HTTP Server 9.0.3, 4.4.1

copying images, 4.2.2

modifying dads.conf, 4.4.2

modifying httpd.conf, 4.4.1.2

modifying wdbsvr.app, 4.4.1

obfuscating password, 4.6.1

O

obfuscate

password, 4.6

Oracle Application Server 10g

configuring (upgrade), 4.3.2

Oracle HTML DB

database requirement, 2.1

disk space requirements, 2.3

installing, 3.2

logging into, 4.7

Oracle HTTP Server

requirement, 2.2

Oracle Text requirement, 2.5 XML DB requirement, 2.4 Oracle HTTP Server

pre-installation tasks, 3.1

Oracle HTTP Server 10g

configuring (upgrade), 4.3.2

Oracle HTTP Server 9.0.3

configuring (upgrade), 4.3.1

Oracle Text

requirement, 2.5

overview, 1.1

P

password

obfuscating, 4.6

post-installation tasks, 4

configuing Oracle HTTP Server (upgrading), 4.3

configuring

Oracle Application Server 10g, 4.4.2

configuring Oracle HTTP Server (new), 4.4 configuring Oracle HTTP Server 9.0.3, 4.4.1 copying images in new installation, 4.2.2 copying images when upgrading, 4.2.1 getting started, 4.7 installing other languages, 4.5 obfuscating passwords, 4.6 pre-installation tasks

stopping processes, 3.1

R

related documentation, Preface

requirements, 2

database, 2.1

disk space, 2.3

Oracle HTTP Server, 2.2

Oracle Text, 2.5

Oracle XML, 2.4

running

htmldbins.sql, 3.2

S

shared_pool_size

changing, 2.1.1

T

translated version

installing, 4.5

troubleshooting, A

cleaning up after failed installation, A.2

reviewing log file, A.1

U

upgrading

about, 1.3

configuring Oracle Application Server 10g, 4.3.2

configuring Oracle HTTP Server 10g, 4.3.2

configuring Oracle HTTP Server 9.0.3, 4.3.1

copying images, 4.2.1

modifying DADs, 4.3

modifying wdbsvr.app, 4.3.1

obfuscating password, 4.6.2

X

XML DB

requirement, 2.4

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.